0001 Flash partitions in device tree
0002 ===============================
0003
0004 Flash devices can be partitioned into one or more functional ranges (e.g. "boot
0005 code", "nvram", "kernel").
0006
0007 Different devices may be partitioned in a different ways. Some may use a fixed
0008 flash layout set at production time. Some may use on-flash table that describes
0009 the geometry and naming/purpose of each functional region. It is also possible
0010 to see these methods mixed.
0011
0012 To assist system software in locating partitions, we allow describing which
0013 method is used for a given flash device. To describe the method there should be
0014 a subnode of the flash device that is named 'partitions'. It must have a
0015 'compatible' property, which is used to identify the method to use.
0016
0017 When a single partition is represented with a DT node (it depends on a used
0018 format) it may also be described using above rules ('compatible' and optionally
0019 some extra properties / subnodes). It allows describing more complex,
0020 hierarchical (multi-level) layouts and should be used if there is some
0021 significant relation between partitions or some partition internally uses
0022 another partitioning method.
0023
0024 Available bindings are listed in the "partitions" subdirectory.
0025
0026
0027 Deprecated: partitions defined in flash node
0028 ============================================
0029
0030 For backwards compatibility partitions as direct subnodes of the flash device are
0031 supported. This use is discouraged.
0032 NOTE: also for backwards compatibility, direct subnodes that have a compatible
0033 string are not considered partitions, as they may be used for other bindings.
