From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: daniel.lezcano@linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal: intel: int340x: Read DDR data rate for Nova Lake
Date: Mon, 09 Mar 2026 08:48:54 -0700 [thread overview]
Message-ID: <80e78e2b4d1ef4158f0065b5e1fdb0dd5ef754f9.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0ju7V3EaUgwxpUZV2LN2YBaduEd4hpoOJsL-LRmSJ1pvA@mail.gmail.com>
On Thu, 2026-03-05 at 15:42 +0100, Rafael J. Wysocki wrote:
> On Mon, Feb 23, 2026 at 8:05 PM Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> >
> > Add support for reading DDR data rate from PCI config offset.
> > The register details are:
> > CFG Offset : 0xE0
> > Bits : 11:2
> >
> > DDR Data rate is in 33.33 MTPS units.
> >
> > Signed-off-by: Srinivas Pandruvada
> > <srinivas.pandruvada@linux.intel.com>
> > ---
> > .../int340x_thermal/processor_thermal_rfim.c | 16
> > ++++++++++++++++
> > 1 file changed, 16 insertions(+)
> >
> > diff --git
> > a/drivers/thermal/intel/int340x_thermal/processor_thermal_rfim.c
> > b/drivers/thermal/intel/int340x_thermal/processor_thermal_rfim.c
> > index 314fbc1f490f..2e834a175471 100644
> > ---
> > a/drivers/thermal/intel/int340x_thermal/processor_thermal_rfim.c
> > +++
> > b/drivers/thermal/intel/int340x_thermal/processor_thermal_rfim.c
> > @@ -402,6 +402,11 @@ static ssize_t rfi_restriction_show(struct
> > device *dev,
> > return sysfs_emit(buf, "%llu\n", resp);
> > }
> >
> > + /* ddr_data_rate */
> > +static const struct mmio_reg nvl_ddr_data_rate_reg = { 1, 0xE0,
> > 10, 0x3FF, 2};
> > +
> > +static const struct mmio_reg *ddr_data_rate_reg;
> > +
> > static ssize_t ddr_data_rate_show(struct device *dev,
> > struct device_attribute *attr,
> > char *buf)
> > @@ -410,10 +415,20 @@ static ssize_t ddr_data_rate_show(struct
> > device *dev,
> > u64 resp;
> > int ret;
> >
> > + if (ddr_data_rate_reg) {
> > + u16 reg_val;
> > +
> > + pci_read_config_word(to_pci_dev(dev),
> > ddr_data_rate_reg->offset, ®_val);
> > + resp = (reg_val >> ddr_data_rate_reg->shift) &
> > ddr_data_rate_reg->mask;
> > + resp = (resp * 3333) / 100;
> > + goto ret_resp;
> > + }
> > +
> > ret = processor_thermal_send_mbox_read_cmd(to_pci_dev(dev),
> > id, &resp);
> > if (ret)
> > return ret;
> >
> > +ret_resp:
> > return sysfs_emit(buf, "%llu\n", resp);
> > }
> >
> > @@ -461,6 +476,7 @@ int proc_thermal_rfim_add(struct pci_dev *pdev,
> > struct proc_thermal_device *proc
> > case PCI_DEVICE_ID_INTEL_NVL_H_THERMAL:
> > case PCI_DEVICE_ID_INTEL_NVL_S_THERMAL:
> > dlvr_mmio_regs_table = nvl_dlvr_mmio_regs;
> > + ddr_data_rate_reg = &nvl_ddr_data_rate_reg;
> > break;
> > default:
> > dlvr_mmio_regs_table = dlvr_mmio_regs;
> > --
>
> Applied as 7.1 material, but I rearranged it to avoid using goto and
> declare local vars where they are needed, please see:
Looks good.
Thanks,
Srinivas
>
> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/patch/?id=6d3e2ce6f10107c2e5870e9dce7c2e1d03a6be72
prev parent reply other threads:[~2026-03-09 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 19:04 Srinivas Pandruvada
2026-03-05 14:42 ` Rafael J. Wysocki
2026-03-09 15:48 ` srinivas pandruvada [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=80e78e2b4d1ef4158f0065b5e1fdb0dd5ef754f9.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@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®