Linux Power Management development
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Akshu Agrawal <akshu.agrawal@amd.com>
Cc: linux-pm@vger.kernel.org, satyajit.sahu@amd.com
Subject: Re: [PATCH] cpufreq: AMD: Ignore the check for ProcFeedback in ST/CZ
Date: Thu, 08 Feb 2018 11:03:49 +0100	[thread overview]
Message-ID: <3381840.P1uz7taRdH@aspire.rjw.lan> (raw)
In-Reply-To: <20180118104251.GJ3012@vireshk-i7>

On Thursday, January 18, 2018 11:42:51 AM CET Viresh Kumar wrote:
> On 18-01-18, 15:51, Akshu Agrawal wrote:
> > In ST/CZ CPUID 8000_0007_EDX[11, ProcFeedbackInterface] is 0,
> > but the mechanism is still available and can be used.
> > 
> > Signed-off-by: Akshu Agrawal <akshu.agrawal@amd.com>
> > ---
> >  drivers/cpufreq/amd_freq_sensitivity.c | 11 +++++++++--
> >  1 file changed, 9 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/cpufreq/amd_freq_sensitivity.c b/drivers/cpufreq/amd_freq_sensitivity.c
> > index 042023bbbf62..be926d9a66e5 100644
> > --- a/drivers/cpufreq/amd_freq_sensitivity.c
> > +++ b/drivers/cpufreq/amd_freq_sensitivity.c
> > @@ -14,6 +14,7 @@
> >  #include <linux/kernel.h>
> >  #include <linux/module.h>
> >  #include <linux/types.h>
> > +#include <linux/pci.h>
> >  #include <linux/percpu-defs.h>
> >  #include <linux/init.h>
> >  #include <linux/mod_devicetable.h>
> > @@ -109,12 +110,18 @@ static unsigned int amd_powersave_bias_target(struct cpufreq_policy *policy,
> >  static int __init amd_freq_sensitivity_init(void)
> >  {
> >  	u64 val;
> > +	struct pci_dev *pcidev;
> >  
> >  	if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD)
> >  		return -ENODEV;
> >  
> > -	if (!static_cpu_has(X86_FEATURE_PROC_FEEDBACK))
> > -		return -ENODEV;
> > +	pcidev = pci_get_device(PCI_VENDOR_ID_AMD,
> > +			PCI_DEVICE_ID_AMD_KERNCZ_SMBUS, NULL);
> > +
> > +	if (!pcidev) {
> > +		if (!static_cpu_has(X86_FEATURE_PROC_FEEDBACK))
> > +			return -ENODEV;
> > +	}
> >  
> >  	if (rdmsrl_safe(MSR_AMD64_FREQ_SENSITIVITY_ACTUAL, &val))
> >  		return -ENODEV;
> 
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

Patch applied, thanks!

  reply	other threads:[~2018-02-08 10:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 10:21 [PATCH] cpufreq: AMD: Ignore the check for ProcFeedback in ST/CZ Akshu Agrawal
2018-01-18 10:42 ` Viresh Kumar
2018-02-08 10:03   ` Rafael J. Wysocki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-18  8:51 Akshu Agrawal
2018-01-18  9:11 ` Viresh Kumar
2018-01-18 10:04   ` Agrawal, Akshu
2018-01-18 10:11     ` Viresh Kumar

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=3381840.P1uz7taRdH@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=akshu.agrawal@amd.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=satyajit.sahu@amd.com \
    --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