Hi, On Thu, Sep 24, 2026 at 09:03:00PM +0200, Adam Wermuth wrote: > On Thu, 24 Sep 2026 6:12 PM, Jonas Karlman wrote: > > This and next patch is likely best suited as an dt-overlay. > > Thanks for the review. That makes sense, as the B-key slot is not > always populated. > > For v2 I will move the host1 enablement and the WWAN power, RESET# > and W_DISABLE1# handling into a new rk3568-rock-3b-wwan.dtso overlay, > and keep only the fan patch in the base DT. Why would this be better suited as an Overlay? Nothing describes the specific card plugged in as it is auto-discovered via USB. The overlays are mostly required for things that cannot easily be auto-detected. FWIW we don't have M.2 Key M as a DT overlay either. Something to consider is, that for Key E and Key M there is a proper DT binding now: Documentation/devicetree/bindings/connector/pcie-m2-*.yaml We probably want the same for Key B. Greetings, -- Sebastian > > > czw., 24 wrz 2026 o 18:12 Jonas Karlman napisaƂ(a): > > > > Hi Adam, > > > > On 9/24/2026 9:14 AM, Adam Wermuth wrote: > > > The USB 2.0 data lines of the M.2 B-key slot are routed to USB2_HOST3, > > > which is served by usb_host1_ehci/ohci through the host port of > > > usb2phy1. Enable the controllers and the PHY port so that modules in > > > the B-key slot, such as LTE modems, can enumerate. > > > > This and next patch is likely best suited as an dt-overlay. > > > > Regards, > > Jonas > > > > > > > > Signed-off-by: Adam Wermuth > > > --- > > > arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts | 13 +++++++++++++ > > > 1 file changed, 13 insertions(+) > > > > > > diff --git a/arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts b/arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts > > > index 149a5306bb03..ad9a91c0d0d0 100644 > > > --- a/arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts > > > +++ b/arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts > > > @@ -758,6 +758,14 @@ &usb_host0_xhci { > > > status = "okay"; > > > }; > > > > > > +&usb_host1_ehci { > > > + status = "okay"; > > > +}; > > > + > > > +&usb_host1_ohci { > > > + status = "okay"; > > > +}; > > > + > > > &usb_host1_xhci { > > > status = "okay"; > > > }; > > > @@ -780,6 +788,11 @@ &usb2phy1 { > > > status = "okay"; > > > }; > > > > > > +&usb2phy1_host { > > > + phy-supply = <&vcc5v0_usb_host>; > > > + status = "okay"; > > > +}; > > > + > > > &usb2phy1_otg { > > > phy-supply = <&vcc5v0_usb_host>; > > > status = "okay"; > > >