devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiubo Li <Li.Xiubo@freescale.com>
To: B29396@freescale.com, pankaj.dubey@samsung.com,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	sameo@linux.intel.com, lee.jones@linaro.org,
	devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Xiubo Li <Li.Xiubo@freescale.com>
Subject: [PATCH] mfd: syscon: binding: Add syscon endianness support.
Date: Thu, 18 Sep 2014 15:27:29 +0800	[thread overview]
Message-ID: <1411025249-34333-1-git-send-email-Li.Xiubo@freescale.com> (raw)

For many drivers which will support rich endianness of Devices
need define DT properties by itself with the binding support.

The regmap core has already support endianness of the following
case:
Index      Device     DT properties needed
------------------------------------------
1          BE         'big-endian'
2          LE         'little-endian'

Please see the regmap binding for more detail information of
the endianness support.

Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
---


This patch hasn't any dependency with Pankaj Dubey's:
    mfd: syscon: Decouple syscon interface from platform devices



 Documentation/devicetree/bindings/mfd/syscon.txt | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/Documentation/devicetree/bindings/mfd/syscon.txt b/Documentation/devicetree/bindings/mfd/syscon.txt
index fe8150b..7c33178 100644
--- a/Documentation/devicetree/bindings/mfd/syscon.txt
+++ b/Documentation/devicetree/bindings/mfd/syscon.txt
@@ -10,11 +10,22 @@ OS driver) to determine the location of the registers, and access the
 registers directly.
 
 Required properties:
-- compatible: Should contain "syscon".
-- reg: the register region can be accessed from syscon
+- compatible:		Should contain "syscon".
+- reg:			The register region can be accessed from syscon
 
-Examples:
+Optional property:
+- {big,little}-endian:	Boolean property. Please see ../regmap/regmap.txt
+			for more information.
+
+Example 1:
 gpr: iomuxc-gpr@020e0000 {
 	compatible = "fsl,imx6q-iomuxc-gpr", "syscon";
 	reg = <0x020e0000 0x38>;
 };
+
+Example 2:
+dcfg: dcfg@1ee0000 {
+	compatible = "fsl,ls1021a-dcfg", "syscon";
+	reg = <0x0 0x1ee0000 0x0 0x10000>;
+	big-endian;
+};
-- 
2.1.0.27.g96db324

             reply	other threads:[~2014-09-18  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  7:27 Xiubo Li [this message]
     [not found] ` <1411025249-34333-1-git-send-email-Li.Xiubo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-10-14  2:30   ` [PATCH] mfd: syscon: binding: Add syscon endianness support Li.Xiubo-KZfg59tc24xl57MIdRCFDg

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=1411025249-34333-1-git-send-email-Li.Xiubo@freescale.com \
    --to=li.xiubo@freescale.com \
    --cc=B29396@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pankaj.dubey@samsung.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sameo@linux.intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).