From: Vinod Koul <vkoul@kernel.org>
To: Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Yixun Lan <dlan@gentoo.org>,
Ze Huang <huang.ze@linux.dev>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org, Ze Huang <huangze@whut.edu.cn>
Subject: Re: [PATCH v6 0/2] Add USB2.0 PHY support for SpacemiT K1
Date: Thu, 01 Jan 2026 16:38:14 +0530 [thread overview]
Message-ID: <176726569400.201416.7844610224983761844.b4-ty@kernel.org> (raw)
In-Reply-To: <20251017-k1-usb2phy-v6-0-7cf9ea2477a1@linux.dev>
On Fri, 17 Oct 2025 22:49:51 +0800, Ze Huang wrote:
> This patch series introduces support for the USB2.0 PHY on the SpacemiT
> K1 SoC. The implementation has been tested on the Milk-V Jupiter and
> BananaPi-f3.
>
> K1 includes three USB ports as follows[1]:
> - A USB2.0 OTG Port
> - A USB2.0 Host Only Port
> - A USB3.0 Port with a USB2.0 DRD interface
>
> [...]
Applied, thanks!
[1/2] dt-bindings: phy: spacemit: add K1 USB2 PHY
commit: 61b84d5b20af2a4c9944972202c1386026598928
[2/2] phy: spacemit: support K1 USB2.0 PHY controller
commit: fe4bc1a08638309b6be1af37210930b856908eb7
Best regards,
--
~Vinod
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-01-01 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 14:49 [PATCH v6 0/2] Add USB2.0 PHY support for SpacemiT K1 Ze Huang
2025-10-17 14:49 ` [PATCH v6 1/2] dt-bindings: phy: spacemit: add K1 USB2 PHY Ze Huang
2025-10-17 14:49 ` [PATCH v6 2/2] phy: spacemit: support K1 USB2.0 PHY controller Ze Huang
2025-12-01 14:17 ` Ze Huang
2025-12-27 2:01 ` [PATCH v6 0/2] Add USB2.0 PHY support for SpacemiT K1 Junzhong Pan
2025-12-29 20:14 ` Aurelien Jarno
2026-01-01 11:08 ` Vinod Koul [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=176726569400.201416.7844610224983761844.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=huang.ze@linux.dev \
--cc=huangze@whut.edu.cn \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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