Re: [PATCHv6 2/2] dt/bindings: Add the DT binding documentation for endianness

[Thierry Reding <thierry.reding@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]

On Wed, Aug 20, 2014 at 09:14:02AM +0000, Li.Xiubo@freescale.com wrote:
> > Subject: Re: [PATCHv6 2/2] dt/bindings: Add the DT binding documentation for
> > endianness
> > 
> > On Tue, Jul 15, 2014 at 12:23:03PM +0800, 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
> > 
> > Sorry for jumping in so late. I think this binding documentation needs
> > to be moved somewhere else. regmap is a Linux kernel specific
> > implementation detail and therefore has no place in device tree binding
> > descriptions. Furthermore the endianness properties described herein do
> > apply to drivers that don't use regmap.
> > 
> > Perhaps we need some top-level file that describes generic properties
> > such as this?
> > 
> > Thierry
> 
> Yes, I do agree.
> And there are many devices that have the endian issue without using the
> Regmap in our LS* SoCs.
> 
> And I also think one generic binding description of this will be much
> better.
> 
> Where should we place it? In Documentation/devicetree/bindings/, or...?

Documentation/devicetree/bindings/standard-properties.txt perhaps?

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]