All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jon Hunter <jonathanh@nvidia.com>,
	Wayne Chang <waynec@nvidia.com>, <devicetree@vger.kernel.org>,
	<linux-usb@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: usb: tegra-xusb: Convert to json-schema
Date: Fri, 25 Nov 2022 12:41:46 +0000	[thread overview]
Message-ID: <Y4C4Cp1D+QEKWiaf@wendy> (raw)
In-Reply-To: <20221103144200.1479640-1-thierry.reding@gmail.com>

Hi Thierry,

On Thu, Nov 03, 2022 at 03:42:00PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Convert the Tegra XUSB controller bindings from the free-form text
> format to json-schema.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>

> +        phys = <&{/padctl@0,7009f000/pads/usb2/lanes/usb2-1}>, /* mini-PCIe USB */
> +               <&{/padctl@0,7009f000/pads/usb2/lanes/usb2-2}>, /* USB A */
> +               <&{/padctl@0,7009f000/pads/pcie/lanes/pcie-0}>; /* USB A */

This seems to be breaking dt_binding_check in today's linux-next:
FATAL ERROR: Can't generate fixup for reference to path &{/padctl@0,7009f000/pads/usb2/lanes/usb2-1}

Am I missing something? My dt-schema is today's main.

Thanks,
Conor.


  parent reply	other threads:[~2022-11-25 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 14:42 [PATCH v2] dt-bindings: usb: tegra-xusb: Convert to json-schema Thierry Reding
2022-11-07 19:52 ` Rob Herring
2022-11-18 12:25   ` Thierry Reding
2022-11-25 12:41 ` Conor Dooley [this message]
2022-11-25 12:59   ` Conor Dooley
2022-11-25 14:01     ` Conor Dooley
2022-11-27 16:38     ` 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=Y4C4Cp1D+QEKWiaf@wendy \
    --to=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=waynec@nvidia.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.