mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Tesarik <petr.tesarik@suse.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Petr Tesarik <petr.tesarik@suse.com>, Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: CPPC: add sysfs entry for guaranteed performance
Date: Fri, 21 Jun 2024 13:09:39 +0200	[thread overview]
Message-ID: <20240621130911.78e4eec1@mordecai.tesarici.cz> (raw)
In-Reply-To: <CAJZ5v0hBR1qGgSq3+sYU_7ChphHuL_R7E1-LBjXE3FdWUPkWpg@mail.gmail.com>

On Fri, 21 Jun 2024 12:16:06 +0200
"Rafael J. Wysocki" <rafael@kernel.org> wrote:

> On Fri, Jun 21, 2024 at 10:49 AM Petr Tesarik <petr.tesarik@suse.com> wrote:
> >
> > On Thu,  6 Jun 2024 13:55:41 +0200
> > Petr Tesarik <ptesarik@suse.com> wrote:
> >  
> > > Expose the CPPC guaranteed performance as reported by the platform through
> > > GuaranteedPerformanceRegister.
> > >
> > > The current value is already read in cppc_get_perf_caps() and stored in
> > > struct cppc_perf_caps (to be used by the intel_pstate driver), so only the
> > > attribute itself needs to be defined.  
> >
> > Are there any objections to exposing this CPPC register through sysfs?
> > I mean, if everybody is OK with it, the patch could be acked and queued
> > for 6.11, right?  
> 
> It actually has been queued already, sorry for the missing notice.
> 
> It's been in linux-next for some time even.

Oh, OK, I could have checked myself. ;-)

Thanks!
Petr T

      reply	other threads:[~2024-06-21 11:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 11:55 Petr Tesařík
2024-06-21  8:48 ` Petr Tesarik
2024-06-21 10:16   ` Rafael J. Wysocki
2024-06-21 11:09     ` Petr Tesarik [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=20240621130911.78e4eec1@mordecai.tesarici.cz \
    --to=petr.tesarik@suse.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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

all inboxes | Powered by JetHome®