Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Guenter Roeck <linux@roeck-us.net>,
	Manaf Meethalavalappu Pallikunhi
	<manaf.pallikunhi@oss.qualcomm.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	amit.kucheria@oss.qualcomm.com,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>,
	linux-hwmon@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] hwmon: Add Qualcomm PMIC BCL hardware monitor driver
Date: Fri, 20 Mar 2026 17:08:57 +0100	[thread overview]
Message-ID: <6f4b27c5-074e-403a-90b8-fe7ef3a993b5@oss.qualcomm.com> (raw)
In-Reply-To: <a922cf55-ebe7-4256-b3bb-cc732e45e1ff@roeck-us.net>


Hi Guenter,

On 3/20/26 16:22, Guenter Roeck wrote:
> On 3/20/26 07:52, Daniel Lezcano wrote:

[ ... ]

>>> +
>>> +ADD_BCL_HWMON_ALARM_MAPS(in, min, lcrit);
>>> +ADD_BCL_HWMON_ALARM_MAPS(curr, max, crit);
>>> +
>>> +/* Interrupt names for each alarm level */
>>> +static const char * const bcl_int_names[ALARM_MAX] = {
>>> +    [LVL0] = "bcl-max-min",
>>> +    [LVL1] = "bcl-critical",
>>> +};
>>
>> IIUC there are three levels of alarms but the hwmon only has max/min
>> and critical. Would it make sense to do adaptative min / max ? So when
> 
> hwmon has lcrit, min, max, and crit alarms for all sensor types, plus
> an additional _cap_alarm for power attributes and _emergency_alarm
> for temperature attributes. There is also a generic _alarm attribute
> for each sensor, which is supposed to be used if the specific alarm
> type is not known.
> 
> What exactly are the three levels of alarms ?

Manaf can give more clarifications, but it is like we have yellow, 
orange and red alarms. So there is an additional alarm comparing to what 
is available in hwmon. The proposed driver maps orange and red alarms, 
respectively to bcl-max and bcl-critical.

I'm just asking if it is important to have this 'yellow' alarm ? And as 
there is a missing alarm to describe it in hwmon, how can we use it ?

  reply	other threads:[~2026-03-20 16:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 21:14 [PATCH 0/4] hwmon: Add Qualcomm PMIC BCL hardware monitor driver Manaf Meethalavalappu Pallikunhi
2026-02-05 21:14 ` [PATCH 1/4] dt-bindings: hwmon: Add qcom,bcl-hwmon yaml bindings Manaf Meethalavalappu Pallikunhi
2026-02-06  8:09   ` Krzysztof Kozlowski
2026-02-12 20:24     ` Manaf Meethalavalappu Pallikunhi
2026-02-06  9:08   ` Dmitry Baryshkov
2026-02-12 20:41     ` Manaf Meethalavalappu Pallikunhi
2026-02-06  9:08   ` Konrad Dybcio
2026-02-13  6:04     ` Manaf Meethalavalappu Pallikunhi
2026-02-13 10:41       ` Konrad Dybcio
2026-02-13 12:00         ` Manaf Meethalavalappu Pallikunhi
2026-02-05 21:14 ` [PATCH 2/4] hwmon: Add Qualcomm PMIC BCL hardware monitor driver Manaf Meethalavalappu Pallikunhi
2026-02-06  8:12   ` Krzysztof Kozlowski
2026-02-13  6:21     ` Manaf Meethalavalappu Pallikunhi
2026-02-06  9:27   ` Konrad Dybcio
2026-02-06  9:38     ` Krzysztof Kozlowski
2026-02-13  9:42     ` Manaf Meethalavalappu Pallikunhi
2026-02-13 10:55       ` Konrad Dybcio
2026-02-06 13:24   ` Bjorn Andersson
2026-02-13 11:38     ` Manaf Meethalavalappu Pallikunhi
2026-02-08  1:27   ` kernel test robot
2026-03-20 14:52   ` Daniel Lezcano
2026-03-20 15:22     ` Guenter Roeck
2026-03-20 16:08       ` Daniel Lezcano [this message]
2026-03-20 16:59         ` Guenter Roeck
2026-03-20 17:23           ` Daniel Lezcano
2026-04-17 18:08         ` Manaf Meethalavalappu Pallikunhi
2026-04-17 18:01     ` Manaf Meethalavalappu Pallikunhi
2026-02-05 21:14 ` [PATCH 3/4] arm64: dts: qcom: pm7250b: Enable Qualcomm BCL device Manaf Meethalavalappu Pallikunhi
2026-02-06  8:13   ` Krzysztof Kozlowski
2026-02-13 11:44     ` Manaf Meethalavalappu Pallikunhi
2026-02-06  9:11   ` Konrad Dybcio
2026-02-13 11:55     ` Manaf Meethalavalappu Pallikunhi
2026-02-16 11:48       ` Konrad Dybcio
2026-02-19 11:34         ` Manaf Meethalavalappu Pallikunhi
2026-02-19 13:04           ` Konrad Dybcio
2026-02-24 18:35             ` Manaf Meethalavalappu Pallikunhi
2026-02-25 11:47               ` Konrad Dybcio
2026-02-06  9:11   ` Konrad Dybcio
2026-02-13 11:56     ` Manaf Meethalavalappu Pallikunhi
2026-02-05 21:14 ` [PATCH 4/4] arm64: dts: qcom: pm8350c: " Manaf Meethalavalappu Pallikunhi

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=6f4b27c5-074e-403a-90b8-fe7ef3a993b5@oss.qualcomm.com \
    --to=daniel.lezcano@oss.qualcomm.com \
    --cc=amit.kucheria@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gaurav.kohli@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=manaf.pallikunhi@oss.qualcomm.com \
    --cc=robh@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