blob: 94de19b8f16bcd548e2e1163704b9fc3ae2ce31f [file] [log] [blame]
Wolfram Sangfc28c39f2009-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 Sangfc28c39f2009-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 Sangfc28c39f2009-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 Sangfc28c39f2009-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 Sangfc28c39f2009-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.
Stefan Roesed0788ce2012-08-17 15:22:32 +020019 - no-unaligned-direct-access: boolean to disable the default direct
20 mapping of the flash.
21 On some platforms (e.g. MPC5200) a direct 1:1 mapping may cause
22 problems with JFFS2 usage, as the local bus (LPB) doesn't support
23 unaligned accesses as implemented in the JFFS2 code via memcpy().
24 By defining "no-unaligned-direct-access", the flash will not be
25 exposed directly to the MTD users (e.g. JFFS2) any more.
Stefan Roeseefcc2da2009-04-16 15:11:54 -060026
27For JEDEC compatible devices, the following additional properties
28are defined:
29
30 - vendor-id : Contains the flash chip's vendor id (1 byte).
31 - device-id : Contains the flash chip's device id (1 byte).
32
Jamie Lentin83619ea2012-03-27 22:54:15 +010033The device tree may optionally contain sub-nodes describing partitions of the
34address space. See partition.txt for more detail.
Stefan Roeseefcc2da2009-04-16 15:11:54 -060035
36Example:
37
38 flash@ff000000 {
39 compatible = "amd,am29lv128ml", "cfi-flash";
40 reg = <ff000000 01000000>;
41 bank-width = <4>;
42 device-width = <1>;
43 #address-cells = <1>;
44 #size-cells = <1>;
45 fs@0 {
46 label = "fs";
47 reg = <0 f80000>;
48 };
49 firmware@f80000 {
50 label ="firmware";
51 reg = <f80000 80000>;
52 read-only;
53 };
54 };
Stefan Roesec5a88dd2009-04-16 15:11:54 -060055
56Here an example with multiple "reg" tuples:
57
58 flash@f0000000,0 {
59 #address-cells = <1>;
60 #size-cells = <1>;
61 compatible = "intel,PC48F4400P0VB", "cfi-flash";
62 reg = <0 0x00000000 0x02000000
63 0 0x02000000 0x02000000>;
64 bank-width = <2>;
65 partition@0 {
66 label = "test-part1";
67 reg = <0 0x04000000>;
68 };
69 };
Wolfram Sangfc28c39f2009-07-17 14:39:23 +020070
71An example using SRAM:
72
73 sram@2,0 {
74 compatible = "samsung,k6f1616u6a", "mtd-ram";
75 reg = <2 0 0x00200000>;
76 bank-width = <2>;
77 };
78