path: root/Documentation/devicetree/bindings/regmap/regmap.txt
diff options
authorMark Brown <broonie@kernel.org>2016-01-26 17:59:30 +0000
committerMark Brown <broonie@kernel.org>2016-01-27 18:46:38 +0000
commita06c488da0b0c1eebf710017675f00b9d5f9cf42 (patch)
tree10a608717ab425e5746a38485cd5cf007b50d32f /Documentation/devicetree/bindings/regmap/regmap.txt
parent92e963f50fc74041b5e9e744c330dca48e04f08d (diff)
regmap: Add explict native endian flag to DT bindings
Currently the binding document says that if no endianness is configured we use native endian but this is not in fact true for all binding types and we do have some devices that really want native endianness such as Broadcom MIPS SoCs where switching the endianness of the CPU also switches the endianness of external IPs. Provide an explicit option for this. Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'Documentation/devicetree/bindings/regmap/regmap.txt')
1 files changed, 7 insertions, 4 deletions
diff --git a/Documentation/devicetree/bindings/regmap/regmap.txt b/Documentation/devicetree/bindings/regmap/regmap.txt
index b494f8b8ef72..e98a9652ccc8 100644
--- a/Documentation/devicetree/bindings/regmap/regmap.txt
+++ b/Documentation/devicetree/bindings/regmap/regmap.txt
@@ -5,15 +5,18 @@ Index Device Endianness properties
1 BE 'big-endian'
2 LE 'little-endian'
+3 Native 'native-endian'
For one device driver, which will run in different scenarios above
on different SoCs using the devicetree, we need one way to simplify
-Required properties:
-- {big,little}-endian: these are boolean properties, if absent
- meaning that the CPU and the Device are in the same endianness mode,
- these properties are for register values and all the buffers only.
+Optional properties:
+- {big,little,native}-endian: these are boolean properties, if absent
+ then the implementation will choose a default based on the device
+ being controlled. These properties are for register values and all
+ the buffers only. Native endian means that the CPU and device have
+ the same endianness.
Scenario 1 : CPU in LE mode & device in LE mode.