mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Sui Jingfeng <suijingfeng@loongson.cn>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Li Yi <liyi@loongson.cn>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	loongson-kernel@lists.loongnix.cn,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] drm/loongson: Fix two warnings because of passing wrong type
Date: Mon, 10 Jul 2023 12:36:20 +0200	[thread overview]
Message-ID: <3742bddc-51b5-71c9-4d4a-ec15d17a515a@suse.de> (raw)
In-Reply-To: <20230710100931.255234-1-suijingfeng@loongson.cn>


[-- Attachment #1.1: Type: text/plain, Size: 2296 bytes --]

Hi

Am 10.07.23 um 12:09 schrieb Sui Jingfeng:
> When accessing I/O memory, we should pass '__iomem *' type instead of
> 'void *' simply, otherwise sparse tests will complain. After applied
> this patch, the following two sparse warnings got fixed.
> 
> 1) drivers/gpu/drm/loongson/lsdc_benchmark.c:27:35:
>     sparse:     expected void volatile [noderef] __iomem *
>     sparse:     got void *kptr
> 
> 2) drivers/gpu/drm/loongson/lsdc_benchmark.c:42:51:
>     sparse:     expected void const volatile [noderef] __iomem *
>     sparse:     got void *kptr
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202307100243.v3hv6aes-lkp@intel.com/
> Signed-off-by: Sui Jingfeng <suijingfeng@loongson.cn>
> ---
>   drivers/gpu/drm/loongson/lsdc_benchmark.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/loongson/lsdc_benchmark.c b/drivers/gpu/drm/loongson/lsdc_benchmark.c
> index b088646a2ff9..36e352820bdb 100644
> --- a/drivers/gpu/drm/loongson/lsdc_benchmark.c
> +++ b/drivers/gpu/drm/loongson/lsdc_benchmark.c
> @@ -24,7 +24,7 @@ static void lsdc_copy_gtt_to_vram_cpu(struct lsdc_bo *src_bo,
>   	lsdc_bo_kmap(dst_bo);
>   
>   	while (n--)
> -		memcpy_toio(dst_bo->kptr, src_bo->kptr, size);
> +		memcpy_toio((void __iomem *)dst_bo->kptr, src_bo->kptr, size);

If this is I/O memory, better add the __iomem qualifier to dst_bo->kptr 
rather than casting here. If if can be both, you could use an unnamed 
union like this:

struct lscd_bo {
   union {
     void __iomem *kptr_iomem;
     void *kptr;
   };
};

Best regards
Thomas

>   
>   	lsdc_bo_kunmap(src_bo);
>   	lsdc_bo_kunmap(dst_bo);
> @@ -39,7 +39,7 @@ static void lsdc_copy_vram_to_gtt_cpu(struct lsdc_bo *src_bo,
>   	lsdc_bo_kmap(dst_bo);
>   
>   	while (n--)
> -		memcpy_fromio(dst_bo->kptr, src_bo->kptr, size);
> +		memcpy_fromio(dst_bo->kptr, (void __iomem *)src_bo->kptr, size);
>   
>   	lsdc_bo_kunmap(src_bo);
>   	lsdc_bo_kunmap(dst_bo);

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      parent reply	other threads:[~2023-07-10 10:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 10:09 Sui Jingfeng
2023-07-10 10:26 ` Jani Nikula
2023-07-10 13:10   ` suijingfeng
2023-07-11  8:03     ` Jani Nikula
2023-07-10 13:50   ` suijingfeng
2023-07-10 10:36 ` Thomas Zimmermann [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=3742bddc-51b5-71c9-4d4a-ec15d17a515a@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liyi@loongson.cn \
    --cc=lkp@intel.com \
    --cc=loongson-kernel@lists.loongnix.cn \
    --cc=suijingfeng@loongson.cn \
    /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

all inboxes | Powered by JetHome®