linux-kernel - Re: [PATCH] Revert "clk: qcom: Specify LE device 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] [day] [month] [year] [list]

Message-ID: <7hsi0xzi1z.fsf@baylibre.com>
Date:	Fri, 12 Feb 2016 14:21:12 -0800
From:	Kevin Hilman <khilman@...libre.com>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Mike Turquette <mturquette@...libre.com>,
	linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
	Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] Revert "clk: qcom: Specify LE device endianness"

Stephen Boyd <sboyd@...eaurora.org> writes:

> This reverts commit 329cabcecf94d8d7821e729dda284ba9dec44c87.
>
> The commit that caused us to specify LE device endianness here,
> 29bb45f25ff3 (regmap-mmio: Use native endianness for read/write,
> 2015-10-29), has been reverted in mainline so now when we specify
> LE it actively breaks big endian kernels because the byte
> swapping in regmap-mmio is incorrect. Let's revert this change
> because it will 1) fix the big endian kernels and 2) be redundant
> to specify LE because that will become the default soon.
>
> Cc: Kevin Hilman <khilman@...aro.org>
> Cc: Mark Brown <broonie@...nel.org>
> Signed-off-by: Stephen Boyd <sboyd@...eaurora.org>

Tested-by: Kevin Hilman <khilman@...libre.com>

I verified that this gets apq8016-sbc booting again with mainline.

Kevin