From: Arnd Bergmann <arnd@arndb.de>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Stephen Boyd <sboyd@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
Kenneth Westfield <kwestfie@codeaurora.org>,
Kevin Hilman <khilman@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "ASoC: qcom: Specify LE device endianness"
Date: Fri, 12 Feb 2016 21:35:26 +0100 [thread overview]
Message-ID: <4609707.AR30v8FONr@wuerfel> (raw)
In-Reply-To: <20160212200311.GB11402@sirena.org.uk>
On Friday 12 February 2016 20:03:11 Mark Brown wrote:
> On Fri, Feb 12, 2016 at 08:48:58PM +0100, Arnd Bergmann wrote:
>
> > which all look like they are regmap_mmio users as well. Do they
> > suffer from the same problem?
>
> Probably, yes. It's only a problem if they're in systems that might
> otherwise run big endian successfully.
>
The affected clock drivers seem to include all the qcom platforms,
so I assumed that whatever platform uses sound/soc/qcom/lpass-cpu.c
has to use one of those as well. Same thing for drivers/nvmem/qfprom.c.
lpc32xx probably won't support big-endian.
syscon is probably fine because it only sets that flag based on the
"little-endian" DT property and I don't see anything setting that
(except the one platform that did so incorrectly).
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Revert "ASoC: qcom: Specify LE device endianness"
Date: Fri, 12 Feb 2016 21:35:26 +0100 [thread overview]
Message-ID: <4609707.AR30v8FONr@wuerfel> (raw)
In-Reply-To: <20160212200311.GB11402@sirena.org.uk>
On Friday 12 February 2016 20:03:11 Mark Brown wrote:
> On Fri, Feb 12, 2016 at 08:48:58PM +0100, Arnd Bergmann wrote:
>
> > which all look like they are regmap_mmio users as well. Do they
> > suffer from the same problem?
>
> Probably, yes. It's only a problem if they're in systems that might
> otherwise run big endian successfully.
>
The affected clock drivers seem to include all the qcom platforms,
so I assumed that whatever platform uses sound/soc/qcom/lpass-cpu.c
has to use one of those as well. Same thing for drivers/nvmem/qfprom.c.
lpc32xx probably won't support big-endian.
syscon is probably fine because it only sets that flag based on the
"little-endian" DT property and I don't see anything setting that
(except the one platform that did so incorrectly).
Arnd
next prev parent reply other threads:[~2016-02-12 20:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 17:30 [PATCH] Revert "ASoC: qcom: Specify LE device endianness" Stephen Boyd
2016-02-12 17:30 ` Stephen Boyd
2016-02-12 19:34 ` Mark Brown
2016-02-12 19:34 ` Mark Brown
2016-02-12 19:48 ` Arnd Bergmann
2016-02-12 19:48 ` Arnd Bergmann
2016-02-12 20:03 ` Mark Brown
2016-02-12 20:03 ` Mark Brown
2016-02-12 20:35 ` Arnd Bergmann [this message]
2016-02-12 20:35 ` Arnd Bergmann
2016-02-12 21:28 ` Mark Brown
2016-02-12 21:28 ` Mark Brown
2016-02-12 22:08 ` Stephen Boyd
2016-02-12 22:08 ` Stephen Boyd
2016-02-12 21:26 ` Mark Brown
2016-02-12 21:26 ` Mark Brown
2016-02-12 22:04 ` Stephen Boyd
2016-02-12 22:04 ` Stephen Boyd
2016-02-12 22:25 ` Mark Brown
2016-02-12 22:25 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4609707.AR30v8FONr@wuerfel \
--to=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=khilman@linaro.org \
--cc=kwestfie@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.