[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251114064413.6105-1-wenliang202407@163.com>
Date: Fri, 14 Nov 2025 01:44:13 -0500
From: Wenliang Yan <wenliang202407@....com>
To: linux@...ck-us.net
Cc: christophe.jaillet@...adoo.fr,
conor+dt@...nel.org,
corbet@....net,
devicetree@...r.kernel.org,
jdelvare@...e.com,
krzk+dt@...nel.org,
linux-hwmon@...r.kernel.org,
linux-kernel@...r.kernel.org,
robh@...nel.org,
wenliang202407@....com
Subject: Re: [PATCH 1/8] dt-binding:ti,ina3221:Add SQ52210
At 2025-11-13 10:03:01, "Guenter Roeck" <linux@...ck-us.net> wrote:
>On 11/11/25 00:05, Wenliang Yan wrote:
>> Add a compatible string for sq52210, sq52210 is forward compatible
>> with INA3221 and add alert register to implement four additional
>> alert function.
>>
>> Signed-off-by: Wenliang Yan <wenliang202407@....com>
>> ---
>> .../devicetree/bindings/hwmon/ti,ina3221.yaml | 16 +++++++++++++++-
>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/hwmon/ti,ina3221.yaml b/Documentation/devicetree/bindings/hwmon/ti,ina3221.yaml
>> index 5f10f1207d69..0fae82ca3ee1 100644
>> --- a/Documentation/devicetree/bindings/hwmon/ti,ina3221.yaml
>> +++ b/Documentation/devicetree/bindings/hwmon/ti,ina3221.yaml
>> @@ -12,7 +12,9 @@ maintainers:
>>
>> properties:
>> compatible:
>> - const: ti,ina3221
>> + enum:
>> + - silergy,sq52210
>> + - ti,ina3221
>>
>> reg:
>> maxItems: 1
>> @@ -77,6 +79,18 @@ patternProperties:
>> exclude specific channels from the summation control function.
>> type: boolean
>>
>> + alert-type:
>> + description: |
>> + The SQ52210 features a configurable alert function with four
>> + types: SUL, BOL, BUL, and POL. Each channel can be configured to
>> + select one of these types to enable the alert function. This alert
>> + function can operate concurrently with both Critical and Warning
>> + functions.
>> +
>> + The configuration must use numerical values 0 through 3,
>> + 0 corresponds to SUL, 1 to BOL, 2 to BUL, and 3 to POL.
>> + enum: [ 0, 1, 2, 3 ]
>> +
>
>Per datasheet, each of the alerts can be enabled independently. It is possible
>to enable SUL, BOL, BUL, and POL on each channel at the same time. This is not
>possible with the above property since it only permits enabling alerts for one
>of the alert sources on each channel.
>
>Also, I am not sure if it makes sense to have this as devicetree property.
>It is not really a board property. It might make more sense to tie enabling
>the alerts automatically if a channel is enabled and a limit is set for a
>given channel.
>
The "If multiple function are enabled, the Alert Function with the highrst
signifivant bit position(D15-D4) takes priority and responds to the Alert
LImit Register" described on page 21 of the datasheet refers to the fact that
when different trigger sources are enabled simultaneously, only the highest
priority trigger source takes effect (SUL > BOL > BUL > POL).Therefore,
essentially only one type of alert can be active per channel.
Indeed, it is unnecessary to configure the alert-type at the board level.
I will modify this content and conduct testing before the next submission,
and also remove the alert-type support in Patch 3.
Thanks,
Wenlaing Yan
Powered by blists - more mailing lists