public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Vas Novikov <vasya.novikov@gmail.com>, stable@vger.kernel.org
Cc: regressions@lists.linux.dev,
	Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
	Suraj Kandpal <suraj.kandpal@intel.com>,
	Khaled Almahallawy <khaled.almahallawy@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Christian Heusel <christian@heusel.eu>
Subject: Re: [REGRESSION][BISECTED] intel iGPU with HDMI PLL stopped working at 1080p@120Hz 1efd5384
Date: Tue, 17 Jun 2025 16:50:57 +0300	[thread overview]
Message-ID: <72c9ef36e81ddce8a9e91c5f3652489f5fa2d78d@intel.com> (raw)
In-Reply-To: <33046593-17e3-4bdc-9d4a-94dc94ef5e81@gmail.com>

On Tue, 17 Jun 2025, Vas Novikov <vasya.novikov@gmail.com> wrote:
> Hi Jani and everyone,
>
> On 17/06/2025 12.33, Jani Nikula wrote:
>> Does [1] help?
>
> The patch works. (Applied on top of 6.16.0-rc2-1.1-mainline, built by 
> Christian @gromit who helped again.)
>
> The patch (or the new kernel) also have a side effect of xrandr allowing 
> a completely new refresh rate, ~144Hz. This new refresh also seems to 
> work (I cannot easily disambiguate 144 versus 120, but I can tell it's 
> not 60Hz). So as far as my hardware is concerned, this patch leaves the 
> whole system working in all scenarios that I've tested.

Thanks a lot for testing! Ankit will send a v2 of it, and I think we'll
have it in mainline and backported to stable in a few weeks.

There's no need to file that bug report, this will suffice.


BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-06-17 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 10:20 [REGRESSION][BISECTED] intel iGPU with HDMI PLL stopped working at 1080p@120Hz 1efd5384 Vas Novikov
2025-06-17 10:33 ` Jani Nikula
2025-06-17 13:43   ` Vas Novikov
2025-06-17 13:50     ` Jani Nikula [this message]
2025-06-18 13:33       ` Nautiyal, Ankit K

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=72c9ef36e81ddce8a9e91c5f3652489f5fa2d78d@intel.com \
    --to=jani.nikula@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=christian@heusel.eu \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=khaled.almahallawy@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=rodrigo.vivi@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=suraj.kandpal@intel.com \
    --cc=vasya.novikov@gmail.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