linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Tero Kristo <t-kristo@ti.com>,
	linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: ti: fapll: fix address space warnings
Date: Tue, 7 Jun 2016 17:13:26 +0100	[thread overview]
Message-ID: <20160607161326.GZ5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1465308337-18047-1-git-send-email-ben.dooks@codethink.co.uk>

On Tue, Jun 07, 2016 at 03:05:37PM +0100, Ben Dooks wrote:
> Fix the following warnings from casting "void __iomem *" pointers
> to u32 when using sparse:
> 
> drivers/clk/ti/fapll.c:583:13: warning: cast removes address space of expression
> drivers/clk/ti/fapll.c:623:21: warning: cast removes address space of expression

As a note of general principle, adding __force to casts is not the correct
way to solve these sparse warnings.

__force is supposed to be used in places which know that the cast is 100%
legitimate - in other words, architecture code removing the __iomem-ness
of the pointer so it can be dereferenced.  Sprinking the code with __force
to shut these warnings up doesn't actually help the cause.

> diff --git a/drivers/clk/ti/fapll.c b/drivers/clk/ti/fapll.c
> index 66a0d0e..d765f4a 100644
> --- a/drivers/clk/ti/fapll.c
> +++ b/drivers/clk/ti/fapll.c
> @@ -43,14 +43,14 @@
>  #define to_synth(_hw)		container_of(_hw, struct fapll_synth, hw)
>  
>  /* The bypass bit is inverted on the ddr_pll.. */
> -#define fapll_is_ddr_pll(va)	(((u32)(va) & 0xffff) == 0x0440)
> +#define fapll_is_ddr_pll(va)	(((u32 __force)(va) & 0xffff) == 0x0440)

This should be a cast to unsigned long, not u32.

>  
>  /*
>   * The audio_pll_clk1 input is hard wired to the 27MHz bypass clock,
>   * and the audio_pll_clk1 synthesizer is hardwared to 32KiHz output.
>   */
> -#define is_ddr_pll_clk1(va)	(((u32)(va) & 0xffff) == 0x044c)
> -#define is_audio_pll_clk1(va)	(((u32)(va) & 0xffff) == 0x04a8)
> +#define is_ddr_pll_clk1(va)	(((u32 __force)(va) & 0xffff) == 0x044c)
> +#define is_audio_pll_clk1(va)	(((u32 __force)(va) & 0xffff) == 0x04a8)

Ditto.

A cast from an __iomem pointer to unsigned long is permitted - no need
to use __force.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

      reply	other threads:[~2016-06-07 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 14:05 [PATCH] clk: ti: fapll: fix address space warnings Ben Dooks
2016-06-07 16:13 ` Russell King - ARM Linux [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=20160607161326.GZ5783@n2100.arm.linux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=ben.dooks@codethink.co.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@lists.codethink.co.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=t-kristo@ti.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).