Commit dde7632e authored by Arnd Bergmann's avatar Arnd Bergmann Committed by Thomas Gleixner

clocksource/fsl: Avoid harmless 64-bit warnings

The ftm_clockevent_init passes the value of "~0UL" into a function
that takes a 32-bit argument, which drops the upper 32 bits, as
gcc warns about on ARM64:

clocksource/fsl_ftm_timer.c: In function 'ftm_clockevent_init':
clocksource/fsl_ftm_timer.c:206:13: warning: large integer implicitly truncated to unsigned type [-Woverflow]

This was obviously unintended behavior, and is easily avoided by
using '~0u' as the integer literal, because that is 32-bit wide
on all architectures.
Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org
Cc: Xiubo Li <Li.Xiubo@freescale.com>
Cc: Shawn Guo <shawnguo@kernel.org>
Cc: Sascha Hauer <kernel@pengutronix.de>
Cc: Stefan Agner <stefan@agner.ch>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: http://lkml.kernel.org/r/3990834.xnjhm37Grs@wuerfelSigned-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
parent 8005c49d
...@@ -203,7 +203,7 @@ static int __init ftm_clockevent_init(unsigned long freq, int irq) ...@@ -203,7 +203,7 @@ static int __init ftm_clockevent_init(unsigned long freq, int irq)
int err; int err;
ftm_writel(0x00, priv->clkevt_base + FTM_CNTIN); ftm_writel(0x00, priv->clkevt_base + FTM_CNTIN);
ftm_writel(~0UL, priv->clkevt_base + FTM_MOD); ftm_writel(~0u, priv->clkevt_base + FTM_MOD);
ftm_reset_counter(priv->clkevt_base); ftm_reset_counter(priv->clkevt_base);
...@@ -230,7 +230,7 @@ static int __init ftm_clocksource_init(unsigned long freq) ...@@ -230,7 +230,7 @@ static int __init ftm_clocksource_init(unsigned long freq)
int err; int err;
ftm_writel(0x00, priv->clksrc_base + FTM_CNTIN); ftm_writel(0x00, priv->clksrc_base + FTM_CNTIN);
ftm_writel(~0UL, priv->clksrc_base + FTM_MOD); ftm_writel(~0u, priv->clksrc_base + FTM_MOD);
ftm_reset_counter(priv->clksrc_base); ftm_reset_counter(priv->clksrc_base);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment