public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Cc: Alex Deucher <alexdeucher@gmail.com>,
	Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, "Siqueira,
	Rodrigo" <Rodrigo.Siqueira@amd.com>
Subject: Re: drm/amd/display: Pass pwrseq inst for backlight and ABM
Date: Mon, 2 Dec 2024 13:35:51 +0100	[thread overview]
Message-ID: <2024120231-untimely-undivided-e1d7@gregkh> (raw)
In-Reply-To: <1733138635@msgid.manchmal.in-ulm.de>

On Mon, Dec 02, 2024 at 12:33:48PM +0100, Christoph Biedl wrote:
> Alex Deucher wrote... [ back in January ]
> 
> > Please cherry pick upstream commit b17ef04bf3a4 ("drm/amd/display:
> > Pass pwrseq inst for backlight and ABM") to stable kernel 6.6.x and
> > newer.
> >
> > This fixes broken backlight adjustment on some AMD platforms with eDP panels.
> 
> Hello,
> 
> tl;dr: Was it possible to have this in 6.1.y?
> 
> after a lenghty bisect session it seems[1] this commit b17ef04bf3a4
> ("drm/amd/display: Pass pwrseq inst for backlight and ABM") indeed
> fixes an issue with a HP mt645[2]: Without it, the backlight stays at
> full brightness all the time, writing various values to the usual sysfs
> place has no effect.
> 
> That commit was backported to 6.6.y (as 71be0f674070) but not to 6.1.y -
> which is the series where I'd like to see that issue fixed. However, is
> does not apply, lot of failed hunks and missing files. So I was
> wondering whether it had been skipped deliberately because a backport
> was deemed impossible - or whether it might be doable with some
> more-than-usual effort. In the latter case, I might be willing to do the
> task, but quite frankly, lacking any understanding of what the code
> does, I'd only try to resolve the conflicts and check whether things
> work.
> 
> So I'd be glad if you could give me some insight here: Would it be worth
> the efforts trying to bring this to 6.1.y?

Why not just move to 6.6.y instead?  What's preventing that from
happening?

thanks,

greg k-h

  reply	other threads:[~2024-12-02 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 16:16 drm/amd/display: Pass pwrseq inst for backlight and ABM Alex Deucher
2024-01-17 16:49 ` Greg KH
2024-01-17 17:21   ` Alex Deucher
2024-01-18  9:57     ` Greg KH
2024-12-02 11:33 ` Christoph Biedl
2024-12-02 12:35   ` Greg KH [this message]
2024-12-05 13:02     ` Christoph Biedl
2024-12-05 14:11       ` Greg KH

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=2024120231-untimely-undivided-e1d7@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=linux-kernel.bfrz@manchmal.in-ulm.de \
    --cc=sashal@kernel.org \
    --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