From: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: drm/tegra: Add hardware cursor support
Date: Fri, 17 Oct 2014 15:15:05 +0200 [thread overview]
Message-ID: <20141017131504.GB22700@ulmo.nvidia.com> (raw)
In-Reply-To: <20141017113123.GA24962@mwanda>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
On Fri, Oct 17, 2014 at 02:31:23PM +0300, Dan Carpenter wrote:
> Hello Thierry Reding,
>
> The patch e687651bc1ed: "drm/tegra: Add hardware cursor support" from
> Dec 20, 2013, leads to the following static checker warning:
>
> drivers/gpu/drm/tegra/dc.c:597 tegra_dc_cursor_set2()
> warn: mask and shift to zero
>
> drivers/gpu/drm/tegra/dc.c
> 594 if (bo) {
> 595 unsigned long addr = (bo->paddr & 0xfffffc00) >> 10;
> 596 #ifdef CONFIG_ARCH_DMA_ADDR_T_64BIT
> 597 unsigned long high = (bo->paddr & 0xfffffffc) >> 32;
How timely. I'm in fact revising this code at this very moment. =)
The masking here is indeed somewhat fishy. While it does the right
thing, it's also needless to some degree. A better version would be:
addr = (bo->paddr >> 10) & 0x3fffff;
Since this is written to a register where the upper 10 bits (actually
only 8 because bits 22 and 23 are reserved) are used for additional
control parameters (cursor size and clipping region). The above will
properly write bits 31:10 into bits 21:0 of addr.
For the upper 32 bits the mask is completely redundant. According to the
register documentation, bits 1:0 should correspond to bits 33:32 of the
physical address, so something like:
high = (bo->paddr >> 32) & 0x3;
would be more correct.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-10-17 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 11:31 drm/tegra: Add hardware cursor support Dan Carpenter
2014-10-17 13:15 ` Thierry Reding [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=20141017131504.GB22700@ulmo.nvidia.com \
--to=treding-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.