Re: [PATCH] soc: qcom: smsm: fix __iomem annotations
From: Bjorn Andersson
Date: Mon Aug 31 2026 - 16:42:52 EST
On Tue, 23 Jun 2026 10:09:54 +0100, Ben Dooks wrote:
> There are a number of points in the driver which miss out
> on __iomem annotations, so add these to remove the following
> sparse warnings:
>
> drivers/soc/qcom/smsm.c:159:32: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:159:32: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:159:32: got unsigned int [usertype] *local_state
> drivers/soc/qcom/smsm.c:171:25: warning: incorrect type in argument 2 (different address spaces)
> drivers/soc/qcom/smsm.c:171:25: expected void volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:171:25: got unsigned int [usertype] *local_state
> drivers/soc/qcom/smsm.c:181:48: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:181:48: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:181:48: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:219:26: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:219:26: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:219:26: got unsigned int [usertype] *remote_state
> drivers/soc/qcom/smsm.c:257:49: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:257:49: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:257:49: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:259:49: warning: incorrect type in argument 2 (different address spaces)
> drivers/soc/qcom/smsm.c:259:49: expected void volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:259:49: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:280:24: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:280:24: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:280:24: got unsigned int [usertype] *remote_state
> drivers/soc/qcom/smsm.c:288:49: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:288:49: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:288:49: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:290:49: warning: incorrect type in argument 2 (different address spaces)
> drivers/soc/qcom/smsm.c:290:49: expected void volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:290:49: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:330:26: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:330:26: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:330:26: got unsigned int [usertype] *remote_state
> drivers/soc/qcom/smsm.c:635:47: warning: incorrect type in argument 2 (different address spaces)
> drivers/soc/qcom/smsm.c:635:47: expected void volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:635:47: got unsigned int [usertype] *
>
> [...]
Applied, thanks!
[1/1] soc: qcom: smsm: fix __iomem annotations
commit: c84cdd308471d6ae4f8121660436a4fed8126709
Best regards,
--
Bjorn Andersson <andersson@xxxxxxxxxx>