From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Borislav Petkov <bp@alien8.de>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
rafael@kernel.org, Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: DPTF_POWER and DPTF_PCH_FIVR
Date: Thu, 15 Oct 2020 13:31:55 +0200 [thread overview]
Message-ID: <d6cdf27b-04ef-7bc8-03ef-2115ca08bffe@intel.com> (raw)
In-Reply-To: <20201015095851.GB11838@zn.tnic>
On 10/15/2020 11:58 AM, Borislav Petkov wrote:
> On Thu, Oct 15, 2020 at 11:53:11AM +0200, Borislav Petkov wrote:
>> Dudes,
>>
>> what are those new symbols in Kconfig and why do they wanna get enabled
>> on my box when doing oldconfig? Depends on X86? Really, that widespread?
Well, they depend on ACPI too and it doesn't look like there is anything
more fine grained that could be used here.
Also I'm not sure if adding ACPI_DPTF (bool, disabled by default and
depending on x86) would help a lot.
>> The help text doesn't say why do I need this...
> And that thing in sysfs:
>
> "/sys/bus/platform/drivers/DPTF Platform Power"
>
> has spaces in the name. What's going on?!
>
Obviously an oversight on my part, sorry.
I think that changing it to "dptf_power" (and analogously for the FIVR
participant driver) should work. Srinivas?
next parent reply other threads:[~2020-10-15 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201015095311.GA11838@zn.tnic>
[not found] ` <20201015095851.GB11838@zn.tnic>
2020-10-15 11:31 ` Rafael J. Wysocki [this message]
2020-10-15 12:06 ` DPTF_POWER and DPTF_PCH_FIVR Borislav Petkov
2020-10-15 12:28 ` Rafael J. Wysocki
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=d6cdf27b-04ef-7bc8-03ef-2115ca08bffe@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=bp@alien8.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).