Jamie Lentin | 83619ea | 2012-03-27 22:54:15 +0100 | [diff] [blame] | 1 | Representing flash partitions in devicetree |
| 2 | |
| 3 | Partitions can be represented by sub-nodes of an mtd device. This can be used |
| 4 | on platforms which have strong conventions about which portions of a flash are |
| 5 | used for what purposes, but which don't use an on-flash partition table such |
| 6 | as RedBoot. |
| 7 | |
| 8 | #address-cells & #size-cells must both be present in the mtd device and be |
| 9 | equal to 1. |
| 10 | |
| 11 | Required properties: |
| 12 | - reg : The partition's offset and size within the mtd bank. |
| 13 | |
| 14 | Optional properties: |
| 15 | - label : The label / name for this partition. If omitted, the label is taken |
| 16 | from the node name (excluding the unit address). |
| 17 | - read-only : This parameter, if present, is a hint to Linux that this |
| 18 | partition should only be mounted read-only. This is usually used for flash |
| 19 | partitions containing early-boot firmware images or data which should not be |
| 20 | clobbered. |
| 21 | |
| 22 | Examples: |
| 23 | |
| 24 | |
| 25 | flash@0 { |
| 26 | #address-cells = <1>; |
| 27 | #size-cells = <1>; |
| 28 | |
| 29 | partition@0 { |
| 30 | label = "u-boot"; |
| 31 | reg = <0x0000000 0x100000>; |
| 32 | read-only; |
| 33 | }; |
| 34 | |
| 35 | uimage@100000 { |
| 36 | reg = <0x0100000 0x200000>; |
| 37 | }; |
Rob Herring | bf6c973 | 2012-07-06 07:16:14 -0500 | [diff] [blame] | 38 | }; |