From: sashiko-bot@kernel.org
To: "Jinseob Kim" <kimjinseob88@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v7 1/5] dt-bindings: iio: add Open Sensor Fusion device
Date: Tue, 07 Jul 2026 01:50:21 +0000 [thread overview]
Message-ID: <20260707015022.06B3E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260707014525.1015-2-kimjinseob88@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The Device Tree binding intentionally omits the specific hardware product identity, restricting the `compatible` property to a generic protocol-level string.
--
--- Patch [1]: [PATCH v7 1/5] dt-bindings: iio: add Open Sensor Fusion device ---
commit 427a1ffc9a3a61dc0d7c28ad4dfc48f800f94f69
Author: Jinseob Kim <kimjinseob88@gmail.com>
dt-bindings: iio: add Open Sensor Fusion device
This commit introduces a binding for the generic Open Sensor Fusion host
interface. It specifies that sensor channels and protocol versions are
discovered at runtime, and sets the compatible string to a generic protocol
identifier.
> diff --git a/Documentation/devicetree/bindings/iio/opensensorfusion,osf.yaml b/Documentation/devicetree/bindings/iio/opensensorfusion,osf.yaml
> new file mode 100644
> index 0000000000000..3998390828cc0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/opensensorfusion,osf.yaml
[ ... ]
> +allOf:
> + - $ref: /schemas/serial/serial-peripheral-props.yaml#
> +
> +properties:
> + compatible:
> + const: opensensorfusion,osf
[Severity: Medium]
Will omitting the specific hardware identity prevent the kernel from applying
hardware-specific quirks in the future?
The commit message notes that OSF GREEN is a product identity and intentionally
omitted from the compatible string. However, device trees are expected to
describe specific hardware, not just the generic protocol it speaks.
If the specific hardware requires workarounds in the future, such as power
sequencing adjustments, delays before the protocol responds, or errata
handling, the kernel will have no way to apply them because the device tree
only identifies it as a generic device.
Could the binding be updated to allow specific hardware compatible strings
alongside the generic fallback, rather than restricting it to a single const
value?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260707014525.1015-1-kimjinseob88@gmail.com?part=1
next prev parent reply other threads:[~2026-07-07 1:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 1:45 [PATCH v7 0/5] iio: add Open Sensor Fusion IIO driver Jinseob Kim
2026-07-07 1:45 ` [PATCH v7 1/5] dt-bindings: iio: add Open Sensor Fusion device Jinseob Kim
2026-07-07 1:50 ` sashiko-bot [this message]
2026-07-07 1:45 ` [PATCH v7 2/5] Documentation: iio: add Open Sensor Fusion driver overview Jinseob Kim
2026-07-07 4:07 ` Randy Dunlap
2026-07-07 1:45 ` [PATCH v7 3/5] iio: osf: add protocol decoding Jinseob Kim
2026-07-07 1:51 ` sashiko-bot
2026-07-07 1:45 ` [PATCH v7 4/5] iio: osf: add authenticated stream parser Jinseob Kim
2026-07-07 1:45 ` [PATCH v7 5/5] iio: osf: add UART IIO driver Jinseob Kim
2026-07-07 8:47 ` Uwe Kleine-König
2026-07-07 8:48 ` Uwe Kleine-König
2026-07-07 9:00 ` Joshua Crofts
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=20260707015022.06B3E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kimjinseob88@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.