From: Varka Bhadram <varkabhadram@gmail.com>
To: Xiubo Li <Li.Xiubo@freescale.com>,
broonie@kernel.org, mark.rutland@arm.com
Cc: robh+dt@kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCHv6 2/2] dt/bindings: Add the DT binding documentation for endianness
Date: Tue, 15 Jul 2014 11:03:24 +0530 [thread overview]
Message-ID: <53C4BD24.9000503@gmail.com> (raw)
In-Reply-To: <1405398183-31345-3-git-send-email-Li.Xiubo@freescale.com>
On 07/15/2014 09:53 AM, Xiubo Li wrote:
> Device-Tree binding for device endianness
> Index Device Endianness properties
> ---------------------------------------------------
> 1 BE 'big-endian'
> 2 LE 'little-endian'
>
> For one device driver, which will run in different scenarios above
> on different SoCs using the devicetree, we need one way to simplify
> this.
>
> Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> ---
> .../devicetree/bindings/regmap/regmap.txt | 47 ++++++++++++++++++++++
> 1 file changed, 47 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regmap/regmap.txt
>
> diff --git a/Documentation/devicetree/bindings/regmap/regmap.txt b/Documentation/devicetree/bindings/regmap/regmap.txt
> new file mode 100644
> index 0000000..b494f8b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regmap/regmap.txt
> @@ -0,0 +1,47 @@
> +Device-Tree binding for regmap
> +
> +The endianness mode of CPU & Device scenarios:
> +Index Device Endianness properties
> +---------------------------------------------------
> +1 BE 'big-endian'
> +2 LE 'little-endian'
> +
> +For one device driver, which will run in different scenarios above
> +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.
> +
It would be more readable if its like 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 propperties are for
values and all the buffers only.
> +Examples:
> +Scenario 1 : CPU in LE mode & device in LE mode.
> +dev: dev@40031000 {
> + compatible = "name";
> + reg = <0x40031000 0x1000>;
> + ...
> +};
> +
> +Scenario 2 : CPU in LE mode & device in BE mode.
> +dev: dev@40031000 {
> + compatible = "name";
> + reg = <0x40031000 0x1000>;
> + ...
> + big-endian;
> +};
> +
> +Scenario 3 : CPU in BE mode & device in BE mode.
> +dev: dev@40031000 {
> + compatible = "name";
> + reg = <0x40031000 0x1000>;
> + ...
> +};
> +
> +Scenario 4 : CPU in BE mode & device in LE mode.
> +dev: dev@40031000 {
> + compatible = "name";
> + reg = <0x40031000 0x1000>;
> + ...
> + little-endian;
> +};
--
Regards,
Varka Bhadram.
next prev parent reply other threads:[~2014-07-15 5:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 4:23 [PATCHv6 0/2] add DT endianness binding support for regmap Xiubo Li
2014-07-15 4:23 ` [PATCHv6 1/2] regmap: add DT endianness binding support Xiubo Li
2014-07-15 4:23 ` [PATCHv6 2/2] dt/bindings: Add the DT binding documentation for endianness Xiubo Li
2014-07-15 5:33 ` Varka Bhadram [this message]
[not found] ` <53C4BD24.9000503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-15 5:36 ` Li.Xiubo-KZfg59tc24xl57MIdRCFDg
[not found] ` <1405398183-31345-3-git-send-email-Li.Xiubo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-08-20 8:05 ` Thierry Reding
2014-08-20 9:14 ` Li.Xiubo-KZfg59tc24xl57MIdRCFDg
2014-08-20 9:43 ` Thierry Reding
2014-08-06 1:58 ` [PATCHv6 0/2] add DT endianness binding support for regmap Li.Xiubo
2014-08-16 13:14 ` Mark Brown
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=53C4BD24.9000503@gmail.com \
--to=varkabhadram@gmail.com \
--cc=Li.Xiubo@freescale.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).