From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regmap: Fix the null function of format_val on regmap_bulk_read.
Date: Wed, 26 Aug 2015 13:35:56 +0100 [thread overview]
Message-ID: <20150826123556.GB2977@sirena.org.uk> (raw)
In-Reply-To: <1440589396-696-1-git-send-email-henryc.chen@mediatek.com>
On Wed, Aug 26, 2015 at 07:43:16PM +0800, Henry Chen wrote:
> The regmap_format will not be initialize if device driver not declare the regmap_bus
> when registering the regmap. To avoid the null function of format_val when
> called regmap_bulk_read(). It need to give a format function when regmap init.
> Call trace:
> [< (null)>] (null)
> [<ffffffc0004cbdd0>] mtk_rtc_read_time+0x9c/0x134
> [<ffffffc0004c9618>] __rtc_read_time.isra.3+0x40/0x7c
> [<ffffffc0004c9688>] rtc_read_time+0x34/0x58
Please don't paste entire backtraces in, they're enormous and tend to
obscure the actual content while adding little value. If needed then
edited highlights work better. I'm fairly sure I've mentioned this
before...
> @@ -783,8 +783,22 @@ struct regmap *regmap_init(struct device *dev,
> map->defer_caching = true;
> map->reg_write = _regmap_bus_raw_write;
> }
> +/*
> + * For bulk read, need to hook the format function.
> + */
> +simple_format_initialization:
The indentation is all messed up here, we're misssing a blank line and
the comment is not indented.
> -skip_format_initialization:
> + switch (config->val_bits) {
> + case 8:
> + map->format.format_val = regmap_format_8;
> + break;
> + case 16:
> + map->format.format_val = regmap_format_16_native;
> + break;
> + case 32:
> + map->format.format_val = regmap_format_32_native;
> + break;
> + }
Why are these format functions sensible? Converting a null pointer
dereference into data corruption wouldn't be ideal. The commit message
should really cover this.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150826/7785bcae/attachment.sig>
next prev parent reply other threads:[~2015-08-26 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 11:43 [PATCH] regmap: Fix the null function of format_val on regmap_bulk_read Henry Chen
2015-08-26 12:35 ` Mark Brown [this message]
2015-08-26 13:22 ` Markus Pargmann
2015-08-26 17:38 ` Mark Brown
2015-08-27 5:49 ` Markus Pargmann
2015-08-27 10:06 ` 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=20150826123556.GB2977@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).