From: Rob Herring <robh@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Fabio Estevam <festevam@gmail.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Kaehlcke <mka@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel@pengutronix.de, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v4 4/5] dt-bindings: usb: microchip,usb2514: add vbus-supply example
Date: Fri, 12 Sep 2025 09:11:58 -0500 [thread overview]
Message-ID: <20250912141158.GA1330389-robh@kernel.org> (raw)
In-Reply-To: <20250912085156.h4hhye5vc2rbntyl@pengutronix.de>
On Fri, Sep 12, 2025 at 10:51:56AM +0200, Marco Felsch wrote:
> On 25-09-11, Rob Herring (Arm) wrote:
> >
> > On Thu, 11 Sep 2025 22:22:45 +0200, Marco Felsch wrote:
> > > Add an usb hub vbus-supply example to make it easier for users to
> > > understand the binding, after the usb-device.yaml gained the support for
> > > it.
> > >
> > > Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> > > ---
> > > Documentation/devicetree/bindings/usb/microchip,usb2514.yaml | 7 +++++++
> > > 1 file changed, 7 insertions(+)
> > >
> >
> > My bot found errors running 'make dt_binding_check' on your patch:
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/usb/microchip,usb2514.example.dtb: ethernet@2 (usbb95,772b): 'vbus-supply' does not match any of the regexes: '^pinctrl-[0-9]+$'
> > from schema $id: http://devicetree.org/schemas/net/asix,ax88178.yaml#
>
> Well this is just an example on how to use it, we can drop this patch of
> course.
Yes, but how's it going to work for an actual user?
Rob
next prev parent reply other threads:[~2025-09-12 14:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 20:22 [PATCH v4 0/5] Add onboard-dev USB hub host managed vbus handling support Marco Felsch
2025-09-11 20:22 ` [PATCH v4 1/5] usb: port: track the disabled state Marco Felsch
2025-09-11 20:22 ` [PATCH v4 2/5] usb: hub: add infrastructure to pass onboard_dev port features Marco Felsch
2025-09-11 20:22 ` [PATCH v4 3/5] dt-bindings: usb: usb-device: add usb hub port vbus-supply suppport Marco Felsch
2025-09-15 20:58 ` Rob Herring
2025-09-11 20:22 ` [PATCH v4 4/5] dt-bindings: usb: microchip,usb2514: add vbus-supply example Marco Felsch
2025-09-12 0:17 ` Rob Herring (Arm)
2025-09-12 8:51 ` Marco Felsch
2025-09-12 14:11 ` Rob Herring [this message]
2025-09-12 15:30 ` Marco Felsch
2025-09-11 20:22 ` [PATCH v4 5/5] usb: misc: onboard_dev: add hub downstream port host vbus-supply handling Marco Felsch
2026-02-10 6:23 ` [PATCH v4 0/5] Add onboard-dev USB hub host managed vbus handling support Ze Huang
2026-02-10 12:32 ` Marco Felsch
2026-02-10 13:20 ` Greg Kroah-Hartman
2026-02-23 11:29 ` Marco Felsch
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=20250912141158.GA1330389-robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=mka@chromium.org \
/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