mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "yu.chen.surf@gmail.com" <yu.chen.surf@gmail.com>
Cc: "andy@infradead.org" <andy@infradead.org>,
	"andy@kernel.org" <andy@kernel.org>,
	"lenb@kernel.org" <lenb@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dvhart@infradead.org" <dvhart@infradead.org>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] platform/x86: Add support for Uncore frequency control
Date: Mon, 13 Jan 2020 18:03:02 +0000	[thread overview]
Message-ID: <3fc777da692d107a75ad648de4be5bbfa927d2be.camel@intel.com> (raw)
In-Reply-To: <CADjb_WQkq0R8eCNvZgtjytc3dcn9_65pzCt9brYZHo6ATy5wuw@mail.gmail.com>

Hi Chenyu,

Thanks for the pointing.

On Mon, 2020-01-13 at 15:00 +0800, Yu Chen wrote:
> Hi Srinivas,
> On Mon, Jan 13, 2020 at 11:59 AM Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> > +
> > +/* Common function to set min/max ratios to be used by sysfs
> > callbacks */
> > +static int uncore_write_ratio(struct uncore_data *data, unsigned
> > int input,
> > +                             int set_max)
> > +{
> > +       int ret;
> > +       u64 cap;
> > +
> > +       mutex_lock(&uncore_lock);
> > +
> > +       input /= UNCORE_FREQ_KHZ_MULTIPLIER;
> > +       if (!input || input > 0x7F) {
> > +               ret = -EINVAL;
> > +               goto finish_write;
> > +       }
> > +
> > +       rdmsrl(MSR_UNCORE_RATIO_LIMIT, cap);
> Should it be rdmsrl_on_cpu()?
Yes. Fixed and sent update.

Thanks,
Srinivas

> 
> Thanks,
> Chenyu

      reply	other threads:[~2020-01-13 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13  3:59 Srinivas Pandruvada
2020-01-13  3:59 ` [PATCH v2 2/2] MAINTAINERS: Update for the intel uncore " Srinivas Pandruvada
2020-01-13  7:00 ` [PATCH v2 1/2] platform/x86: Add support for Uncore " Yu Chen
2020-01-13 18:03   ` Pandruvada, Srinivas [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=3fc777da692d107a75ad648de4be5bbfa927d2be.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=andy@infradead.org \
    --cc=andy@kernel.org \
    --cc=dvhart@infradead.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=yu.chen.surf@gmail.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

all inboxes | Powered by JetHome®