From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: javierm@redhat.com, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 1/2] drm/ofdrm: Cast PCI IDs to u32 for comparing
Date: Thu, 27 Oct 2022 15:07:25 +0200 [thread overview]
Message-ID: <5987066.DvuYhMxLoT@steina-w> (raw)
In-Reply-To: <20221027115707.17980-2-tzimmermann@suse.de>
Hello Thomas,
Am Donnerstag, 27. Oktober 2022, 13:57:06 CEST schrieb Thomas Zimmermann:
> Properties of 32-bit integers are returned from the OF device tree
> as type __be32. Cast PCI vendor and device IDs from __be32 to u32
> before comparing them to constants. Fixes sparse warnings shown below.
>
> drivers/gpu/drm/tiny/ofdrm.c:237:17: warning: restricted __be32 degrades
> to integer drivers/gpu/drm/tiny/ofdrm.c:238:18: warning: restricted __be32
> degrades to integer drivers/gpu/drm/tiny/ofdrm.c:238:54: warning:
> restricted __be32 degrades to integer
>
> See [1] for the bug report.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> Link: https://lore.kernel.org/dri-devel/202210192208.D888I6X7-lkp@intel.com/
> # [1] ---
> drivers/gpu/drm/tiny/ofdrm.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/tiny/ofdrm.c b/drivers/gpu/drm/tiny/ofdrm.c
> index 0e1cc2369afcc..0da8b248ccc6e 100644
> --- a/drivers/gpu/drm/tiny/ofdrm.c
> +++ b/drivers/gpu/drm/tiny/ofdrm.c
> @@ -231,8 +231,11 @@ static u64 display_get_address_of(struct drm_device
> *dev, struct device_node *of return address;
> }
>
> -static bool is_avivo(__be32 vendor, __be32 device)
> +static bool is_avivo(__be32 vendor_id, __be32 device_id)
> {
> + u32 vendor = (__force u32)vendor_id;
> + u32 device = (__force u32)device_id;
I don't have much context, but just from reading this, shouldn't this be
be32_to_cpu() instead?
Best regards,
Alexander
> +
> /* This will match most R5xx */
> return (vendor == PCI_VENDOR_ID_ATI) &&
> ((device >= PCI_VENDOR_ID_ATI_R520 && device < 0x7800) ||
next prev parent reply other threads:[~2022-10-27 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 11:57 [PATCH 0/2] drm/ofdrm: Fix sparse warnings Thomas Zimmermann
2022-10-27 11:57 ` [PATCH 1/2] drm/ofdrm: Cast PCI IDs to u32 for comparing Thomas Zimmermann
2022-10-27 13:07 ` Alexander Stein [this message]
2022-10-27 14:04 ` Thomas Zimmermann
2022-10-28 6:33 ` Alexander Stein
2022-10-28 6:59 ` Thomas Zimmermann
2022-10-27 11:57 ` [PATCH 2/2] drm/ofdrm: Cast error pointers to void __iomem * Thomas Zimmermann
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=5987066.DvuYhMxLoT@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=lkp@intel.com \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.