stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Wentland, Harry" <Harry.Wentland@amd.com>
Subject: Re: [PATCH] drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2
Date: Thu, 27 Jan 2022 16:47:57 +0100	[thread overview]
Message-ID: <YfK+rc4mowKwp4VM@kroah.com> (raw)
In-Reply-To: <BL1PR12MB5157FC7109F99B0D2DB265B5E25F9@BL1PR12MB5157.namprd12.prod.outlook.com>

On Tue, Jan 25, 2022 at 03:52:47PM +0000, Limonciello, Mario wrote:
> [Public]
> 
> > -----Original Message-----
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Tuesday, January 25, 2022 09:50
> > To: Limonciello, Mario <Mario.Limonciello@amd.com>
> > Cc: stable@vger.kernel.org; Deucher, Alexander
> > <Alexander.Deucher@amd.com>; Wentland, Harry
> > <Harry.Wentland@amd.com>
> > Subject: Re: [PATCH] drm/amdgpu: Use correct VIEWPORT_DIMENSION for
> > DCN2
> > 
> > On Tue, Jan 25, 2022 at 09:21:11AM -0600, Mario Limonciello wrote:
> > > For some reason this file isn't using the appropriate register
> > > headers for DCN headers, which means that on DCN2 we're getting
> > > the VIEWPORT_DIMENSION offset wrong.
> > >
> > > This means that we're not correctly carving out the framebuffer
> > > memory correctly for a framebuffer allocated by EFI and
> > > therefore see corruption when loading amdgpu before the display
> > > driver takes over control of the framebuffer scanout.
> > >
> > > Fix this by checking the DCE_HWIP and picking the correct offset
> > > accordingly.
> > >
> > > Long-term we should expose this info from DC as GMC shouldn't
> > > need to know about DCN registers.
> > >
> > > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> > > (cherry picked from commit dc5d4aff2e99c312df8abbe1ee9a731d2913bc1b)
> > > ---
> > > This is backported from 5.17-rc1, but doesn't backport cleanly because
> > > v5.16 changed to IP version harvesting for ASIC detection.  5.15.y doesn't
> > > have this.
> > >  drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 14 +++++++++++++-
> > >  1 file changed, 13 insertions(+), 1 deletion(-)
> > 
> > What stable tree(s) do you want this applied to?
> > 
> 
> The original commit it was cherry-picked from was CC to @stable and it
> should have applied to 5.16 from that. 
> 
> This fixed commit should go into 5.15.y.

Thanks, now queued up.

> > And what happened to the original signed-off-by's on the original
> > commit?
> 
> I dropped them because I had to change code to do the backport, it didn't seem reasonable
> to me to keep all of their ACK's/signed-off-by's on the code still.
> 
> If that's incorrect, please let me know and I can re-send with the exact same commit message.

Please keep them.  I've fixed this up for now, so no need for a resend.

thanks,

greg k-h

      reply	other threads:[~2022-01-27 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 15:21 [PATCH] drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2 Mario Limonciello
2022-01-25 15:46 ` Limonciello, Mario
2022-01-25 15:50 ` Greg KH
2022-01-25 15:52   ` Limonciello, Mario
2022-01-27 15:47     ` Greg KH [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=YfK+rc4mowKwp4VM@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Alexander.Deucher@amd.com \
    --cc=Harry.Wentland@amd.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).