linux-kernel - Re: [PATCH] regmap: fix documentation to match code

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] [day] [month] [year] [list]

Date:	Mon, 21 Mar 2016 08:14:28 -0500
From:	Rob Herring <robh@...nel.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Mark Brown <broonie@...nel.org>, Xiubo Li <Li.Xiubo@....com>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: fix documentation to match code

On Thu, Mar 17, 2016 at 06:23:40PM +0100, Arnd Bergmann wrote:
> The regmap binding talks about one thing, which is register
> endianess, and it gets almost every aspect of it wrong.
> 
> This replaces the current text of the file with a version
> that makes more sense and that matches what we implement
> now.
> 
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> Fixes: a06c488da0b0 ("regmap: Add explict native endian flag to DT bindings")
> Fixes: 275876e208e2 ("regmap: Add the DT binding documentation for endianness")

[...]

> +Note:
> +Regmap defaults to little-endian register access on MMIO based
> +devices, this is by far the most common setting. On CPU

This seems a bit Linux specific to me, but I guess if we are defining 
the binding to be this way it is fine.

Acked-by: Rob Herring <robh@...nel.org>

> +architectures that typically run big-endian operating systems
> +(e.g. PowerPC), registers can be defined as big-endian and must
> +be marked that way in the devicetree.