devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	gregkh@linuxfoundation.org, krzysztof.kozlowski+dt@linaro.org,
	vkoul@kernel.org, treding@nvidia.com, linux-usb@vger.kernel.org,
	devicetree@vger.kernel.org, linux-phy@lists.infradead.org,
	linux-tegra@vger.kernel.org, waynec@nvidia.com
Subject: Re: [PATCH V4 6/6] dt-bindings: phy: tegra-xusb: Add support for Tegra234
Date: Fri, 2 Dec 2022 09:53:48 +0000	[thread overview]
Message-ID: <6c664b5c-aea8-883f-c278-e010b95e5b84@nvidia.com> (raw)
In-Reply-To: <20221130170709.GA2454510-robh@kernel.org>


On 30/11/2022 17:07, Rob Herring wrote:
> On Fri, Nov 18, 2022 at 03:40:06PM +0000, Jon Hunter wrote:
>> Add the compatible string for the Tegra234 XUSB PHY.
>>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>> This is a new patch in this version of the series. This patch is
>> dependent upon the following patch.
>>
>> https://lore.kernel.org/linux-tegra/20221118144015.3650774-1-thierry.reding@gmail.com/
>>
>>   .../devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml  | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml b/Documentation/devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml
>> index 1c570ff65eb4..5302fdb0949c 100644
>> --- a/Documentation/devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml
>> +++ b/Documentation/devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml
>> @@ -42,7 +42,9 @@ description:
>>   
>>   properties:
>>     compatible:
>> -    const: nvidia,tegra194-xusb-padctl
>> +    enum:
>> +      - nvidia,tegra194-xusb-padctl
>> +      - nvidia,tegra194-xusb-padctl
> 
> Did you test this because I'm pretty sure you would get an error. The
> bot didn't test because of the dependency.


Indeed. My fault for trying to juggle too many things at once. OK will 
correct this.

Jon

-- 
nvpublic

      reply	other threads:[~2022-12-02  9:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 15:40 [PATCH V4 0/6] Enable USB host on Jetson AGX Orin Jon Hunter
2022-11-18 15:40 ` [PATCH V4 1/6] dt-bindings: usb: Add NVIDIA Tegra234 XUSB host controller binding Jon Hunter
2022-11-18 18:50   ` Rob Herring
2022-11-18 15:40 ` [PATCH V4 2/6] arm64: tegra: Enable XUSB host function on Jetson AGX Orin Jon Hunter
2022-11-18 15:40 ` [PATCH V4 3/6] phy: tegra: xusb: Disable trk clk when not in use Jon Hunter
2022-11-18 15:40 ` [PATCH V4 4/6] phy: tegra: xusb: Add Tegra234 support Jon Hunter
2022-11-18 15:40 ` [PATCH V4 5/6] usb: host: xhci-tegra: Add Tegra234 XHCI support Jon Hunter
2022-11-22 16:07   ` Greg KH
2022-11-23 14:20     ` Jon Hunter
2022-11-24 12:30       ` Wayne Chang
2022-11-18 15:40 ` [PATCH V4 6/6] dt-bindings: phy: tegra-xusb: Add support for Tegra234 Jon Hunter
2022-11-30 17:07   ` Rob Herring
2022-12-02  9:53     ` Jon Hunter [this message]

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=6c664b5c-aea8-883f-c278-e010b95e5b84@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=robh@kernel.org \
    --cc=treding@nvidia.com \
    --cc=vkoul@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).