From: Heiko Stuebner <heiko@sntech.de>
To: vkoul@kernel.org, kishon@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] usb-phy support for the old rk3036 soc
Date: Sat, 3 May 2025 22:15:09 +0200 [thread overview]
Message-ID: <20250503201512.991277-1-heiko@sntech.de> (raw)
While trying to resurrect the rk3036 board in my boardfarm, I also
implemented the up to now missing usb2phy support.
The implementation is quite similar to the rk3128, except the not-
supported charger-detection, so its addition was quite simple.
Heiko Stuebner (3):
dt-bindings: phy: rockchip,inno-usb2phy: add rk3036 compatible
phy: rockchip: inno-usb2: add phy definition for rk3036
ARM: dts: rockchip: add rk3036 usb2phy nodes and enable them on kylin
.../bindings/phy/rockchip,inno-usb2phy.yaml | 2 ++
arch/arm/boot/dts/rockchip/rk3036-kylin.dts | 12 +++++++
arch/arm/boot/dts/rockchip/rk3036.dtsi | 35 +++++++++++++++++++
drivers/phy/rockchip/phy-rockchip-inno-usb2.c | 32 +++++++++++++++++
4 files changed, 81 insertions(+)
--
2.47.2
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next reply other threads:[~2025-05-03 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 20:15 Heiko Stuebner [this message]
2025-05-03 20:15 ` [PATCH 1/3] dt-bindings: phy: rockchip,inno-usb2phy: add rk3036 compatible Heiko Stuebner
2025-05-06 16:22 ` Conor Dooley
2025-05-03 20:15 ` [PATCH 2/3] phy: rockchip: inno-usb2: add phy definition for rk3036 Heiko Stuebner
2025-05-03 20:15 ` [PATCH 3/3] ARM: dts: rockchip: add rk3036 usb2phy nodes and enable them on kylin Heiko Stuebner
2025-05-14 11:37 ` (subset) [PATCH 0/3] usb-phy support for the old rk3036 soc Vinod Koul
2025-05-15 12:50 ` Heiko Stuebner
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=20250503201512.991277-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=vkoul@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