All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	devicetree@vger.kernel.org
Subject: strange dtbs_check error message regarding 8250_omap.yaml + serdev + gnss
Date: Fri, 1 Oct 2021 10:22:37 +0200	[thread overview]
Message-ID: <20211001102237.4db23bff@aktux> (raw)

Hi,

while doing some make dtbs_check cleanup I came across this message:

/home/andi/kernel/linux/arch/arm/boot/dts/omap3-gta04a4.dt.yaml: serial@4806c000: 'gnss' does not match any of the regexes: 'pinctrl-[0-9]+'
        From schema: /home/andi/kernel/linux/Documentation/devicetree/bindings/serial/8250_omap.yaml

the corresponding snippet is this one:

&uart2 {
        pinctrl-names = "default";
        pinctrl-0 = <&uart2_pins>;
        gnss: gnss {
                compatible = "wi2wi,w2sg0004";
                pinctrl-names = "default";
                pinctrl-0 = <&gps_pins>;
                sirf,onoff-gpios = <&gpio5 17 GPIO_ACTIVE_HIGH>;
                lna-supply = <&vsim>;
                vcc-supply = <&ldo_3v3>;
        };
};


I see a pattern for serdev objects in
Documentation/devicetree/bindings/serial/serial.yaml

patternProperties:
  ".*":
    if:
      type: object
    then:
      description:
        Serial attached devices shall be a child node of the host UART device
        the slave device is attached to. It is expected that the attached
        device is the only child node of the UART device. The slave device node
        name shall reflect the generic type of device for the node.


so I would say, everything is allowed. serial.yaml is referenced by
8250_omap.yaml. So what is the problem here?

Regards,
Andreas

             reply	other threads:[~2021-10-01  8:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  8:22 Andreas Kemnade [this message]
2021-10-01 14:45 ` strange dtbs_check error message regarding 8250_omap.yaml + serdev + gnss Rob Herring

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=20211001102237.4db23bff@aktux \
    --to=andreas@kemnade.info \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=vigneshr@ti.com \
    /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.