mtd-physmap.txt 2.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778
  1. CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
  2. Flash chips (Memory Technology Devices) are often used for solid state
  3. file systems on embedded devices.
  4. - compatible : should contain the specific model of mtd chip(s)
  5. used, if known, followed by either "cfi-flash", "jedec-flash"
  6. or "mtd-ram".
  7. - reg : Address range(s) of the mtd chip(s)
  8. It's possible to (optionally) define multiple "reg" tuples so that
  9. non-identical chips can be described in one node.
  10. - bank-width : Width (in bytes) of the bank. Equal to the
  11. device width times the number of interleaved chips.
  12. - device-width : (optional) Width of a single mtd chip. If
  13. omitted, assumed to be equal to 'bank-width'.
  14. - #address-cells, #size-cells : Must be present if the device has
  15. sub-nodes representing partitions (see below). In this case
  16. both #address-cells and #size-cells must be equal to 1.
  17. - no-unaligned-direct-access: boolean to disable the default direct
  18. mapping of the flash.
  19. On some platforms (e.g. MPC5200) a direct 1:1 mapping may cause
  20. problems with JFFS2 usage, as the local bus (LPB) doesn't support
  21. unaligned accesses as implemented in the JFFS2 code via memcpy().
  22. By defining "no-unaligned-direct-access", the flash will not be
  23. exposed directly to the MTD users (e.g. JFFS2) any more.
  24. For JEDEC compatible devices, the following additional properties
  25. are defined:
  26. - vendor-id : Contains the flash chip's vendor id (1 byte).
  27. - device-id : Contains the flash chip's device id (1 byte).
  28. The device tree may optionally contain sub-nodes describing partitions of the
  29. address space. See partition.txt for more detail.
  30. Example:
  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. };
  48. Here an example with multiple "reg" tuples:
  49. flash@f0000000,0 {
  50. #address-cells = <1>;
  51. #size-cells = <1>;
  52. compatible = "intel,PC48F4400P0VB", "cfi-flash";
  53. reg = <0 0x00000000 0x02000000
  54. 0 0x02000000 0x02000000>;
  55. bank-width = <2>;
  56. partition@0 {
  57. label = "test-part1";
  58. reg = <0 0x04000000>;
  59. };
  60. };
  61. An example using SRAM:
  62. sram@2,0 {
  63. compatible = "samsung,k6f1616u6a", "mtd-ram";
  64. reg = <2 0 0x00200000>;
  65. bank-width = <2>;
  66. };