public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Mike Turquette <mturquette@baylibre.com>,
	 linux-kernel@vger.kernel.org,  linux-clk@vger.kernel.org,
	 Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] Revert "clk: qcom: Specify LE device endianness"
Date: Fri, 12 Feb 2016 14:21:12 -0800	[thread overview]
Message-ID: <7hsi0xzi1z.fsf@baylibre.com> (raw)
In-Reply-To: <1455298060-15199-1-git-send-email-sboyd@codeaurora.org> (Stephen Boyd's message of "Fri, 12 Feb 2016 09:27:40 -0800")

Stephen Boyd <sboyd@codeaurora.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@linaro.org>
> Cc: Mark Brown <broonie@kernel.org>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>

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

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

Kevin

      reply	other threads:[~2016-02-12 22:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 17:27 [PATCH] Revert "clk: qcom: Specify LE device endianness" Stephen Boyd
2016-02-12 22:21 ` Kevin Hilman [this message]

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=7hsi0xzi1z.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox