From: "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: "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: Thu, 3 Apr 2014 07:04:00 +0000 [thread overview]
Message-ID: <bebf1cf679014e62b1f4ad3fa970b52f@BY2PR03MB505.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20140402194812.GK14763@sirena.org.uk>
> Subject: Re: [PATCHv2 2/3] regmap: Add the DT binding documentation for
> endianness
>
> On Wed, Apr 02, 2014 at 06:09:08PM +0800, Xiubo Li wrote:
>
> > +sai2: sai@40031000 {
> > + compatible = "fsl,vf610-sai";
> > + reg = <0x40031000 0x1000>;
> > + ...
> > + val-endian = 'LE';
> > +};
>
> This is mostly OK as a binding (though it should be CCed to the DT list
> and maintiners as all DT bindings should) except using upper case
> doesn't really seem idiomatic for DT - lower case is more normal -
I will your advices.
> and I
> don't think we can make these properties mandatory in themselves.
> Individual bindings would need to make them mandatory. It's also odd to
> have a mandatory property which may be absent!
Well, yes, It is.
The absent one is just to compatible with the old drivers.
>
> It'd probably be better if the binding defined what the default
> endianess was too, or just didn't say what happens in cases where
> nothing is specified, the latter seems better.
I will think it over carefully.
> Generally just not
> mentioning regmap is better for a binding definition, the binding should
> be usable by all OSs and not just Linux.
How about move the endianness OF parsing to the driver/of/ ?
Is this will be better ?
Thanks,
BRs
Xiubo
next prev parent reply other threads:[~2014-04-03 7:04 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 ` [PATCHv2 2/3] regmap: Add the DT binding documentation for endianness Xiubo Li
2014-04-02 19:48 ` Mark Brown
2014-04-03 7:04 ` Li.Xiubo [this message]
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=bebf1cf679014e62b1f4ad3fa970b52f@BY2PR03MB505.namprd03.prod.outlook.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®