blob: a63c2bd7de2b66f4d847618d31628d22cc2c870b [file] [log] [blame]
Wolfram Sangfc28c392009-07-17 14:39:23 +02001CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
Stefan Roeseefcc2da2009-04-16 15:11:54 -06002
3Flash chips (Memory Technology Devices) are often used for solid state
4file systems on embedded devices.
5
Wolfram Sangfc28c392009-07-17 14:39:23 +02006 - compatible : should contain the specific model of mtd chip(s)
7 used, if known, followed by either "cfi-flash", "jedec-flash"
8 or "mtd-ram".
9 - reg : Address range(s) of the mtd chip(s)
Stefan Roesec5a88dd2009-04-16 15:11:54 -060010 It's possible to (optionally) define multiple "reg" tuples so that
Wolfram Sangfc28c392009-07-17 14:39:23 +020011 non-identical chips can be described in one node.
12 - bank-width : Width (in bytes) of the bank. Equal to the
Stefan Roeseefcc2da2009-04-16 15:11:54 -060013 device width times the number of interleaved chips.
Wolfram Sangfc28c392009-07-17 14:39:23 +020014 - device-width : (optional) Width of a single mtd chip. If
Stefan Roeseefcc2da2009-04-16 15:11:54 -060015 omitted, assumed to be equal to 'bank-width'.
Wolfram Sangfc28c392009-07-17 14:39:23 +020016 - #address-cells, #size-cells : Must be present if the device has
Stefan Roeseefcc2da2009-04-16 15:11:54 -060017 sub-nodes representing partitions (see below). In this case
18 both #address-cells and #size-cells must be equal to 1.
19
20For JEDEC compatible devices, the following additional properties
21are defined:
22
23 - vendor-id : Contains the flash chip's vendor id (1 byte).
24 - device-id : Contains the flash chip's device id (1 byte).
25
Jamie Lentin83619ea2012-03-27 22:54:15 +010026The device tree may optionally contain sub-nodes describing partitions of the
27address space. See partition.txt for more detail.
Stefan Roeseefcc2da2009-04-16 15:11:54 -060028
29Example:
30
31 flash@ff000000 {
32 compatible = "amd,am29lv128ml", "cfi-flash";
33 reg = <ff000000 01000000>;
34 bank-width = <4>;
35 device-width = <1>;
36 #address-cells = <1>;
37 #size-cells = <1>;
38 fs@0 {
39 label = "fs";
40 reg = <0 f80000>;
41 };
42 firmware@f80000 {
43 label ="firmware";
44 reg = <f80000 80000>;
45 read-only;
46 };
47 };
Stefan Roesec5a88dd2009-04-16 15:11:54 -060048
49Here an example with multiple "reg" tuples:
50
51 flash@f0000000,0 {
52 #address-cells = <1>;
53 #size-cells = <1>;
54 compatible = "intel,PC48F4400P0VB", "cfi-flash";
55 reg = <0 0x00000000 0x02000000
56 0 0x02000000 0x02000000>;
57 bank-width = <2>;
58 partition@0 {
59 label = "test-part1";
60 reg = <0 0x04000000>;
61 };
62 };
Wolfram Sangfc28c392009-07-17 14:39:23 +020063
64An example using SRAM:
65
66 sram@2,0 {
67 compatible = "samsung,k6f1616u6a", "mtd-ram";
68 reg = <2 0 0x00200000>;
69 bank-width = <2>;
70 };
71