Connection between flash and controller is not necessary to be always of same type. It may varies from platform to platform. Adding endianness (optional) property to provide connection type information. Signed-off-by: Prabhakar Kushwaha <prabhakar.kushwaha@xxxxxxx> Reviewed-by: Rob Herring <robh@xxxxxxxxxx> --- Changes for v2: updated subject Changes for v3: fixed typo for "big-endian" Changes for v4: Moved binding definition in mtd-physmap.txt as discussed at https://patchwork.ozlabs.org/patch/842543/ Changes for v5: Sending as it is Documentation/devicetree/bindings/mtd/mtd-physmap.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt index 4a0a48bf4ecb..961a8eed9d0d 100644 --- a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt +++ b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt @@ -41,6 +41,11 @@ additional (optional) property is defined: - erase-size : The chip's physical erase block size in bytes. + The device tree may optionally contain endianness property. + little-endian or big-endian : It represents connection between controller and + flash. If this property is absent, flash is considered + to be host-endian. + The device tree may optionally contain sub-nodes describing partitions of the address space. See partition.txt for more detail. -- 2.14.1 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
