From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Mark Brown <broonie@kernel.org>,
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] regmap: fix of_regmap_get_endian()
Date: Tue, 19 Aug 2014 07:21:45 +0200 [thread overview]
Message-ID: <20140819052141.GA12859@ulmo> (raw)
In-Reply-To: <1408400044-2560-1-git-send-email-swarren@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 2845 bytes --]
On Mon, Aug 18, 2014 at 04:14:04PM -0600, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Commit d647c199510c ("regmap: add DT endianness binding support") has
> some issues. Specifically, if config->reg_format_endian is not explicitly
> set, it will be zero, i.e. REGMAP_ENDIAN_DEFAULT. The switch statement
> that looks up the *endian from DT for the type==REGMAP_ENDIAN_VAL case
> doesn't change *endian in the type==REGMAP_ENDIAN_REG case. However, the
> test immediately following, compares *endian against REGMAP_ENDIAN_NATIVE,
> and if not equal, returns *endian as is. This ends up returning
> REGMAP_ENDIAN_DEFAULT, which the calling code does not expect, eventually
> leading to e.g.:
>
> Unable to handle kernel NULL pointer dereference at virtual address 00000024
> ...
> [<c02efd64>] (regcache_cache_only) from [<c0465fa8>] (tegra30_ahub_probe+0x1b8/0x430)
> [<c0465fa8>] (tegra30_ahub_probe) from [<c02e196c>] (platform_drv_probe+0x2c/0x5c)
> [<c02e196c>] (platform_drv_probe) from [<c02e0580>] (driver_probe_device+0x10c/0x22c)
> [<c02e0580>] (driver_probe_device) from [<c02e072c>] (__driver_attach+0x8c/0x90)
>
> This patch solves this by:
> * When looking up the endianness from DT, don't change *endian at all if
> there is no DT property; leave it set to REGMAP_ENDIAN_DEFAULT so the
> code falls through to other data sources in the same way as before.
> Now, the "unspecified" case acts the same for both REGMAP_ENDIAN_REG and
> REGMAP_ENDIAN_VAL.
> * After potentially looking up the endianness from DT, check *endian
> against REGMAP_ENDIAN_DEFAULT instead of REGMAP_ENDIAN_NATIVE to avoid
> returning unexpected values.
>
> Also, clean up the code a bit:
>
> * Make the comments briefer, and only refer to the specific action taken
> at their location. This makes most of the comments independent of DT,
> and easier to follow.
> * Restore the overall default of REGMAP_ENDIAN_BIG if none of the config,
> DT, or the bus specify any endianness. Since all busses specify an
> endianness now, this makes no difference, but I saw no justification in
> the patch description for changing the default default.
> * s/of_regmap_get_endian/regmap_get_endian/ since the function isn't DT-
> specific, even if the reason it was originally added was to add some
> DT-specific features.
>
> Reported-by: Thierry Reding <treding@nvidia.com>
> Fixes: d647c199510c ("regmap: add DT endianness binding support")
> Cc: Xiubo Li <Li.Xiubo@freescale.com>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> drivers/base/regmap/regmap.c | 58 ++++++++++++++------------------------------
> 1 file changed, 18 insertions(+), 40 deletions(-)
Thanks for fixing this, Stephen.
Tested-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-19 5:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 22:14 [PATCH] regmap: fix of_regmap_get_endian() Stephen Warren
2014-08-19 5:21 ` Thierry Reding [this message]
2014-08-19 5:43 ` Li.Xiubo
2014-08-19 15:34 ` Mark Brown
2014-08-19 16:14 ` Stephen Warren
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=20140819052141.GA12859@ulmo \
--to=thierry.reding@gmail.com \
--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 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.