Re: [PATCH] soc: qcom: smp2p: fix __iomem annotation on entry->value pointer

[Bjorn Andersson]

On Tue, 23 Jun 2026 09:59:31 +0100, Ben Dooks wrote:
> The entry->value is passed to readl() so should be marked __iomem
> so remove these sparse warnings by marking it __iomem and do the
> relevant casting to ensure no further warnings:
> 
> drivers/soc/qcom/smp2p.c:280:64: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smp2p.c:280:64:    expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smp2p.c:280:64:    got unsigned int [usertype] *value
> drivers/soc/qcom/smp2p.c:318:34: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smp2p.c:318:34:    expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smp2p.c:318:34:    got unsigned int [usertype] *value
> drivers/soc/qcom/smp2p.c:446:26: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smp2p.c:446:26:    expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smp2p.c:446:26:    got unsigned int [usertype] *value
> drivers/soc/qcom/smp2p.c:501:33: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smp2p.c:501:33:    expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smp2p.c:501:33:    got unsigned int [usertype] *value
> drivers/soc/qcom/smp2p.c:504:26: warning: incorrect type in argument 2 (different address spaces)
> drivers/soc/qcom/smp2p.c:504:26:    expected void volatile [noderef] __iomem *addr
> drivers/soc/qcom/smp2p.c:504:26:    got unsigned int [usertype] *value
> 
> [...]

Applied, thanks!

[1/1] soc: qcom: smp2p: fix __iomem annotation on entry->value pointer
      commit: c5b0ca559afa50ce4ab39e85da927261814373e2

Best regards,
-- 
Bjorn Andersson <andersson@xxxxxxxxxx>