linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rafael@kernel.org, lenb@kernel.org, daniel.lezcano@linaro.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, amitk@kernel.org,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH 0/3] DPTF IDs for Raptor Lake
Date: Fri, 14 Jan 2022 15:24:32 -0800	[thread overview]
Message-ID: <20220114232435.448340-1-srinivas.pandruvada@linux.intel.com> (raw)

Add ACPI and PCI device ids for Raptor Lake DPTF support.

Srinivas Pandruvada (3):
  ACPI: DPTF: Support Raptor Lake
  thermal: int340x: Support Raptor Lake
  thermal: int340x: Add Raptor Lake PCI device id

 drivers/acpi/dptf/dptf_pch_fivr.c                           | 1 +
 drivers/acpi/dptf/dptf_power.c                              | 2 ++
 drivers/acpi/dptf/int340x_thermal.c                         | 6 ++++++
 drivers/acpi/fan.h                                          | 1 +
 drivers/thermal/intel/int340x_thermal/int3400_thermal.c     | 1 +
 drivers/thermal/intel/int340x_thermal/int3403_thermal.c     | 1 +
 .../intel/int340x_thermal/processor_thermal_device.h        | 1 +
 .../intel/int340x_thermal/processor_thermal_device_pci.c    | 1 +
 8 files changed, 14 insertions(+)

-- 
2.34.1


             reply	other threads:[~2022-01-14 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 23:24 Srinivas Pandruvada [this message]
2022-01-14 23:24 ` [PATCH 1/3] ACPI: DPTF: Support Raptor Lake Srinivas Pandruvada
2022-01-14 23:24 ` [PATCH 2/3] thermal: int340x: " Srinivas Pandruvada
2022-01-14 23:24 ` [PATCH 3/3] thermal: int340x: Add Raptor Lake PCI device id Srinivas Pandruvada
2022-01-17 18:52 ` [PATCH 0/3] DPTF IDs for Raptor Lake Rafael J. Wysocki

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=20220114232435.448340-1-srinivas.pandruvada@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=amitk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).