From: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>
To: gregkh@linuxfoundation.org, hminas@synopsys.com,
robh+dt@kernel.org, krzk+dt@kernel.org,
tsbogend@alpha.franken.de, paul@crapouillou.net
Cc: linux-usb@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
dongsheng.qiu@ingenic.com, aric.pzqi@ingenic.com,
rick.tyliu@ingenic.com, sernia.zhou@foxmail.com,
zhenwenjin@gmail.com, reimu@sudomaker.com
Subject: [PATCH v4 3/3] MIPS: Ingenic: Refresh USB nodes to match driver changes.
Date: Fri, 22 Apr 2022 01:15:08 +0800 [thread overview]
Message-ID: <1650561308-54704-4-git-send-email-zhouyanjie@wanyeetech.com> (raw)
In-Reply-To: <1650561308-54704-1-git-send-email-zhouyanjie@wanyeetech.com>
Refresh USB nodes in the jz4780.dtsi, x1000.dtsi, and x1830.dtsi files.
Signed-off-by: 周琰杰 (Zhou Yanjie) <zhouyanjie@wanyeetech.com>
---
Notes:
v3:
New patch.
v3->v4:
No change.
arch/mips/boot/dts/ingenic/jz4780.dtsi | 2 +-
arch/mips/boot/dts/ingenic/x1000.dtsi | 2 +-
arch/mips/boot/dts/ingenic/x1830.dtsi | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/mips/boot/dts/ingenic/jz4780.dtsi b/arch/mips/boot/dts/ingenic/jz4780.dtsi
index b998301..c182a65 100644
--- a/arch/mips/boot/dts/ingenic/jz4780.dtsi
+++ b/arch/mips/boot/dts/ingenic/jz4780.dtsi
@@ -577,7 +577,7 @@
};
otg: usb@13500000 {
- compatible = "ingenic,jz4780-otg", "snps,dwc2";
+ compatible = "ingenic,jz4780-otg";
reg = <0x13500000 0x40000>;
interrupt-parent = <&intc>;
diff --git a/arch/mips/boot/dts/ingenic/x1000.dtsi b/arch/mips/boot/dts/ingenic/x1000.dtsi
index 8bd27ede..343818a2 100644
--- a/arch/mips/boot/dts/ingenic/x1000.dtsi
+++ b/arch/mips/boot/dts/ingenic/x1000.dtsi
@@ -366,7 +366,7 @@
};
otg: usb@13500000 {
- compatible = "ingenic,x1000-otg", "snps,dwc2";
+ compatible = "ingenic,x1000-otg";
reg = <0x13500000 0x40000>;
interrupt-parent = <&intc>;
diff --git a/arch/mips/boot/dts/ingenic/x1830.dtsi b/arch/mips/boot/dts/ingenic/x1830.dtsi
index 2595df8..6aff19f 100644
--- a/arch/mips/boot/dts/ingenic/x1830.dtsi
+++ b/arch/mips/boot/dts/ingenic/x1830.dtsi
@@ -355,7 +355,7 @@
};
otg: usb@13500000 {
- compatible = "ingenic,x1830-otg", "snps,dwc2";
+ compatible = "ingenic,x1830-otg";
reg = <0x13500000 0x40000>;
interrupt-parent = <&intc>;
--
2.7.4
next prev parent reply other threads:[~2022-04-21 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 17:15 [PATCH v4 0/3] Add OTG support for Ingenic SoCs 周琰杰 (Zhou Yanjie)
2022-04-21 17:15 ` [PATCH v4 1/3] dt-bindings: dwc2: Add bindings for new " 周琰杰 (Zhou Yanjie)
2022-04-22 12:44 ` Paul Cercueil
2022-04-22 17:57 ` Zhou Yanjie
2022-04-21 17:15 ` [PATCH v4 2/3] USB: dwc2: Add OTG support for " 周琰杰 (Zhou Yanjie)
2022-04-21 17:15 ` 周琰杰 (Zhou Yanjie) [this message]
2022-04-22 8:30 ` [PATCH v4 0/3] " Greg KH
2022-04-22 15:57 ` Zhou Yanjie
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=1650561308-54704-4-git-send-email-zhouyanjie@wanyeetech.com \
--to=zhouyanjie@wanyeetech.com \
--cc=aric.pzqi@ingenic.com \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.qiu@ingenic.com \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=reimu@sudomaker.com \
--cc=rick.tyliu@ingenic.com \
--cc=robh+dt@kernel.org \
--cc=sernia.zhou@foxmail.com \
--cc=tsbogend@alpha.franken.de \
--cc=zhenwenjin@gmail.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).