From: Jani Nikula <jani.nikula@linux.intel.com>
To: "René Herman" <rene.herman@gmail.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Arun R Murthy" <arun.r.murthy@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:42:50 +0300 [thread overview]
Message-ID: <57adde32e4fa7fc4c74d8cba39249af1399de609@intel.com> (raw)
In-Reply-To: <9436a617-ae53-4702-9ac3-27d9c1267626@gmail.com>
On Mon, 04 Aug 2025, René Herman <rene.herman@gmail.com> wrote:
> On 04-08-2025 10:21, Jani Nikula wrote:
>
>> On Sat, 02 Aug 2025, René Herman <rene.herman@gmail.com> wrote:
>
>>> I.e., could while working with the person with the hardware not figure
>>> out what the point of that i915_drrs_ctl would be if the system
>>> immediately enabled it again anyway, so Arun's approach seems to make
>>> sense to me.
>>
>> Hacking debugfs is not a fix, it's a hack.
>
> So I take it that's a no then on looking at/fixing the DRRS bug?
All I'm saying is that any fix must not depend on the user having to use
a debugfs or a module parameter. It needs to work out of the box.
BR,
Jani.
> Please
> don't get me wrong; as said to Arun as well, I have no experience with
> either this code or really anything concerning this technology even: I
> am assuming I'm missing something when I couldn't figure out why the
> DRRS disable CTL existed when the system activated it again immediately
> anyway.
>
> I am/was trying that help that user, and maybe you guys as to having
> this issue on the map; that already reported bug is 4 year's old, so it
> didn't seem to otherwise have a lot of traction.
>
> Kind regards,
> Rene
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-08-04 15:42 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 [this message]
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
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=57adde32e4fa7fc4c74d8cba39249af1399de609@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.