Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@oss.qualcomm.com>
To: Guenter Roeck <linux@roeck-us.net>,
	Hardware Monitoring <linux-hwmon@vger.kernel.org>
Subject: Re: [PATCH v2] hwmon: Add support for currX_emergency and inX_[l]emergency attributes
Date: Tue, 25 Aug 2026 01:12:24 +0530	[thread overview]
Message-ID: <293f09a2-a9ac-4e35-bb5b-e1008533c318@oss.qualcomm.com> (raw)
In-Reply-To: <20260813211433.879638-1-linux@roeck-us.net>

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>

  parent reply	other threads:[~2026-08-24 19:42 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 [this message]
2026-08-24 21:00   ` Guenter Roeck

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=293f09a2-a9ac-4e35-bb5b-e1008533c318@oss.qualcomm.com \
    --to=manaf.pallikunhi@oss.qualcomm.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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