On Wed, Jan 10, 2024 at 1:51 PM David Lechner <dlechner@xxxxxxxxxxxx> wrote:
>
> According to the spi-controller.yaml bindings, SPI peripheral child
> nodes match the pattern "^.*@[0-9a-f]+$".
>
> A SPI controller binding may require a child object node that is not a
> peripheral. For example, the adi,axi-spi-engine binding requires an
> "offloads" child node that is not a peripheral but rather a part of the
> controller itself.
>
> By checking for '@' in the node name, we can avoids a warnings like:
>
> Warning (spi_bus_reg): /example-0/spi@44a00000/offloads: missing or empty reg property
>
> for a binding like:
>
> spi {
> ...
>
> offloads {
> offload@0 {
> ...
> };
> ...
> };
>
> peripheral@0 {
> ...
> };
> };
>
> Signed-off-by: David Lechner <dlechner@xxxxxxxxxxxx>
> ---
> scripts/dtc/checks.c | 4 ++++
> 1 file changed, 4 insertions(+)
Check the commit history. We don't take changes to kernel's dtc copy.
They must go upstream first.
Rob
