Linux Documentation
 help / color / mirror / Atom feed
From: <Marius.Cristea@microchip.com>
To: <conor@kernel.org>
Cc: <corbet@lwn.net>, <linux@roeck-us.net>,
	<linux-hwmon@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<robh@kernel.org>, <linux-kernel@vger.kernel.org>,
	<krzk+dt@kernel.org>, <linux-doc@vger.kernel.org>,
	<conor+dt@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: temperature: add support for EMC1812
Date: Mon, 3 Nov 2025 16:35:27 +0000	[thread overview]
Message-ID: <c844428aa8d57d870b8cb55ce37d6359e3142585.camel@microchip.com> (raw)
In-Reply-To: <20251029-blaspheme-stinking-91b73a8ab778@spud>

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@microchip.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


> pw-bot: changes-requested
> 
> Cheers,
> Conor.
> 
> > +
> > +  "#address-cells":
> > +    const: 1
> > +
> > +  "#size-cells":
> > +    const: 0
> > +

Thanks,
Marius

  reply	other threads:[~2025-11-03 16:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 15:50 [PATCH 0/2] Add support for Microchip EMC1812 Marius Cristea
2025-10-29 15:50 ` [PATCH 1/2] dt-bindings: hwmon: temperature: add support for EMC1812 Marius Cristea
2025-10-29 18:25   ` Conor Dooley
2025-11-03 16:35     ` Marius.Cristea [this message]
2025-11-04  8:39       ` Conor Dooley
2025-10-29 15:50 ` [PATCH 2/2] " Marius Cristea
2025-10-29 18:00   ` Guenter Roeck
2025-10-29 20:32   ` Guenter Roeck
2025-10-29 20:47   ` Guenter Roeck
2025-10-29 22:03   ` 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=c844428aa8d57d870b8cb55ce37d6359e3142585.camel@microchip.com \
    --to=marius.cristea@microchip.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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