From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>,
rafael@kernel.org, daniel.lezcano@linaro.org, amitk@kernel.org,
rui.zhang@intel.com, atenart@kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal: int340x: Add Meteor Lake PCI device id
Date: Mon, 23 May 2022 10:34:33 -0700 [thread overview]
Message-ID: <700214729a042ef80ea06b3f2c2b2399d63a84ae.camel@linux.intel.com> (raw)
In-Reply-To: <20220523172242.30378-1-sumeet.r.pawnikar@intel.com>
On Mon, 2022-05-23 at 22:52 +0530, Sumeet Pawnikar wrote:
> Add Meteor Lake PCI ID for processor thermal device.
>
> Signed-off-by: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
> Signed-off-by: Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com>
Replace Signed-off-by
Reviewed-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> drivers/thermal/intel/int340x_thermal/processor_thermal_device.h | 1
> +
> .../thermal/intel/int340x_thermal/processor_thermal_device_pci.c | 1
> +
> 2 files changed, 2 insertions(+)
>
> diff --git
> a/drivers/thermal/intel/int340x_thermal/processor_thermal_device.h
> b/drivers/thermal/intel/int340x_thermal/processor_thermal_device.h
> index 49932a68abac..7d52fcff4937 100644
> ---
> a/drivers/thermal/intel/int340x_thermal/processor_thermal_device.h
> +++
> b/drivers/thermal/intel/int340x_thermal/processor_thermal_device.h
> @@ -24,6 +24,7 @@
> #define PCI_DEVICE_ID_INTEL_HSB_THERMAL 0x0A03
> #define PCI_DEVICE_ID_INTEL_ICL_THERMAL 0x8a03
> #define PCI_DEVICE_ID_INTEL_JSL_THERMAL 0x4E03
> +#define PCI_DEVICE_ID_INTEL_MTLP_THERMAL 0x7D03
> #define PCI_DEVICE_ID_INTEL_RPL_THERMAL 0xA71D
> #define PCI_DEVICE_ID_INTEL_SKL_THERMAL 0x1903
> #define PCI_DEVICE_ID_INTEL_TGL_THERMAL 0x9A03
> diff --git
> a/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.
> c
> b/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.
> c
> index ca40b0967cdd..c2dc4c158b9d 100644
> ---
> a/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.
> c
> +++
> b/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.
> c
> @@ -358,6 +358,7 @@ static SIMPLE_DEV_PM_OPS(proc_thermal_pci_pm,
> proc_thermal_pci_suspend,
>
> static const struct pci_device_id proc_thermal_pci_ids[] = {
> { PCI_DEVICE_DATA(INTEL, ADL_THERMAL,
> PROC_THERMAL_FEATURE_RAPL | PROC_THERMAL_FEATURE_FIVR |
> PROC_THERMAL_FEATURE_DVFS | PROC_THERMAL_FEATURE_MBOX) },
> + { PCI_DEVICE_DATA(INTEL, MTLP_THERMAL,
> PROC_THERMAL_FEATURE_RAPL | PROC_THERMAL_FEATURE_FIVR |
> PROC_THERMAL_FEATURE_DVFS | PROC_THERMAL_FEATURE_MBOX) },
> { PCI_DEVICE_DATA(INTEL, RPL_THERMAL,
> PROC_THERMAL_FEATURE_RAPL | PROC_THERMAL_FEATURE_FIVR |
> PROC_THERMAL_FEATURE_DVFS | PROC_THERMAL_FEATURE_MBOX) },
> { },
> };
prev parent reply other threads:[~2022-05-23 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 17:22 [PATCH] thermal: int340x: Add Meteor Lake PCI device id Sumeet Pawnikar
2022-05-23 17:34 ` 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=700214729a042ef80ea06b3f2c2b2399d63a84ae.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=amitk@kernel.org \
--cc=atenart@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sumeet.r.pawnikar@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).