From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>,
rui.zhang@intel.com, daniel.lezcano@linaro.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: DPTF: Add battery participant for Intel SoCs
Date: Fri, 07 May 2021 08:46:57 -0700 [thread overview]
Message-ID: <335740e398b96b438153f8e6ea27eaa40a12c324.camel@linux.intel.com> (raw)
In-Reply-To: <20210507145819.22608-1-sumeet.r.pawnikar@intel.com>
On Fri, 2021-05-07 at 20:28 +0530, Sumeet Pawnikar wrote:
> Add ACPI Device ID for DPTF battery participant for the Intel
> Jasper Lake (INT3532) and Tiger Lake (INTC1050) SoC based platforms.
>
You need to copy to linux-acpi@vger.kernel.org
> Signed-off-by: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
> ---
> drivers/acpi/dptf/int340x_thermal.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/acpi/dptf/int340x_thermal.c
> b/drivers/acpi/dptf/int340x_thermal.c
> index d14025a85ce8..da5d5f0be2f2 100644
> --- a/drivers/acpi/dptf/int340x_thermal.c
> +++ b/drivers/acpi/dptf/int340x_thermal.c
> @@ -24,6 +24,7 @@ static const struct acpi_device_id
> int340x_thermal_device_ids[] = {
> {"INT3409"},
> {"INT340A"},
> {"INT340B"},
> + {"INT3532"},
> {"INTC1040"},
> {"INTC1041"},
> {"INTC1043"},
> @@ -33,6 +34,7 @@ static const struct acpi_device_id
> int340x_thermal_device_ids[] = {
> {"INTC1047"},
> {"INTC1048"},
> {"INTC1049"},
> + {"INTC1050"},
> {"INTC1060"},
> {"INTC1061"},
> {""},
next prev parent reply other threads:[~2021-05-07 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 14:58 [PATCH] ACPI: DPTF: Add battery participant for Intel SoCs Sumeet Pawnikar
2021-05-07 15:46 ` Srinivas Pandruvada [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-10 15:58 Sumeet Pawnikar
2021-05-12 13:49 ` 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=335740e398b96b438153f8e6ea27eaa40a12c324.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=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).