From: Xiubo Li <Li.Xiubo@freescale.com>
To: <broonie@kernel.org>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Xiubo Li <Li.Xiubo@freescale.com>
Subject: [PATCHv2 2/3] regmap: Add the DT binding documentation for endianness
Date: Wed, 2 Apr 2014 18:09:08 +0800 [thread overview]
Message-ID: <1396433349-31470-3-git-send-email-Li.Xiubo@freescale.com> (raw)
In-Reply-To: <1396433349-31470-1-git-send-email-Li.Xiubo@freescale.com>
Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
---
.../bindings/regmap/regmap-endianness.txt | 49 ++++++++++++++++++++++
1 file changed, 49 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regmap/regmap-endianness.txt
diff --git a/Documentation/devicetree/bindings/regmap/regmap-endianness.txt b/Documentation/devicetree/bindings/regmap/regmap-endianness.txt
new file mode 100644
index 0000000..045d347
--- /dev/null
+++ b/Documentation/devicetree/bindings/regmap/regmap-endianness.txt
@@ -0,0 +1,49 @@
+Device-Tree bindings for regmap endianness
+
+Required properties:
+- reg-endian: Register endianness, this string property could be absent
+ as default endianness, or must be one of 'BE', 'LE' and 'NT'.
+- val-endian: Value endianness, this string property could be absent as
+ default endianness, or must be one of 'BE', 'LE' and 'NT'.
+
+The Endianness flags supported by regmap:
+
+DT properties Macros
+----------------------------------------
+ 'LE' REGMAP_ENDIAN_LITTLE
+ 'BE' REGMAP_ENDIAN_BIG
+ 'NT' REGMAP_ENDIAN_NATIVE
+ Absent REGMAP_ENDIAN_DEFAULT
+
+Examples:
+Case 1 : CPU in LE mode & SAI device in BE mode, using mmio.
+sai2: sai@40031000 {
+ compatible = "fsl,vf610-sai";
+ reg = <0x40031000 0x1000>;
+ ...
+ val-endian = 'BE';
+};
+
+Case 2 : CPU in BE mode & SAI device in LE mode, using mmio.
+sai2: sai@40031000 {
+ compatible = "fsl,vf610-sai";
+ reg = <0x40031000 0x1000>;
+ ...
+ val-endian = 'LE';
+};
+
+Case 3 : CPU in LE mode & SAI device in LE mode, using mmio.
+sai2: sai@40031000 {
+ compatible = "fsl,vf610-sai";
+ reg = <0x40031000 0x1000>;
+ ...
+ val-endian = 'NT'; or just absent.
+};
+
+Case 4 : CPU in BE mode & SAI device in BE mode, using mmio.
+sai2: sai@40031000 {
+ compatible = "fsl,vf610-sai";
+ reg = <0x40031000 0x1000>;
+ ...
+ val-endian = 'NT'; or just absent.
+};
--
1.8.4
next prev parent reply other threads:[~2014-04-02 10:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 10:09 [PATCHv2 0/3] regmap: add LE and DT binding " Xiubo Li
2014-04-02 10:09 ` [PATCHv2 1/3] regmap: implement LE formatting/parsing for 16/32-bit values Xiubo Li
2014-04-02 19:42 ` Mark Brown
2014-04-02 10:09 ` Xiubo Li [this message]
2014-04-02 19:48 ` [PATCHv2 2/3] regmap: Add the DT binding documentation for endianness Mark Brown
2014-04-03 7:04 ` Li.Xiubo
2014-04-14 21:09 ` Mark Brown
2014-04-23 5:08 ` Li.Xiubo
2014-04-02 10:09 ` [PATCHv2 3/3] regmap: add DT endianness binding support Xiubo Li
2014-04-02 19:50 ` Mark Brown
2014-04-03 5:26 ` Li.Xiubo
2014-04-14 21:07 ` Mark Brown
2014-04-02 11:14 ` [PATCHv2 0/3] regmap: add LE and DT binding for endianness Haijun.Zhang
2014-04-23 6:46 [PATCHv2 0/3] add DT endianness binding support Xiubo Li
2014-04-23 6:46 ` [PATCHv2 2/3] regmap: Add the DT binding documentation for endianness Xiubo Li
2014-04-23 8:40 ` Mark Rutland
2014-04-28 8:52 ` Li.Xiubo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1396433349-31470-3-git-send-email-Li.Xiubo@freescale.com \
--to=li.xiubo@freescale.com \
--cc=broonie@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®