linux-kernel - Re: [PATCH 1/2] dt-bindings: hwmon: temperature: add support for EMC1812

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251104-displace-pretense-9efca7fd0796@wendy>
Date: Tue, 4 Nov 2025 08:39:39 +0000
From: Conor Dooley <conor.dooley@...rochip.com>
To: <Marius.Cristea@...rochip.com>
CC: <conor@...nel.org>, <corbet@....net>, <linux@...ck-us.net>,
	<linux-hwmon@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<robh@...nel.org>, <linux-kernel@...r.kernel.org>, <krzk+dt@...nel.org>,
	<linux-doc@...r.kernel.org>, <conor+dt@...nel.org>
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: temperature: add support for
 EMC1812

On Mon, Nov 03, 2025 at 04:35:27PM +0000, Marius.Cristea@...rochip.com wrote:
> Hi Conor,
> 
> On Wed, 2025-10-29 at 18:25 +0000, Conor Dooley wrote:
> > On Wed, Oct 29, 2025 at 05:50:58PM +0200, Marius Cristea wrote:
> > > This is the devicetree schema for Microchip EMC1812/13/14/15/33
> > > Multichannel Low-Voltage Remote Diode Sensor Family.
> > > 
> > > Signed-off-by: Marius Cristea <marius.cristea@...rochip.com>
> > > ---
> > >  .../bindings/hwmon/microchip,emc1812.yaml          | 176
> > > +++++++++++++++++++++
> > >  MAINTAINERS                                        |   6 +
> > >  2 files changed, 182 insertions(+)
> > > 
> > 
> 
> ...
> > You should be able to just move this into interrupts:
> >   interrupts:
> >     items:
> >       - description:
> >           alert-therm2 asserts when a diode temperature exceeds the
> > ALERT
> >           threshold.
> >       - description:
> >           therm-addr asserts low when the hardware-set THERM limit
> > threshold is
> >           exceeded by one of the temperature sensors.
> > 
> > > +    items:
> > > +      - const: alert-therm2
> > > +      - const: therm-addr
> > 
> > Also, should this and interrupts have minItems: 1? Are both actually
> > required? Can you have therm-addr without alert-therm2?
> > 
> 
> Right now the driver doesn't support any interrupts, but it may support
> in future. The "alert-therm2" is a maskable interrupt and the "therm-
> addr" can't be masked and is "always enabled" into the chip.
> 
> I didn't use "minItems: 1" because I wanted to leave to the user the
> decision if he needs any interrupts into their system

Unfortunately, this doesn't work the way you expected. If you don't set
minItems: 1, then anyone who wants to use an interrupt must use both.

If someone that would connect therm-addr would always also connect
alert-therm2, then minItems: 1 is enough to add. If someone might want to
use therm-addr but not use alter-therm2, then this needs to be changed
to permit these in any order. You can do that by adding the names as an
enum, eg
items:
 - enum: [ foo, bar]
 - bar


Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)