From: Jani Nikula <jani.nikula@linux.intel.com>
To: "René Herman" <rene.herman@gmail.com>,
"Murthy, Arun R" <arun.r.murthy@intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Issue or bug concerning DRRS on old i7-4980HQ
Date: Mon, 04 Aug 2025 18:46:48 +0300 [thread overview]
Message-ID: <3e6e7022aa88f8097b6176068cf8bbe28587cb10@intel.com> (raw)
In-Reply-To: <b18e7718-95c4-4220-afd3-0bbde0fc21b1@gmail.com>
On Mon, 04 Aug 2025, René Herman <rene.herman@gmail.com> wrote:
> On 04-08-2025 10:48, Murthy, Arun R wrote:
>
>> On 02-08-2025 16:06, René Herman wrote:
>
>>> Although I'm not a graphics/display person, seems to me it's more
>>> or less fixed by Arun Murthy (added to the To: list) in the last,
>>> still recent-ish comment on that bug?
>>
>> This was a debug patch provided to root case the issue and not a
>> proper fix!
> OK, but it's a real question I have, not meant flippantly or anythng:
> what is then the idea of the DRRS CTL when it's enable/activated again
> immediately anyway? I'm not at all familiar with this code or even
> technology; I assume I'm missing something.
The debugfs is mainly for testing, where the scenarios that re-enable
DRRS are under control.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-08-04 15:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 2:49 Issue or bug concerning DRRS on old i7-4980HQ René Herman
2025-07-31 14:01 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2025-07-31 15:07 ` René Herman
2025-08-01 9:19 ` Jani Nikula
2025-08-02 10:36 ` René Herman
2025-08-04 8:21 ` Jani Nikula
2025-08-04 10:25 ` René Herman
2025-08-04 15:42 ` Jani Nikula
2025-08-04 15:53 ` René Herman
2025-08-04 16:03 ` Jani Nikula
2025-08-04 16:11 ` René Herman
2025-08-21 19:24 ` René Herman
2025-08-28 6:10 ` René Herman
2025-09-09 12:53 ` René Herman
2025-08-04 8:48 ` Murthy, Arun R
2025-08-04 10:12 ` René Herman
2025-08-04 15:46 ` Jani Nikula [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=3e6e7022aa88f8097b6176068cf8bbe28587cb10@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rene.herman@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.