Commit efcc2da3 authored by Stefan Roese's avatar Stefan Roese Committed by Grant Likely

powerpc/of-device-tree: Factor MTD physmap bindings out of booting-without-of

It's easier to find bindings descriptions in separate files.  So factor
out the MTD physmap bindings into a separate file to not clutter
booting-without-of.txt more.
Signed-off-by: default avatarStefan Roese <sr@denx.de>
Signed-off-by: default avatarGrant Likely <grant.likely@secretlab.ca>
parent 41240102
...@@ -43,12 +43,11 @@ Table of Contents ...@@ -43,12 +43,11 @@ Table of Contents
2) Representing devices without a current OF specification 2) Representing devices without a current OF specification
a) PHY nodes a) PHY nodes
b) Interrupt controllers b) Interrupt controllers
c) CFI or JEDEC memory-mapped NOR flash c) 4xx/Axon EMAC ethernet nodes
d) 4xx/Axon EMAC ethernet nodes d) Xilinx IP cores
e) Xilinx IP cores e) USB EHCI controllers
f) USB EHCI controllers f) MDIO on GPIOs
g) MDIO on GPIOs g) SPI busses
h) SPI busses
VII - Marvell Discovery mv64[345]6x System Controller chips VII - Marvell Discovery mv64[345]6x System Controller chips
1) The /system-controller node 1) The /system-controller node
...@@ -999,7 +998,7 @@ compatibility. ...@@ -999,7 +998,7 @@ compatibility.
translation of SOC addresses for memory mapped SOC registers. translation of SOC addresses for memory mapped SOC registers.
- bus-frequency: Contains the bus frequency for the SOC node. - bus-frequency: Contains the bus frequency for the SOC node.
Typically, the value of this field is filled in by the boot Typically, the value of this field is filled in by the boot
loader. loader.
Recommended properties: Recommended properties:
...@@ -1287,71 +1286,7 @@ platforms are moved over to use the flattened-device-tree model. ...@@ -1287,71 +1286,7 @@ platforms are moved over to use the flattened-device-tree model.
device_type = "open-pic"; device_type = "open-pic";
}; };
c) CFI or JEDEC memory-mapped NOR flash c) 4xx/Axon EMAC ethernet nodes
Flash chips (Memory Technology Devices) are often used for solid state
file systems on embedded devices.
- compatible : should contain the specific model of flash chip(s)
used, if known, followed by either "cfi-flash" or "jedec-flash"
- reg : Address range of the flash chip
- bank-width : Width (in bytes) of the flash bank. Equal to the
device width times the number of interleaved chips.
- device-width : (optional) Width of a single flash chip. If
omitted, assumed to be equal to 'bank-width'.
- #address-cells, #size-cells : Must be present if the flash has
sub-nodes representing partitions (see below). In this case
both #address-cells and #size-cells must be equal to 1.
For JEDEC compatible devices, the following additional properties
are defined:
- vendor-id : Contains the flash chip's vendor id (1 byte).
- device-id : Contains the flash chip's device id (1 byte).
In addition to the information on the flash bank itself, the
device tree may optionally contain additional information
describing partitions of the flash address space. This can be
used on platforms which have strong conventions about which
portions of the flash are used for what purposes, but which don't
use an on-flash partition table such as RedBoot.
Each partition is represented as a sub-node of the flash device.
Each node's name represents the name of the corresponding
partition of the flash device.
Flash partitions
- reg : The partition's offset and size within the flash bank.
- label : (optional) The label / name for this flash partition.
If omitted, the label is taken from the node name (excluding
the unit address).
- read-only : (optional) This parameter, if present, is a hint to
Linux that this flash partition should only be mounted
read-only. This is usually used for flash partitions
containing early-boot firmware images or data which should not
be clobbered.
Example:
flash@ff000000 {
compatible = "amd,am29lv128ml", "cfi-flash";
reg = <ff000000 01000000>;
bank-width = <4>;
device-width = <1>;
#address-cells = <1>;
#size-cells = <1>;
fs@0 {
label = "fs";
reg = <0 f80000>;
};
firmware@f80000 {
label ="firmware";
reg = <f80000 80000>;
read-only;
};
};
d) 4xx/Axon EMAC ethernet nodes
The EMAC ethernet controller in IBM and AMCC 4xx chips, and also The EMAC ethernet controller in IBM and AMCC 4xx chips, and also
the Axon bridge. To operate this needs to interact with a ths the Axon bridge. To operate this needs to interact with a ths
...@@ -1499,7 +1434,7 @@ platforms are moved over to use the flattened-device-tree model. ...@@ -1499,7 +1434,7 @@ platforms are moved over to use the flattened-device-tree model.
available. available.
For Axon: 0x0000012a For Axon: 0x0000012a
e) Xilinx IP cores d) Xilinx IP cores
The Xilinx EDK toolchain ships with a set of IP cores (devices) for use The Xilinx EDK toolchain ships with a set of IP cores (devices) for use
in Xilinx Spartan and Virtex FPGAs. The devices cover the whole range in Xilinx Spartan and Virtex FPGAs. The devices cover the whole range
...@@ -1761,7 +1696,7 @@ platforms are moved over to use the flattened-device-tree model. ...@@ -1761,7 +1696,7 @@ platforms are moved over to use the flattened-device-tree model.
listed above, nodes for these devices should include a phy-handle listed above, nodes for these devices should include a phy-handle
property, and may include other common network device properties property, and may include other common network device properties
like local-mac-address. like local-mac-address.
iv) Xilinx Uartlite iv) Xilinx Uartlite
Xilinx uartlite devices are simple fixed speed serial ports. Xilinx uartlite devices are simple fixed speed serial ports.
...@@ -1793,7 +1728,7 @@ platforms are moved over to use the flattened-device-tree model. ...@@ -1793,7 +1728,7 @@ platforms are moved over to use the flattened-device-tree model.
- reg-offset : A value of 3 is required - reg-offset : A value of 3 is required
- reg-shift : A value of 2 is required - reg-shift : A value of 2 is required
f) USB EHCI controllers e) USB EHCI controllers
Required properties: Required properties:
- compatible : should be "usb-ehci". - compatible : should be "usb-ehci".
...@@ -1819,7 +1754,7 @@ platforms are moved over to use the flattened-device-tree model. ...@@ -1819,7 +1754,7 @@ platforms are moved over to use the flattened-device-tree model.
big-endian; big-endian;
}; };
g) MDIO on GPIOs f) MDIO on GPIOs
Currently defined compatibles: Currently defined compatibles:
- virtual,gpio-mdio - virtual,gpio-mdio
...@@ -1839,7 +1774,7 @@ platforms are moved over to use the flattened-device-tree model. ...@@ -1839,7 +1774,7 @@ platforms are moved over to use the flattened-device-tree model.
&qe_pio_c 6>; &qe_pio_c 6>;
}; };
h) SPI (Serial Peripheral Interface) busses g) SPI (Serial Peripheral Interface) busses
SPI busses can be described with a node for the SPI master device SPI busses can be described with a node for the SPI master device
and a set of child nodes for each SPI slave on the bus. For this and a set of child nodes for each SPI slave on the bus. For this
......
CFI or JEDEC memory-mapped NOR flash
Flash chips (Memory Technology Devices) are often used for solid state
file systems on embedded devices.
- compatible : should contain the specific model of flash chip(s)
used, if known, followed by either "cfi-flash" or "jedec-flash"
- reg : Address range of the flash chip
- bank-width : Width (in bytes) of the flash bank. Equal to the
device width times the number of interleaved chips.
- device-width : (optional) Width of a single flash chip. If
omitted, assumed to be equal to 'bank-width'.
- #address-cells, #size-cells : Must be present if the flash has
sub-nodes representing partitions (see below). In this case
both #address-cells and #size-cells must be equal to 1.
For JEDEC compatible devices, the following additional properties
are defined:
- vendor-id : Contains the flash chip's vendor id (1 byte).
- device-id : Contains the flash chip's device id (1 byte).
In addition to the information on the flash bank itself, the
device tree may optionally contain additional information
describing partitions of the flash address space. This can be
used on platforms which have strong conventions about which
portions of the flash are used for what purposes, but which don't
use an on-flash partition table such as RedBoot.
Each partition is represented as a sub-node of the flash device.
Each node's name represents the name of the corresponding
partition of the flash device.
Flash partitions
- reg : The partition's offset and size within the flash bank.
- label : (optional) The label / name for this flash partition.
If omitted, the label is taken from the node name (excluding
the unit address).
- read-only : (optional) This parameter, if present, is a hint to
Linux that this flash partition should only be mounted
read-only. This is usually used for flash partitions
containing early-boot firmware images or data which should not
be clobbered.
Example:
flash@ff000000 {
compatible = "amd,am29lv128ml", "cfi-flash";
reg = <ff000000 01000000>;
bank-width = <4>;
device-width = <1>;
#address-cells = <1>;
#size-cells = <1>;
fs@0 {
label = "fs";
reg = <0 f80000>;
};
firmware@f80000 {
label ="firmware";
reg = <f80000 80000>;
read-only;
};
};
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment