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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140820080549.GA15414@ulmo>
Date:	Wed, 20 Aug 2014 10:05:50 +0200
From:	Thierry Reding <thierry.reding@...il.com>
To:	Xiubo Li <Li.Xiubo@...escale.com>
Cc:	broonie@...nel.org, mark.rutland@....com, robh+dt@...nel.org,
	pawel.moll@....com, ijc+devicetree@...lion.org.uk,
	galak@...eaurora.org, gregkh@...uxfoundation.org,
	linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
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@...escale.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

Content of type "application/pgp-signature" skipped