u-boot.git/drivers/phy/rockchip, branch v2024.07

Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet""

2024-05-19T14:16:36Z

When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman Signed-off-by: Tom Rini

Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"

2024-05-13T15:15:51Z

Roger Quadros says: Sync AM62 device tree files with Linux v6.9 and add in the missing bits in -u-boot.dtsi to get CPSW Ethernet working. CI testing: https://github.com/u-boot/u-boot/pull/534

phy: Remove and add needed includes

2024-05-07T14:00:56Z

Remove from this driver directory and when needed add missing include files directly. Signed-off-by: Tom Rini

phy: rockchip: usbdp: Adopt driver to work with upstream DT

2024-05-07T07:56:10Z

The upstream DT binding added in linux-phy next commit a75d8056e9fe ("dt-bindings: phy: add rockchip usbdp combo phy document") does not define subnodes for the type of PHY, instead it is expected that phandle args are used for setting the type of the PHY. phys = <&usbdp_phy0 PHY_TYPE_USB3> Adopt the usbdp phy driver to work with upstream DT binding targeted for Linux kernel v6.10. Signed-off-by: Jonas Karlman Reviewed-by: Kever Yang

phy: rockchip: usbdp: Drop rockchip_u3phy_uboot_init()

2024-05-07T07:56:10Z

Remove the rockchip_u3phy_uboot_init() function, it has no caller and is not needed with proper driver model use. Signed-off-by: Jonas Karlman Reviewed-by: Kever Yang

phy: rockchip: usbdp: Find phy-id from the io address

2024-05-07T07:56:10Z

The upstream Linux kernel driver find the phy-id from the io address. Change to use a similar method as the U-Boot inno-usb2 phy driver and the Linux kernel driver to set correct phy-id. This is based on the linux-phy next commit 2f70bbddeb45 ("phy: rockchip: add usbdp combo phy driver"). Signed-off-by: Jonas Karlman Reviewed-by: Kever Yang

phy: rockchip-inno-usb2: Add support for RK3308

2024-04-26T07:47:03Z

Add clkout_ctl and phy_sus regs to support USB2PHY for RK3308. Based on linux commit 31f840e7ff3e ("phy: phy-rockchip-inno-usb2: add support for RK3308 USB phy"). Signed-off-by: Jonas Karlman Reviewed-by: Kever Yang

phy: rockchip: Add Rockchip INNO HDMI PHY driver

2024-04-21T07:07:00Z

Add Rockchip INNO HDMI PHY driver for RK3328. Reference from linux-next phy-rockchip-inno-hdmi driver. Signed-off-by: Jagan Teki

phy: rockchip-inno-usb2: Limit changes made to regs

2024-03-14T03:48:40Z

The USB2PHY regs already contain working default reset values for RK3328 and RK35xx as evidenced by the fact that this driver never has changed a single value for these SoCs. Reduce to only configure utmi_suspend_n and utmi_sel bits similar to what is currently done on RK3399. Also add missing clkout_ctl for RK3588. When enabled utmi_suspend_n is changed to normal mode and utmi_sel to use otg/host controller utmi interface to phy. When disabled utmi_suspend_n is changed to suspend mode and utmi_sel to use GRF utmi interface to phy. Signed-off-by: Jonas Karlman

phy: rockchip-inno-usb2: Write to correct GRF

2024-03-14T03:48:40Z

On RK3399 the USB2PHY regs are located in the common GRF, remaining SoCs that is supported by this driver have the USB2PHY regs in a different GRF. When support for RK356x, RK3588 and RK3328 was added this driver was never updated to use correct GRF and have instead incorrectly written to wrong GRF for these SoCs. The default reset values for the USB2PHY have made USB mostly working even when wrong GRF was used, however, following have been observed: scanning bus usb@fd840000 for devices... ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) unable to get device descriptor (error=-1) Fix this by using a regmap from rockchip,usbgrf prop and fall back to getting a regmap for parent udevice instead of always getting the common GRF. Also protect against accidental clear of bit 0 in a reg with offset 0, only bind driver to enabled otg/host-ports and remove unused headers. Fixes: 3da15f0b49a2 ("phy: rockchip-inno-usb2: Add USB2 PHY for rk3568") Fixes: cdf9010f6e17 ("phy: rockchip-inno-usb2: add initial support for rk3588 PHY") Fixes: 9aa93d84038b ("phy: rockchip-inno-usb2: Add USB2 PHY for RK3328") Signed-off-by: Jonas Karlman Reviewed-by: Kever Yang