Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bhargav Joshi <j.bhargav.u@gmail.com>
To: Nishanth Menon <nm@ti.com>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	 Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org, j.bhargav.u@gmail.com
Subject: [PATCH 1/2] ARM: dts: keystone-k2g: Add required #phy-cells to usb-nop-xceiv nodes
Date: Fri, 11 Sep 2026 02:22:50 +0530	[thread overview]
Message-ID: <20260911-ti-keystone-usb-phy-fix-v1-1-9f6e9cd649a3@gmail.com> (raw)
In-Reply-To: <20260911-ti-keystone-usb-phy-fix-v1-0-9f6e9cd649a3@gmail.com>

The usb-nop-xceiv binding requires "#phy-cells" with a value of 0.
usb0_phy and usb1_phy are missing it. Add the required property.

Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
---
 arch/arm/boot/dts/ti/keystone/keystone-k2g.dtsi | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/boot/dts/ti/keystone/keystone-k2g.dtsi b/arch/arm/boot/dts/ti/keystone/keystone-k2g.dtsi
index dafe485dfe19..5a63874090eb 100644
--- a/arch/arm/boot/dts/ti/keystone/keystone-k2g.dtsi
+++ b/arch/arm/boot/dts/ti/keystone/keystone-k2g.dtsi
@@ -77,12 +77,14 @@ usbphy {
 		usb0_phy: usb-phy@0 {
 			compatible = "usb-nop-xceiv";
 			reg = <0>;
+			#phy-cells = <0>;
 			status = "disabled";
 		};
 
 		usb1_phy: usb-phy@1 {
 			compatible = "usb-nop-xceiv";
 			reg = <1>;
+			#phy-cells = <0>;
 			status = "disabled";
 		};
 	};

-- 
2.55.0



  reply	other threads:[~2026-09-10 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 20:52 [PATCH 0/2] ARM: dts: keystone-k2g: Fix usb-nop-xceiv dtbs_check warnings Bhargav Joshi
2026-09-10 20:52 ` Bhargav Joshi [this message]
2026-09-10 20:52 ` [PATCH 2/2] ARM: dts: keystone-k2g: Move usb-phy nodes out of simple-bus Bhargav Joshi

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=20260911-ti-keystone-usb-phy-fix-v1-1-9f6e9cd649a3@gmail.com \
    --to=j.bhargav.u@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=ssantosh@kernel.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