summaryrefslogtreecommitdiffstats
path: root/virt
diff options
context:
space:
mode:
authorStephen Boyd <sboyd@codeaurora.org>2015-12-14 10:42:57 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-02-08 08:09:13 +0100
commit3b2b9ead32142b4cf55ea2793e5e4f7b63c04818 (patch)
tree01e10e2f69610c29a1ecea93452dccaaffd461c5 /virt
parentnvmem: core: return error for non word aligned access (diff)
downloadlinux-3b2b9ead32142b4cf55ea2793e5e4f7b63c04818.tar.xz
linux-3b2b9ead32142b4cf55ea2793e5e4f7b63c04818.zip
nvmem: qfprom: Specify LE device endianness
The qfprom is a little endian device, but so far we've been relying on the regmap mmio bus handling this for us without explicitly stating that fact. After commit 4a98da2164cf (regmap-mmio: Use native endianness for read/write, 2015-10-29), the regmap mmio bus will read/write with the __raw_*() IO accessors, instead of using the readl/writel() APIs that do proper byte swapping for little endian devices. So if we're running on a big endian processor and haven't specified the endianness explicitly in the regmap config or in DT, we're going to switch from doing little endian byte swapping to big endian accesses without byte swapping, leading to some confusing results. Specify the endianness explicitly so that the regmap core properly byte swaps the accesses for us. Cc: Rajendra Nayak <rnayak@codeaurora.org> Cc: Kevin Hilman <khilman@linaro.org> Cc: Tyler Baker <tyler.baker@linaro.org> Cc: Simon Arlott <simon@fire.lp0.eu> Cc: Mark Brown <broonie@kernel.org> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions