From: "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"rob@landley.net" <rob@landley.net>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Pawel Moll <Pawel.Moll@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCHv2 2/3] regmap: Add the DT binding documentation for endianness
Date: Mon, 28 Apr 2014 08:52:04 +0000 [thread overview]
Message-ID: <39a09c53860c41248d2fd475c3691cd8@BY2PR03MB505.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20140423084009.GB30036@e106331-lin.cambridge.arm.com>
> Subject: Re: [PATCHv2 2/3] regmap: Add the DT binding documentation for
> endianness
>
> On Wed, Apr 23, 2014 at 07:46:34AM +0100, Xiubo Li wrote:
> > Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> > ---
> > .../bindings/regmap/regmap-endianness.txt | 48
> ++++++++++++++++++++++
> > 1 file changed, 48 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..1d838c5
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/regmap/regmap-endianness.txt
> > @@ -0,0 +1,48 @@
> > +Device-Tree bindings for regmap endianness
>
> As regmap is a Linux internal detail, I don't see why it needs to leak
> into bindings.
>
> > +Required properties:
> > +- regmap-reg-endian: register endianness, see ../endianness/endianness.txt
> > + for detail.
> > +- regmap-val-endian: value endianness, see ../endianness/endianness.txt for
>
> I'm not familiar with regmap. What is the difference between register
> and value endianness?
>
Sorry for late, I'm very busy these days.
The register endianness here is used for the I2C and SPI protocol, which will
Send the register address(which maybe 8-bit or 16-bit) before its values.
BRs
Xiubo
next prev parent reply other threads:[~2014-04-28 8:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 6:46 [PATCHv2 0/3] add DT endianness binding support Xiubo Li
2014-04-23 6:46 ` [PATCHv2 1/3] dt/bindings: Add the DT binding documentation for endianness Xiubo Li
2014-04-23 8:34 ` Mark Rutland
2014-04-30 5:08 ` Li.Xiubo
2014-04-23 6:46 ` [PATCHv2 2/3] regmap: " Xiubo Li
2014-04-23 8:40 ` Mark Rutland
2014-04-28 8:52 ` Li.Xiubo [this message]
2014-04-23 6:46 ` [PATCHv2 3/3] regmap: add DT endianness binding support Xiubo Li
-- strict thread matches above, loose matches on Subject: below --
2014-04-02 10:09 [PATCHv2 0/3] regmap: add LE and DT binding for endianness Xiubo Li
2014-04-02 10:09 ` [PATCHv2 2/3] regmap: Add the DT binding documentation " Xiubo Li
2014-04-02 19:48 ` Mark Brown
2014-04-03 7:04 ` Li.Xiubo
2014-04-14 21:09 ` Mark Brown
2014-04-23 5:08 ` 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=39a09c53860c41248d2fd475c3691cd8@BY2PR03MB505.namprd03.prod.outlook.com \
--to=li.xiubo@freescale.com \
--cc=Pawel.Moll@arm.com \
--cc=broonie@kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rob@landley.net \
--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
all inboxes | Powered by JetHome®