mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Varone, Dillon" <Dillon.Varone@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
	"LIPSKI, IVAN" <IVAN.LIPSKI@amd.com>,
	"Wheeler, Daniel" <Daniel.Wheeler@amd.com>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Liu, Wenjing" <Wenjing.Liu@amd.com>,
	Simona Vetter <simona@ffwll.ch>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: RE: [git pull] drm for 6.17-rc1
Date: Thu, 31 Jul 2025 13:57:29 +0000	[thread overview]
Message-ID: <CYYPR12MB8962F7B39D2CFE2AC0B3F2E3FE27A@CYYPR12MB8962.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CADnq5_NBM1Kso==+N=1xCjF+xiS7Vy4g47uvUN7sSWs8bontZQ@mail.gmail.com>

[AMD Official Use Only - AMD Internal Distribution Only]

Yes, that patch Alex linked should also fix the div by zero bug for ASIC's that don't support DSC.

RX580 I think was DCE11, which doesn't support DSC... so all the relevant clocks and caps should be zeroed and gracefully fail any of the DSC checks.

-Dillon

-----Original Message-----
From: Alex Deucher <alexdeucher@gmail.com>
Sent: Thursday, July 31, 2025 9:10 AM
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>; Varone, Dillon <Dillon.Varone@amd.com>; LIPSKI, IVAN <IVAN.LIPSKI@amd.com>; Wheeler, Daniel <Daniel.Wheeler@amd.com>; Deucher, Alexander <Alexander.Deucher@amd.com>; Liu, Wenjing <Wenjing.Liu@amd.com>; Simona Vetter <simona@ffwll.ch>; dri-devel <dri-devel@lists.freedesktop.org>; LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 6.17-rc1

On Thu, Jul 31, 2025 at 3:03 AM Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> On Wed, 30 Jul 2025 at 21:58, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > d7b618bc41ee3d44c070212dff93949702ede997 is the first bad commit
> >     drm/amd/display: Refactor DSC cap calculations
> >
> > Let me go see how painful it is to just revert it from top-of-tree.
>
> So with that reverted (didn't require a lot of fixing, only minor
> unrelated context added nearby later), current top-of-tree works for
> me again.
>
> The revert I used for testing attached just so people can see exactly
> what I did.
>
> It's late here, I wasn't getting any more work done today anyway, so
> I'll leave it like this for now.
>
> I can continue to do the merge window with this revert purely local
> for a while, so if somebody comes up with a proper fix, I can test
> that out.

I think it may be fixed here:
https://patchwork.freedesktop.org/patch/663973/

Alex

>
>             Linus

  reply	other threads:[~2025-07-31 13:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29 21:05 Dave Airlie
2025-07-31  3:05 ` Linus Torvalds
2025-07-31  3:39   ` Dave Airlie
2025-07-31  3:49     ` Linus Torvalds
2025-07-31  3:40   ` Linus Torvalds
2025-07-31  3:47     ` Dave Airlie
2025-07-31  3:52       ` Linus Torvalds
2025-07-31  4:02     ` Linus Torvalds
2025-07-31  4:21       ` Dave Airlie
2025-07-31  4:26         ` Linus Torvalds
2025-07-31  4:31           ` Linus Torvalds
2025-07-31  4:32           ` Dave Airlie
2025-07-31  4:36             ` Dave Airlie
2025-07-31  4:48               ` Linus Torvalds
2025-07-31  4:58                 ` Linus Torvalds
2025-07-31  5:07                   ` Linus Torvalds
2025-07-31 12:41                     ` Mario Limonciello
2025-07-31 13:09                     ` Alex Deucher
2025-07-31 13:57                       ` Varone, Dillon [this message]
2025-07-31 14:00                       ` Alex Deucher
2025-07-31 18:01                       ` Linus Torvalds
2025-07-31 19:04                         ` Alex Deucher
2025-07-31  5:10                   ` Dave Airlie
2025-07-31  3:11 ` pr-tracker-bot
2025-07-31 20:09   ` Miguel Ojeda
2025-07-31  7:01 ` Imre Deak

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=CYYPR12MB8962F7B39D2CFE2AC0B3F2E3FE27A@CYYPR12MB8962.namprd12.prod.outlook.com \
    --to=dillon.varone@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Daniel.Wheeler@amd.com \
    --cc=IVAN.LIPSKI@amd.com \
    --cc=Wenjing.Liu@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®