[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c2112fcd-187a-73dd-22e4-631500a6b648@nvidia.com>
Date: Mon, 24 Oct 2022 16:58:53 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Rob Herring <robh@...nel.org>, Wayne Chang <waynec@...dia.com>
Cc: linux-phy@...ts.infradead.org, robh+dt@...nel.org,
gregkh@...uxfoundation.org, kishon@...com, vkoul@...nel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
singhanc@...dia.com, linux-i2c@...r.kernel.org,
mathias.nyman@...el.com, heikki.krogerus@...ux.intel.com,
linux-usb@...r.kernel.org, thierry.reding@...il.com,
devicetree@...r.kernel.org, treding@...dia.com,
krzysztof.kozlowski+dt@...aro.org, balbi@...nel.org,
ajayg@...dia.com, jckuo@...dia.com, p.zabel@...gutronix.de
Subject: Re: [PATCH 02/11] dt-bindings: usb: Add NVIDIA Tegra XUSB host
controller binding
On 24/10/2022 14:30, Rob Herring wrote:
> On Mon, 24 Oct 2022 15:41:19 +0800, Wayne Chang wrote:
>> Add device-tree binding documentation for the XUSB host controller present
>> on Tegra194 and Tegra234 SoC. This controller supports the USB 3.1
>> specification.
>>
>> Signed-off-by: Wayne Chang <waynec@...dia.com>
>> ---
>> .../bindings/usb/nvidia,tegra-xhci.yaml | 213 ++++++++++++++++++
>> 1 file changed, 213 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/usb/nvidia,tegra-xhci.yaml
>>
>
> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> on your patch (DT_CHECKER_FLAGS is new in v5.13):
>
> yamllint warnings/errors:
>
> dtschema/dtc warnings/errors:
> Error: Documentation/devicetree/bindings/usb/nvidia,tegra-xhci.example.dts:36.27-28 syntax error
> FATAL ERROR: Unable to parse input tree
> make[1]: *** [scripts/Makefile.lib:406: Documentation/devicetree/bindings/usb/nvidia,tegra-xhci.example.dtb] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make: *** [Makefile:1492: dt_binding_check] Error 2
I believe that this is because another DT patch [0] is missing (see
patch 0/11). Thierry has just picked this up for -next and so hopefully
will resolve this.
Cheers
Jon
[0]
https://lore.kernel.org/all/20221003125141.123759-1-jonathanh@nvidia.com/
--
nvpublic
Powered by blists - more mailing lists