From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Hoan Tran <hotran@apm.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
viresh.kumar@linaro.org, linux acpi <linux-acpi@vger.kernel.org>,
linux-pm@vger.kernel.org,
Ashwin Chaugule <ashwin.chaugule@linaro.org>
Subject: Re: [PATCH 1/5] acpi: cppc: Allow build with ACPI_CPU_FREQ_PSS config
Date: Fri, 12 Aug 2016 10:16:21 -0700 [thread overview]
Message-ID: <1471022181.3745.13.camel@linux.intel.com> (raw)
In-Reply-To: <CAFHUOYzXd-cP0G8BiScyH-EykK0D9RJD9eFKGP9Ok12NAgpRnA@mail.gmail.com>
On Fri, 2016-08-12 at 09:58 -0700, Hoan Tran wrote:
> Hi Srinivas,
>
> On Fri, Aug 12, 2016 at 9:52 AM, Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> >
> > On Fri, 2016-08-12 at 09:35 -0700, Hoan Tran wrote:
> > >
> > > Hi Srinivas,
> > >
> > > On Wed, Aug 10, 2016 at 5:17 PM, Srinivas Pandruvada
> > > <srinivas.pandruvada@linux.intel.com> wrote:
> > > >
> > > >
> > > > Some newer x86 platforms have support for both _CPC and _PSS
> > > > object. So
> > > > kernel config can have both ACPI_CPU_FREQ_PSS and
> > > > ACPI_CPPC_LIB. So
> > > > remove
> > > > restriction for ACPI_CPPC_LIB to build only when
> > > > ACPI_CPU_FREQ_PSS
> > > > is not
> > > > defined.
> > > > Also for legacy systems with only _PSS, we shouldn't bail out
> > > > if
> > > > acpi_cppc_processor_probe() fails, if ACPI_CPU_FREQ_PSS is also
> > > > defined.
> > > >
> > > > Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.i
> > > > ntel
> > > > .com>
> > > > ---
> > > > drivers/acpi/Kconfig | 1 -
> > > > drivers/acpi/processor_driver.c | 5 ++++-
> > > > 2 files changed, 4 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
> > > > index 445ce28..c6bb6aa 100644
> > > > --- a/drivers/acpi/Kconfig
> > > > +++ b/drivers/acpi/Kconfig
> > > > @@ -227,7 +227,6 @@ config ACPI_MCFG
> > > > config ACPI_CPPC_LIB
> > > > bool
> > > > depends on ACPI_PROCESSOR
> > > > - depends on !ACPI_CPU_FREQ_PSS
> > > From ACPI 6.1 spec, if _CPC is present, its use supersedes the
> > > use of
> > > PSS. So I think, config ACPI_CPU_FREQ_PSS should depend on
> > > !ACPI_CPPC_LIB.
> > >
> > Distro want to have a single binary kernel image, so they will turn
> > on
> > all configs. So this is not a compile time decision.
> > On runtime if the ACPI contains both tables than _CPC should be
> > used
> > (but that also if the kernel is capable of handling _CPC, as legacy
> > kernel will not).
> Agreed. If so, this "depends on" is not need, right ? And a runtime
> code will be added to decide which is used instead ?
Yes, _CPC will be used if present.
Thanks,
Srinivas
>
> Thanks
> Hoan
>
> >
> >
> > Thanks,
> > Srinivas
> >
> > >
> > > Thanks
> > > Hoan
> > >
> > > >
> > > >
> > > > select MAILBOX
> > > > select PCC
> > > > help
> > > > diff --git a/drivers/acpi/processor_driver.c
> > > > b/drivers/acpi/processor_driver.c
> > > > index 0553aee..0e0b629 100644
> > > > --- a/drivers/acpi/processor_driver.c
> > > > +++ b/drivers/acpi/processor_driver.c
> > > > @@ -245,8 +245,11 @@ static int __acpi_processor_start(struct
> > > > acpi_device *device)
> > > > return 0;
> > > >
> > > > result = acpi_cppc_processor_probe(pr);
> > > > - if (result)
> > > > + if (result) {
> > > > +#ifndef CONFIG_ACPI_CPU_FREQ_PSS
> > > > return -ENODEV;
> > > > +#endif
> > > > + }
> > > >
> > > > if (!cpuidle_get_driver() || cpuidle_get_driver() ==
> > > > &acpi_idle_driver)
> > > > acpi_processor_power_init(pr);
> > > > --
> > > > 2.7.4
> > > >
> > > > --
> > > > To unsubscribe from this list: send the line "unsubscribe
> > > > linux-
> > > > acpi" in
> > > > the body of a message to majordomo@vger.kernel.org
> > > > More majordomo info at http://vger.kernel.org/majordomo-info.h
> > > > tml
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-
> > > pm"
> > > in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.htm
> > > l
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-08-12 17:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 0:17 [PATCH 0/5] x86 CPPC usage Srinivas Pandruvada
2016-08-11 0:17 ` [PATCH 1/5] acpi: cppc: Allow build with ACPI_CPU_FREQ_PSS config Srinivas Pandruvada
2016-08-12 9:13 ` Alexey Klimov
2016-08-12 12:34 ` Srinivas Pandruvada
2016-08-12 16:04 ` Prakash, Prashanth
2016-08-12 16:32 ` Hoan Tran
2016-08-12 16:53 ` Srinivas Pandruvada
2016-08-12 16:35 ` Hoan Tran
2016-08-12 16:52 ` Srinivas Pandruvada
2016-08-12 16:58 ` Hoan Tran
2016-08-12 17:16 ` Srinivas Pandruvada [this message]
2016-08-11 0:17 ` [PATCH 2/5] acpi: cpcc: Add integer read support Srinivas Pandruvada
2016-08-11 0:17 ` [PATCH 3/5] acpi: cppc: Add support for function fixed hardware address Srinivas Pandruvada
2016-08-11 0:17 ` [PATCH 4/5] acpi: cppc: Add prefix cppc to cpudata structure name Srinivas Pandruvada
2016-08-11 0:17 ` [PATCH 5/5] acpi: bus: Enable HWP CPPC objects Srinivas Pandruvada
2016-08-16 14:32 ` Alexey Klimov
2016-08-16 16:50 ` Srinivas Pandruvada
2016-08-18 21:14 ` [PATCH 0/5] x86 CPPC usage Srinivas Pandruvada
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=1471022181.3745.13.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=ashwin.chaugule@linaro.org \
--cc=hotran@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).