From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [RFC 0/7] rockchip: Add PHY drivers
Date: Fri, 1 May 2020 03:15:22 +0530 [thread overview]
Message-ID: <20200430214529.18887-1-jagan@amarulasolutions.com> (raw)
This patch add support for USB2PHY and PCIe PHY driver
on rockchip platform and tested the same in rk3399.
Basic code is referenced from Linux, hence all the
license SPDX are reused.
The reason behind sending this as RFC is PHY devices
for u2phy, pcie_phy nodes are unable to get via
Generic PHY framework. The observed reasons are
1) u2phy is not part of root node.
2) pcie_phy is not part of root node and also parent
is of non-PHY type.
This is sample PHY provider topology that Generic PHY
is failed to get PHY device.
/{
grf: syscon at ff770000 {
compatible = "rockchip,rk3399-grf", "syscon", "simple-mfd";
reg = <0x0 0xff770000 0x0 0x10000>;
#address-cells = <1>;
#size-cells = <1>;
u2phy0: usb2-phy at e450 {
compatible = "rockchip,rk3399-usb2phy";
reg = <0xe450 0x10>;
clocks = <&cru SCLK_USB2PHY0_REF>;
clock-names = "phyclk";
#clock-cells = <0>;
clock-output-names = "clk_usbphy0_480m";
status = "disabled";
u2phy0_host: host-port {
#phy-cells = <0>;
interrupts = <GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH 0>;
interrupt-names = "linestate";
status = "disabled";
};
u2phy0_otg: otg-port {
#phy-cells = <0>;
interrupts = <GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH 0>,
<GIC_SPI 104 IRQ_TYPE_LEVEL_HIGH 0>,
<GIC_SPI 106 IRQ_TYPE_LEVEL_HIGH 0>;
interrupt-names = "otg-bvalid", "otg-id",
"linestate";
status = "disabled";
};
};
pcie_phy: pcie-phy {
compatible = "rockchip,rk3399-pcie-phy";
clocks = <&cru SCLK_PCIEPHY_REF>;
clock-names = "refclk";
#phy-cells = <1>;
resets = <&cru SRST_PCIEPHY>;
drive-impedance-ohm = <50>;
reset-names = "phy";
status = "disabled";
};
};
So, this series moved these nodes as part of root
to make it work but of course any suggestions on this
will be taken into consideration.
Any inputs?
Jagan.
Jagan Teki (7):
phy: Add Rockchip PCIe PHY driver
clk: rk3399: Enable/Disable the USB2PHY clk
phy: rockchip: Add Rockchip USB2PHY driver
arm64: dts: rk3399: Move u2phy into root port
arm64: dts: rk3399: Move pcie_phy into root port
pci: rockchip: Switch to generic-phy
pci: rockchip: Drop legacy PHY driver
arch/arm/dts/rk3399.dtsi | 118 +++----
drivers/Kconfig | 2 +
drivers/Makefile | 1 +
drivers/clk/rockchip/clk_rk3399.c | 12 +
drivers/pci/Makefile | 2 +-
drivers/pci/pcie_rockchip.c | 95 +++++-
drivers/pci/pcie_rockchip.h | 142 --------
drivers/pci/pcie_rockchip_phy.c | 205 ------------
drivers/phy/rockchip/Kconfig | 16 +
drivers/phy/rockchip/Makefile | 7 +
drivers/phy/rockchip/phy-rockchip-inno-usb2.c | 312 ++++++++++++++++++
drivers/phy/rockchip/phy-rockchip-pcie.c | 271 +++++++++++++++
12 files changed, 764 insertions(+), 419 deletions(-)
delete mode 100644 drivers/pci/pcie_rockchip.h
delete mode 100644 drivers/pci/pcie_rockchip_phy.c
create mode 100644 drivers/phy/rockchip/Kconfig
create mode 100644 drivers/phy/rockchip/Makefile
create mode 100644 drivers/phy/rockchip/phy-rockchip-inno-usb2.c
create mode 100644 drivers/phy/rockchip/phy-rockchip-pcie.c
--
2.17.1
next reply other threads:[~2020-04-30 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 21:45 Jagan Teki [this message]
2020-04-30 21:45 ` [RFC 1/7] phy: Add Rockchip PCIe PHY driver Jagan Teki
2020-04-30 21:45 ` [RFC 2/7] clk: rk3399: Enable/Disable the USB2PHY clk Jagan Teki
2020-04-30 21:45 ` [RFC 3/7] phy: rockchip: Add Rockchip USB2PHY driver Jagan Teki
2020-04-30 21:45 ` [RFC 4/7] arm64: dts: rk3399: Move u2phy into root port Jagan Teki
2020-04-30 21:45 ` [RFC 5/7] arm64: dts: rk3399: Move pcie_phy " Jagan Teki
2020-04-30 21:45 ` [RFC 6/7] pci: rockchip: Switch to generic-phy Jagan Teki
2020-04-30 21:45 ` [RFC 7/7] pci: rockchip: Drop legacy PHY driver Jagan Teki
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=20200430214529.18887-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
/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