mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	daniel.lezcano@linaro.org, amit.kucheria@verdurent.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Swaminathan, Nivedita" <nivedita.swaminathan@intel.com>
Subject: Re: [PATCH] thermal: int340x: processor_thermal: Add Jasper Lake support
Date: Thu, 16 Jan 2020 14:55:55 +0800	[thread overview]
Message-ID: <22cf7771952d633e36503ae3d8d462a1d40c3c90.camel@intel.com> (raw)
In-Reply-To: <20191212203025.36310-1-srinivas.pandruvada@linux.intel.com>

On Thu, 2019-12-12 at 12:30 -0800, Srinivas Pandruvada wrote:
> From: "Swaminathan, Nivedita" <nivedita.swaminathan@intel.com>
> 
> Added new PCI id for Jasper Lake processor thermal device.
> 
> Signed-off-by: Swaminathan, Nivedita <nivedita.swaminathan@intel.com>
> Signed-off-by: Srinivas Pandruvada <
> srinivas.pandruvada@linux.intel.com>

Acked-by: Zhang Rui <rui.zhang@intel.com>
> ---
>  .../thermal/intel/int340x_thermal/processor_thermal_device.c  | 4
> ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git
> a/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> b/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> index 89a015387283..b1fd34516e28 100644
> ---
> a/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> +++
> b/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> @@ -42,6 +42,9 @@
>  /* IceLake thermal reporting device */
>  #define PCI_DEVICE_ID_PROC_ICL_THERMAL	0x8a03
>  
> +/* JasperLake thermal reporting device */
> +#define PCI_DEVICE_ID_PROC_JSL_THERMAL	0x4503
> +
>  #define DRV_NAME "proc_thermal"
>  
>  struct power_config {
> @@ -724,6 +727,7 @@ static const struct pci_device_id
> proc_thermal_pci_ids[] = {
>  	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL,
> PCI_DEVICE_ID_PROC_GLK_THERMAL)},
>  	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL,
> PCI_DEVICE_ID_PROC_ICL_THERMAL),
>  		.driver_data = (kernel_ulong_t)&rapl_mmio_hsw, },
> +	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL,
> PCI_DEVICE_ID_PROC_JSL_THERMAL)},
>  	{ 0, },
>  };
>  


      reply	other threads:[~2020-01-16  6:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 20:30 Srinivas Pandruvada
2020-01-16  6:55 ` Zhang Rui [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=22cf7771952d633e36503ae3d8d462a1d40c3c90.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=amit.kucheria@verdurent.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nivedita.swaminathan@intel.com \
    --cc=srinivas.pandruvada@linux.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

all inboxes | Powered by JetHome®