From: <Victor.Duicu@microchip.com>
To: <linux@roeck-us.net>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <corbet@lwn.net>, <krzk@kernel.org>
Cc: <Marius.Cristea@microchip.com>, <linux-hwmon@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: hwmon: add support for MCP998X
Date: Mon, 9 Feb 2026 14:46:55 +0000 [thread overview]
Message-ID: <049f04c549bbea2f22b4fdab485beaa86af1b7db.camel@microchip.com> (raw)
In-Reply-To: <a9d4b53f-d8c2-4b31-aa13-901838c2933c@kernel.org>
Hi Krzysztof,
> > +
> > + interrupts:
> > + items:
> > + - description: Signal coming from ALERT/THERM pin.
> > + - description: Signal coming from THERM/ADDR pin.
> > + - description: Signal coming from SYS_SHDN pin.
>
> As Guenter pointed out - code is wrong (thanks Guenter!)
>
> This does not match your if:then:.
>
> > +
> > + interrupt-names:
> > + items:
> > + - const: alert-therm
> > + - const: therm-addr
> > + - const: sys-shutdown
>
> Neither this.
>
>
> ...
>
> > + then:
> > + properties:
> > + interrupts-names:
> > + items:
> > + - const: alert-therm
> > + - const: sys-shutdown
>
> So three interrupts, but two AND three interrupt-names? This is mess.
I was mistakenly under the impression that I could set two out of three
possible interrupts depending on the chip. But I understand now that
in the code written as is all chips have three interrupts.
Indeed, this error was present multiple versions in the past and you
identified it in v4 of the IIO driver. I failed to fix it then, I
apologize.
I will use two interrupts only and remove the if:then code regarding
them.
Kind Regards,
Victor
next prev parent reply other threads:[~2026-02-09 14:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 15:18 [PATCH v3 0/2] add support in hwmon for MCP998X victor.duicu
2026-01-27 15:18 ` [PATCH v3 1/2] dt-bindings: hwmon: add support " victor.duicu
2026-02-03 19:15 ` Guenter Roeck
2026-02-06 14:17 ` Victor.Duicu
2026-02-06 16:49 ` Krzysztof Kozlowski
2026-02-06 16:51 ` Krzysztof Kozlowski
2026-02-06 16:47 ` Krzysztof Kozlowski
2026-02-09 14:46 ` Victor.Duicu [this message]
2026-01-27 15:18 ` [PATCH v3 2/2] " victor.duicu
2026-01-27 18:51 ` Guenter Roeck
2026-02-02 8:15 ` Victor.Duicu
2026-02-02 15:18 ` Guenter Roeck
2026-02-03 13:31 ` Victor.Duicu
2026-01-27 22:23 ` kernel test robot
2026-02-03 19:45 ` Guenter Roeck
2026-02-03 20:09 ` Guenter Roeck
2026-02-03 20:45 ` Guenter Roeck
2026-02-06 16:55 ` [PATCH v3 0/2] add support in hwmon " 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=049f04c549bbea2f22b4fdab485beaa86af1b7db.camel@microchip.com \
--to=victor.duicu@microchip.com \
--cc=Marius.Cristea@microchip.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--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=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