linux-kernel - Re: [PATCH] Revert "regmap-mmio: Use native endianness for read/write"

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]

Date:	Tue, 26 Jan 2016 20:05:17 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Johannes Berg <johannes@...solutions.net>,
	Simon Arlott <simon@...e.lp0.eu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Revert "regmap-mmio: Use native endianness for
 read/write"

On Tue, Jan 26, 2016 at 02:16:16PM +0100, Arnd Bergmann wrote:

> So if we default to little-endian for all regmap-mmio mappings, and let
> the driver or DT override that, and the regmap core already has the
> logic to read the ordering from DT, should we remove the parsing of 
> the byteorder attributes from syscon and just let regmap do its thing?

> I was thinking about adding the patch below, but it sounds like we can
> just remove the parsing completely.

Probably, yes.  I've got a patch for that now, just trying to work out
what to do to resolve the readl/writel thing without breaking MIPS which
is harder than it sounds without doing a proper fix (which I obviously
want to avoid in -rc).

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)