[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1452673622-5865-1-git-send-email-lixiubo@cmss.chinamobile.com>
Date: Wed, 13 Jan 2016 16:27:02 +0800
From: Xiubo Li <lixiubo@...s.chinamobile.com>
To: broonie@...nel.org
Cc: linux-kernel@...r.kernel.org,
Xiubo Li <lixiubo@...s.chinamobile.com>
Subject: [PATCH] regmap: dt-binding: simplify the doc and make it more readable
Signed-off-by: Xiubo Li <lixiubo@...s.chinamobile.com>
---
Documentation/devicetree/bindings/regmap/regmap.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/regmap/regmap.txt b/Documentation/devicetree/bindings/regmap/regmap.txt
index b494f8b..22cd9ad 100644
--- a/Documentation/devicetree/bindings/regmap/regmap.txt
+++ b/Documentation/devicetree/bindings/regmap/regmap.txt
@@ -11,9 +11,10 @@ on different SoCs using the devicetree, we need one way to simplify
this.
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.
+- {big,little}-endian: boolean properties, if absent the CPU and
+ the Device will be in the same endianness mode.
+ Note: they are only used for the device register values and the
+ buffers.
Examples:
Scenario 1 : CPU in LE mode & device in LE mode.
--
1.8.3.1
Powered by blists - more mailing lists