From: Romain Gantois <romain.gantois@bootlin.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-hwmon@vger.kernel.org, conor+dt@kernel.org,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-binding: hwmon: Add binding for ADT7462
Date: Wed, 03 Jun 2026 14:02:33 +0200 [thread overview]
Message-ID: <2eAABoDhQ5ih8u_5nmvpxw@bootlin.com> (raw)
In-Reply-To: <20260603113526.232F61F00898@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
On Wednesday, 3 June 2026 13:35:25 CEST sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue(s) to consider: - [Medium] Incomplete binding migration:
> `onnn,adt7462` is not migrated to the new schema and remains in
> `trivial-devices.yaml`. --
>
> commit 8e3b73cf675c7a9534a713ae61c15469f85f0d06
> Author: Kory Maincent <kory.maincent@bootlin.com>
>
> dt-binding: hwmon: Add binding for ADT7462
>
> This commit adds the ADT7462 hwmon Controller device tree bindings
> documentation.
>
> > diff --git a/Documentation/devicetree/bindings/hwmon/adt7462.yaml
> > b/Documentation/devicetree/bindings/hwmon/adt7462.yaml new file mode
> > 100644
> > index 0000000000000..745a371affd65
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/hwmon/adt7462.yaml
>
> [ ... ]
>
> > +properties:
> > + compatible:
> > + enum:
> > + - adi,adt7462
>
> [Severity: Medium]
> Should the existing onnn,adt7462 compatible string be migrated into this
> new schema?
>
> The ADT7462 device is already documented in trivial-devices.yaml under
> the compatible string onnn,adt7462, which is actively used in existing
> device trees.
>
> By introducing this new schema without including onnn,adt7462 and without
> removing it from trivial-devices.yaml, existing device trees will not
> benefit from the detailed schema validation. This also leaves the subsystem
> with two conflicting, fragmented representations of the same hardware.
I've just done a bit of research and it looks like this component is now
commercialized by Onsemi, so the existing compatible would be the correct one.
Furthermore, the suggested binding only has a "reg" property and a
"compatible" property, so it seems like the trivial-devices binding is enough
to describe it for now.
I'll drop patch 1/2 in version 2.
Thanks,
--
Romain Gantois, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-06-03 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 11:10 [PATCH 0/2] hwmon: (adt7462) Support probing via device tree Romain Gantois
2026-06-03 11:10 ` [PATCH 1/2] dt-binding: hwmon: Add binding for ADT7462 Romain Gantois
2026-06-03 11:35 ` sashiko-bot
2026-06-03 12:02 ` Romain Gantois [this message]
2026-06-03 11:10 ` [PATCH 2/2] hwmon: (adt7462) Add of_match_table to support devicetree Romain Gantois
2026-06-03 11:40 ` sashiko-bot
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=2eAABoDhQ5ih8u_5nmvpxw@bootlin.com \
--to=romain.gantois@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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