From: Hans de Goede <hdegoede@redhat.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix DISP_POS_Y and DISP_HEIGHT defines
Date: Wed, 20 Apr 2022 17:32:43 +0200 [thread overview]
Message-ID: <60452154-8aab-b15d-1dff-29d3fa732f22@redhat.com> (raw)
In-Reply-To: <YmASniwe39jj1miR@intel.com>
Hi Ville,
On 4/20/22 16:03, Ville Syrjälä wrote:
> On Mon, Apr 18, 2022 at 05:09:36PM +0200, Hans de Goede wrote:
>> Commit 428cb15d5b00 ("drm/i915: Clean up pre-skl primary plane registers")
>> introduced DISP_POS_Y and DISP_HEIGHT defines but accidentally set these
>> their masks to REG_GENMASK(31, 0) instead of REG_GENMASK(31, 16).
>>
>> This breaks the primary display pane on at least pineview machines, fix
>> the mask to fix the primary display pane only showing black.
>>
>> Tested on an Acer One AO532h with an Intel N450 SoC.
>>
>> Fixes: 428cb15d5b00 ("drm/i915: Clean up pre-skl primary plane registers")
>> Cc: José Roberto de Souza <jose.souza@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> Note this fixes a regression in 5.18-rc# and I'm not entirely sure what
>> the procedure is here. Once I get a Reviewed-by or Acked-by and I push
>> this to drm-intel-next (where it also is necessary), should I then also
>> push it to drm-intel-fixes or will the current drm-intel-fixes
>> maintainer pick it up?
>> ---
>> drivers/gpu/drm/i915/i915_reg.h | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
>> index 51f46fe45c72..5f1f38684d65 100644
>> --- a/drivers/gpu/drm/i915/i915_reg.h
>> +++ b/drivers/gpu/drm/i915/i915_reg.h
>> @@ -4352,12 +4352,12 @@
>> #define _DSPAADDR 0x70184
>> #define _DSPASTRIDE 0x70188
>> #define _DSPAPOS 0x7018C /* reserved */
>> -#define DISP_POS_Y_MASK REG_GENMASK(31, 0)
>> +#define DISP_POS_Y_MASK REG_GENMASK(31, 16)
>
> Doh. I guess I only tested it on plane A where the plane gets its size
> from PIPESRC instead. And looks like the failure mode is such that
> the likes of kms_plane/pixel-formats still gets consistent looking CRCs
> even with the misconfigured plane size :/
>
> Thanks for the fix. Pushed to drm-intel-next.
Thank you pushing this out, will you (or someone else from Intel)
also take care of getting this on its way to 5.18-rc# ?
Regards,
Hans
>
>> #define DISP_POS_Y(y) REG_FIELD_PREP(DISP_POS_Y_MASK, (y))
>> #define DISP_POS_X_MASK REG_GENMASK(15, 0)
>> #define DISP_POS_X(x) REG_FIELD_PREP(DISP_POS_X_MASK, (x))
>> #define _DSPASIZE 0x70190
>> -#define DISP_HEIGHT_MASK REG_GENMASK(31, 0)
>> +#define DISP_HEIGHT_MASK REG_GENMASK(31, 16)
>> #define DISP_HEIGHT(h) REG_FIELD_PREP(DISP_HEIGHT_MASK, (h))
>> #define DISP_WIDTH_MASK REG_GENMASK(15, 0)
>> #define DISP_WIDTH(w) REG_FIELD_PREP(DISP_WIDTH_MASK, (w))
>> --
>> 2.35.1
>
next prev parent reply other threads:[~2022-04-20 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 15:09 [Intel-gfx] [PATCH] drm/i915: Fix DISP_POS_Y and DISP_HEIGHT defines Hans de Goede
2022-04-18 15:27 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-04-18 15:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-18 17:20 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-18 18:15 ` [Intel-gfx] [PATCH] " Souza, Jose
2022-04-20 14:03 ` Ville Syrjälä
2022-04-20 15:32 ` Hans de Goede [this message]
2022-04-20 16:23 ` Ville Syrjälä
2022-04-21 6:36 ` Joonas Lahtinen
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=60452154-8aab-b15d-1dff-29d3fa732f22@redhat.com \
--to=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@linux.intel.com \
/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