From: Inochi Amaoto <inochiama@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Minas Harutyunyan <hminas@synopsys.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Chen Wang <unicorn_wang@outlook.com>,
Inochi Amaoto <inochiama@gmail.com>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
sophgo@lists.linux.dev, Yixun Lan <dlan@gentoo.org>,
Longbin Li <looong.bin@gmail.com>
Subject: [PATCH 0/2] riscv: sophgo: rename compatible string of the USB device for cv18xx
Date: Wed, 18 Jun 2025 11:11:28 +0800 [thread overview]
Message-ID: <20250618031132.373216-1-inochiama@gmail.com> (raw)
Old days I added the USB support with a wildcard compatible string.
It is not formal and it is more clear to use a compatible for a
real world SoC. As the usb device is not used in any board device
tree (The patch for USB phy is under review), I think it is good
to correct this mistake before submitting the device node.
Inochi Amaoto (2):
dt-bindings: usb: dwc2: rename sophgo usb compatible string
usb: dwc2: follow compatible string change for Sophgo CV18XX/SG200X
series SoC
Documentation/devicetree/bindings/usb/dwc2.yaml | 2 +-
drivers/usb/dwc2/params.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-18 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 3:11 Inochi Amaoto [this message]
2025-06-18 3:11 ` [PATCH 1/2] dt-bindings: usb: dwc2: rename sophgo usb compatible string Inochi Amaoto
2025-06-18 3:11 ` [PATCH 2/2] usb: dwc2: follow compatible string change for Sophgo CV18XX/SG200X series SoC Inochi Amaoto
2025-06-20 5:50 ` Minas Harutyunyan
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=20250618031132.373216-1-inochiama@gmail.com \
--to=inochiama@gmail.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=looong.bin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@outlook.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