From: Francesco Valla <francesco@valla.it>
To: sashiko-reviews@lists.linux.dev
Cc: devicetree@vger.kernel.org, virtualization@lists.linux.dev,
Eugenio Perez <eperezma@redhat.com>,
robh@kernel.org, conor+dt@kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 1/2] dt-bindings: spi: add bindings for spi-virtio
Date: Wed, 30 Sep 2026 08:19:08 +0200 [thread overview]
Message-ID: <arypmHeudsJm4RIN@bywater> (raw)
In-Reply-To: <20260929165015.E5DDF1F000FF@smtp.kernel.org>
On Tue, Sep 29, 2026 at 04:50:14PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] dt-bindings: spi-virtio: undocumented compatible in example
> --
>
> commit eb6ae8a9a8b3aa403347f70589897a8c7d297186
> Author: Francesco Valla <francesco@valla.it>
>
> dt-bindings: spi: add bindings for spi-virtio
>
> This commit adds device tree bindings for spi-virtio based on virtio-device.
> It defines the properties and node dependencies for the virtio SPI controller.
>
> > diff --git a/Documentation/devicetree/bindings/spi/spi-virtio.yaml b/Documentation/devicetree/bindings/spi/spi-virtio.yaml
> > new file mode 100644
> > index 0000000000000..5b8639dd2e1f1
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/spi/spi-virtio.yaml
>
> [ ... ]
>
> > +examples:
> > + - |
> > + virtio@3000 {
> > + compatible = "virtio,mmio";
> > + reg = <0x3000 0x100>;
> > + interrupts = <41>;
> > +
> > + spi {
> > + compatible = "virtio,device2d";
> > +
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + sram@0 {
> > + compatible = "microchip,mchp23k256";
>
> [Severity: Low]
> Is this compatible string documented in any existing binding schema?
>
Yes - the compatible fot the Microchip MCHP23K256 is documented in:
Documentation/devicetree/bindings/mtd/microchip,mchp23k256.yaml
> The dt_binding_check tool strictly validates all compatible strings against
> known schemas, so an undocumented compatible string in an example will emit a
> schema validation warning.
>
> When running make dt_binding_check on the new spi-virtio.yaml file, it
> parses the example and attempts to match microchip,mchp23k256 against
> registered bindings, which fails if none exist.
>
> > + reg = <0>;
> > + spi-max-frequency = <20000000>;
> > + };
> > + };
> > + };
> > +
> > +...
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260929-spi-virtio-bindings-v1-0-6a0eef3213b3@valla.it?part=1
next prev parent reply other threads:[~2026-09-30 6:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 16:41 [PATCH 0/2] Add devicetree bindings for spi-virtio Francesco Valla
2026-09-29 16:41 ` [PATCH 1/2] dt-bindings: spi: add " Francesco Valla
2026-09-29 16:50 ` sashiko-bot
2026-09-30 6:19 ` Francesco Valla [this message]
2026-09-30 12:03 ` Krzysztof Kozlowski
2026-09-30 16:22 ` Francesco Valla
2026-09-29 16:41 ` [PATCH 2/2] MAINTAINERS: add Francesco as spi-virtio reviewer Francesco Valla
2026-09-30 11:58 ` [PATCH 0/2] Add devicetree bindings for spi-virtio Krzysztof Kozlowski
2026-09-30 16:01 ` Francesco Valla
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=arypmHeudsJm4RIN@bywater \
--to=francesco@valla.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@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