From: Guenter Roeck <linux@roeck-us.net>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Igor Reznichenko <igor@reznichenko.net>
Cc: conor+dt@kernel.org, corbet@lwn.net,
david.hunter.linux@gmail.com, devicetree@vger.kernel.org,
krzk+dt@kernel.org, linux-doc@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org, skhan@linuxfoundation.org
Subject: Re: [PATCH v2 1/2] dt-bindings: hwmon: Add support for ST TSC1641 power monitor
Date: Mon, 27 Oct 2025 09:53:53 -0700 [thread overview]
Message-ID: <0dfcfcde-d207-44af-ae7f-d90d623bac02@roeck-us.net> (raw)
In-Reply-To: <112db7fd-3c0e-4c56-a553-5aca12965bdf@kernel.org>
On 10/27/25 01:40, Krzysztof Kozlowski wrote:
> On 26/10/2025 20:58, Guenter Roeck wrote:
>>>>>> + reg:
>>>>>> + maxItems: 1
>>>>>> +
>>>>>> + shunt-resistor-micro-ohms:
>>>>>> + description: Shunt resistor value in micro-ohms. Since device has internal
>>>>>> + 16-bit RSHUNT register with 10 uOhm LSB, the maximum value is capped at
>>>>>> + 655.35 mOhm.
>>>>>> + minimum: 100
>>>>>> + default: 1000
>>>>>> + maximum: 655350
>>>>>> +
>>>>>> + st,alert-polarity-active-high:
>>>>>
>>>>> Isn't this just interrupt? You need proper interrupts property and then
>>>>> its flag define the type of interrupt.
>>>>
>>>> This controls a bit written into device register.
>>>> I omitted interrupt property after looking at existing power monitor bindings,
>>>> especially hwmon/ti,ina2xx.yaml. INA226 has very similar bit controlling alert
>>>> pin polarity and binding doesn't define alert pin as interrupt. Overall, I didn't
>>>> find many power monitor bindings defining alert pins as interrupts.
>>>
>>>
>>> On INA2xx that's SMBUS Alert. Is this the case here as well?
>>>
>>
>> It could be wired to SMBus alert, or it could be wired to a CPU interrupt pin.
>
> So please explain me why CPU interrupt pin, which in every really every
> device called "interrupts", would not be "interrupts" here? How CPU can
> even guess the number of the interrupt in such case, without
> "interrupts" property?
>
I thought we were discussing the need for the st,alert-polarity-active-high
property, sorry.
Guenter
next prev parent reply other threads:[~2025-10-27 16:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 4:47 [PATCH 0/5] hwmon: Add TSC1641 I2C power monitor driver Igor Reznichenko
2025-10-22 4:47 ` [PATCH 1/5] drivers/hwmon: " Igor Reznichenko
2025-10-22 14:51 ` Guenter Roeck
2025-10-23 7:50 ` Igor Reznichenko
2025-10-23 12:55 ` Guenter Roeck
2025-10-22 4:47 ` [PATCH 2/5] drivers/hwmon: Add Kconfig entry for TSC1641 Igor Reznichenko
2025-10-22 6:49 ` Krzysztof Kozlowski
2025-10-22 4:47 ` [PATCH 3/5] drivers/hwmon: Add TSC1641 module to Makefile Igor Reznichenko
2025-10-22 6:49 ` Krzysztof Kozlowski
2025-10-22 4:47 ` [PATCH 4/5] Documentation/hwmon: Add TSC1641 driver documentation Igor Reznichenko
2025-10-22 4:47 ` [PATCH 5/5] Documentation/devicetree/bindings/hwmon: Add TSC1641 binding Igor Reznichenko
2025-10-22 6:29 ` Rob Herring (Arm)
2025-10-22 6:48 ` Krzysztof Kozlowski
2025-10-22 14:07 ` [PATCH 0/5] hwmon: Add TSC1641 I2C power monitor driver Guenter Roeck
2025-10-26 6:50 ` [PATCH v2 0/2] " Igor Reznichenko
2025-10-26 6:50 ` [PATCH v2 1/2] dt-bindings: hwmon: Add support for ST TSC1641 power monitor Igor Reznichenko
2025-10-26 16:32 ` Krzysztof Kozlowski
2025-10-26 17:22 ` Guenter Roeck
2025-10-26 19:15 ` Krzysztof Kozlowski
2025-10-26 18:46 ` Igor Reznichenko
2025-10-26 19:41 ` Krzysztof Kozlowski
2025-10-26 19:58 ` Guenter Roeck
2025-10-27 8:40 ` Krzysztof Kozlowski
2025-10-27 16:53 ` Guenter Roeck [this message]
2025-10-27 18:01 ` Krzysztof Kozlowski
2025-10-27 19:14 ` Rob Herring
2025-10-28 15:17 ` Igor Reznichenko
2025-10-28 15:33 ` Guenter Roeck
2025-10-31 4:40 ` Igor Reznichenko
2025-10-31 7:57 ` Krzysztof Kozlowski
2025-10-31 17:30 ` Igor Reznichenko
2025-10-31 18:37 ` Guenter Roeck
2025-10-26 6:50 ` [PATCH v2 2/2] hwmon: Add TSC1641 I2C power monitor driver Igor Reznichenko
2025-10-26 17:08 ` Guenter Roeck
2025-10-27 6:41 ` Igor Reznichenko
2025-10-27 16:52 ` Guenter Roeck
2025-10-26 16:28 ` [PATCH v2 0/2] " Krzysztof Kozlowski
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=0dfcfcde-d207-44af-ae7f-d90d623bac02@roeck-us.net \
--to=linux@roeck-us.net \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=david.hunter.linux@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=igor@reznichenko.net \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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