From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Stephen Warren <swarren@wwwdotorg.org>, Mark Brown <broonie@kernel.org>
Cc: Thierry Reding <treding@nvidia.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Stephen Warren <swarren@nvidia.com>,
Xiubo Li <Li.Xiubo@freescale.com>
Subject: Re: [PATCH V2] regmap: of_regmap_get_endian() cleanup
Date: Wed, 20 Aug 2014 11:33:15 +0200 [thread overview]
Message-ID: <53F46B5B.80400@collabora.co.uk> (raw)
In-Reply-To: <1408466947-26593-1-git-send-email-swarren@wwwdotorg.org>
Hello Stephen,
On 08/19/2014 06:49 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Commit d647c199510c ("regmap: add DT endianness binding support") had
> some issues. Commit ba1b53feb8ca ("regmap: Fix DT endianess parsing
> logic") fixed the main problem. This patch fixes the other.
>
> Specifically, restore the overall default of REGMAP_ENDIAN_BIG if none of
> the config, DT, or the bus specify any endianness. Without this,
> of_regmap_get_endian() could return REGMAP_ENDIAN_DEFAULT, which the
> calling code can't handle. Since all busses do specify an endianness in
> the current code, this makes no difference right now, but I saw no
> justification in the patch description for removing this final default.
>
Yes, I also wondered about the second issue you are mentioning when I was
fixing the main problem. But since Xiubo's patch also set
REGMAP_ENDIAN_BIG as default for both the I2C and SPI buses (making no
difference as you said) I assumed that the intention was to make buses to
explicitly define their default instead of rely on a global one so I just
kept that way.
But I agree with you that is better to go back to the default
REGMAP_ENDIAN_BIG as it used to be before since buses can change the
default if needed anyways.
Best regards,
Javier
prev parent reply other threads:[~2014-08-20 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 16:49 [PATCH V2] regmap: of_regmap_get_endian() cleanup Stephen Warren
2014-08-19 21:17 ` Mark Brown
2014-08-27 13:14 ` Geert Uytterhoeven
2014-08-27 21:07 ` Mark Brown
2014-08-20 9:33 ` Javier Martinez Canillas [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=53F46B5B.80400@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=Li.Xiubo@freescale.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=treding@nvidia.com \
/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