From: Guenter Roeck <linux@roeck-us.net>
To: Manaf Meethalavalappu Pallikunhi
<manaf.pallikunhi@oss.qualcomm.com>,
Hardware Monitoring <linux-hwmon@vger.kernel.org>
Subject: Re: [PATCH v2] hwmon: Add support for currX_emergency and inX_[l]emergency attributes
Date: Mon, 24 Aug 2026 14:00:45 -0700 [thread overview]
Message-ID: <8ab90280-6eea-4e4d-b698-e6c050cd7ca0@roeck-us.net> (raw)
In-Reply-To: <293f09a2-a9ac-4e35-bb5b-e1008533c318@oss.qualcomm.com>
On 8/24/26 12:42, Manaf Meethalavalappu Pallikunhi wrote:
> Hi Guenter,
>
>
> On 8/14/2026 2:44 AM, Guenter Roeck wrote:
>> Some hardware monitoring chips support three alarm levels for current and voltage high limits, and three alarm levels for voltage low limits. Add support for currX_emergency, inX_emergency, and inX_lemergency attributes together with the appropriate alarm attributes to support such chips. Cc: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@oss.qualcomm.com>Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>
> Thanks for the patch.
>
> The change looks good to me. I applied the patch and validated the
> emergency limit alarm for voltage and current sensors with my Qualcomm
> BCL series applied on top of it, on the Qualcomm Glymur CRD platform.
>
> Tested-by: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@oss.qualcomm.com>
Thanks!
Guenter
prev parent reply other threads:[~2026-08-24 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 21:14 [PATCH v2] hwmon: Add support for currX_emergency and inX_[l]emergency attributes Guenter Roeck
2026-08-14 1:20 ` sashiko-bot
2026-08-14 1:54 ` Guenter Roeck
2026-08-24 19:42 ` Manaf Meethalavalappu Pallikunhi
2026-08-24 21:00 ` Guenter Roeck [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=8ab90280-6eea-4e4d-b698-e6c050cd7ca0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=manaf.pallikunhi@oss.qualcomm.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