From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>,
rafael@kernel.org, lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: DPTF: Add support for high frequency impedance notification
Date: Thu, 05 May 2022 07:46:57 -0700 [thread overview]
Message-ID: <305d709b037e2d56ac7eaaa66567c9a91afcf737.camel@linux.intel.com> (raw)
In-Reply-To: <20220427155130.8023-1-sumeet.r.pawnikar@intel.com>
On Wed, 2022-04-27 at 21:21 +0530, Sumeet Pawnikar wrote:
> Add high frequency impedance notification support under DPTF.
> This returns high frequency impedance value that can be obtained
> from battery fuel gauge whenever there is change over a threshold.
>
I think you should add
While here corrected spelling from IMPEDANCED_CHNGED to
IMPEDANCE_CHANGED.
Otherwise looks good to me.
Thanks,
Srinivas
> Signed-off-by: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
> ---
> drivers/acpi/dptf/dptf_power.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/dptf/dptf_power.c
> b/drivers/acpi/dptf/dptf_power.c
> index dc1f52a5b3f4..2ef53ca88714 100644
> --- a/drivers/acpi/dptf/dptf_power.c
> +++ b/drivers/acpi/dptf/dptf_power.c
> @@ -117,7 +117,7 @@ static const struct attribute_group
> dptf_battery_attribute_group = {
> #define POWER_STATE_CHANGED 0x81
> #define STEADY_STATE_POWER_CHANGED 0x83
> #define POWER_PROP_CHANGE_EVENT 0x84
> -#define IMPEDANCED_CHNGED 0x85
> +#define IMPEDANCE_CHANGED 0x85
> #define VOLTAGE_CURRENT_CHANGED 0x86
>
> static long long dptf_participant_type(acpi_handle handle)
> @@ -150,6 +150,9 @@ static void dptf_power_notify(acpi_handle handle,
> u32 event, void *data)
> case STEADY_STATE_POWER_CHANGED:
> attr = "max_steady_state_power_mw";
> break;
> + case IMPEDANCE_CHANGED:
> + attr = "high_freq_impedance_mohm";
> + break;
> case VOLTAGE_CURRENT_CHANGED:
> attr = "no_load_voltage_mv";
> break;
prev parent reply other threads:[~2022-05-05 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 15:51 Sumeet Pawnikar
2022-05-05 14:46 ` 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=305d709b037e2d56ac7eaaa66567c9a91afcf737.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--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
all inboxes | Powered by JetHome®