From: Mikko Perttunen <mikko.perttunen@kapsi.fi>
To: Eduardo Valentin <edubezval@gmail.com>,
Mikko Perttunen <mperttunen@nvidia.com>
Cc: rui.zhang@intel.com, swarren@wwwdotorg.org,
thierry.reding@gmail.com, linux-pm@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, juha-matti.tilli@iki.fi
Subject: Re: [PATCH v5 4/4] thermal: Add Tegra SOCTHERM thermal management driver
Date: Wed, 24 Sep 2014 22:32:13 +0300 [thread overview]
Message-ID: <54231C3D.6040900@kapsi.fi> (raw)
In-Reply-To: <20140924191829.GA16529@developer>
On 09/24/2014 10:18 PM, Eduardo Valentin wrote:
>
> Mikko,
>
> On Thu, Aug 21, 2014 at 01:17:22PM +0300, Mikko Perttunen wrote:
>> ...
>> +
>> +static int enable_tsensor(struct tegra_soctherm *tegra,
>> + const struct tegra_tsensor *sensor,
>> + struct tsensor_shared_calibration shared)
>> +{
>> + void * __iomem base = tegra->regs + sensor->base;
>
> I get sparse complaining about this declaration. For the sake of keeping
> a clean static checks, can you please:
> - void * __iomem base = tegra->regs + sensor->base;
> + void __iomem * base = tegra->regs + sensor->base;
>
Sure.
>
> Can you also please check the remaining sparse errors?
> CHECK drivers/thermal/tegra_soctherm.c
> drivers/thermal/tegra_soctherm.c:260:43: warning: incorrect type in
> initializer (different address spaces)
> drivers/thermal/tegra_soctherm.c:260:43: expected void *[noderef]
> <asn:2>base
> drivers/thermal/tegra_soctherm.c:260:43: got void [noderef]
> <asn:2>*
> drivers/thermal/tegra_soctherm.c:271:9: warning: incorrect type in
> argument 2 (different address spaces)
> drivers/thermal/tegra_soctherm.c:271:9: expected void volatile
> [noderef] <asn:2>*addr
> drivers/thermal/tegra_soctherm.c:271:9: got void *
> drivers/thermal/tegra_soctherm.c:279:9: warning: incorrect type in
> argument 2 (different address spaces)
> drivers/thermal/tegra_soctherm.c:279:9: expected void volatile
> [noderef] <asn:2>*addr
> drivers/thermal/tegra_soctherm.c:279:9: got void *
> drivers/thermal/tegra_soctherm.c:281:9: warning: incorrect type in
> argument 2 (different address spaces)
> drivers/thermal/tegra_soctherm.c:281:9: expected void volatile
> [noderef] <asn:2>*addr
> drivers/thermal/tegra_soctherm.c:281:9: got void *
> drivers/thermal/tegra_soctherm.c:347:25: warning: incorrect type in
> argument 1 (different address spaces)
> drivers/thermal/tegra_soctherm.c:347:25: expected void const *ptr
> drivers/thermal/tegra_soctherm.c:347:25: got void [noderef]
> <asn:2>*regs
> drivers/thermal/tegra_soctherm.c:349:37: warning: incorrect type in
> argument 1 (different address spaces)
> drivers/thermal/tegra_soctherm.c:349:37: expected void const *ptr
> drivers/thermal/tegra_soctherm.c:349:37: got void [noderef]
> <asn:2>*regs
> drivers/thermal/tegra_soctherm.c:271:9: warning: dereference of
> noderef expression
> drivers/thermal/tegra_soctherm.c:279:9: warning: dereference of
> noderef expression
> drivers/thermal/tegra_soctherm.c:281:9: warning: dereference of
> noderef expression
>
Most of these seem to be caused by the above-mentioned swapping of
__iomem and *. The ones on lines 347 and 349 are more peculiar, though.
Apparently sparse doesn't like using IS_ERR and PTR_ERR on the void
__iomem * pointer returned by devm_ioremap_resource. Looks like this has
been discussed before (https://lkml.org/lkml/2013/6/17/216) and sparse
should have been patched to ignore this situation, so I'm not sure why
it's complaining about it. Anyway, there shouldn't be any issue here.
Mikko
next prev parent reply other threads:[~2014-09-24 19:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 10:17 [PATCH v5 0/4] Tegra124 soctherm driver Mikko Perttunen
2014-08-21 10:17 ` [PATCH v5 1/4] of: Add bindings for nvidia,tegra124-soctherm Mikko Perttunen
2014-09-24 18:40 ` Eduardo Valentin
2014-09-24 19:43 ` Stephen Warren
2014-08-21 10:17 ` [PATCH v5 2/4] ARM: tegra: Add soctherm and thermal zones to Tegra124 device tree Mikko Perttunen
2014-08-21 10:17 ` [PATCH v5 3/4] ARM: tegra: Add thermal trip points for Jetson TK1 Mikko Perttunen
2014-09-24 18:32 ` Eduardo Valentin
2014-09-24 18:34 ` Mikko Perttunen
2014-09-24 18:41 ` Eduardo Valentin
2014-09-24 18:43 ` Mikko Perttunen
2014-09-24 18:48 ` Eduardo Valentin
2014-09-24 19:01 ` Mikko Perttunen
2014-10-03 19:57 ` Pavel Machek
2014-10-06 7:24 ` Peter De Schrijver
2014-08-21 10:17 ` [PATCH v5 4/4] thermal: Add Tegra SOCTHERM thermal management driver Mikko Perttunen
2014-09-24 19:18 ` Eduardo Valentin
2014-09-24 19:32 ` Mikko Perttunen [this message]
2014-09-24 23:24 ` Eduardo Valentin
2014-09-25 5:59 ` Thierry Reding
2014-09-25 7:55 ` Mikko Perttunen
2014-08-21 12:20 ` [PATCH v5 0/4] Tegra124 soctherm driver Juha-Matti Tilli
2014-08-21 16:01 ` Eduardo Valentin
2014-08-21 18:03 ` Juha-Matti Tilli
2014-08-27 15:36 ` Mikko Perttunen
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=54231C3D.6040900@kapsi.fi \
--to=mikko.perttunen@kapsi.fi \
--cc=edubezval@gmail.com \
--cc=juha-matti.tilli@iki.fi \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=rui.zhang@intel.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).