[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YXXNsdVTo8pVfs4/@think.localdomain>
Date: Sun, 24 Oct 2021 17:18:41 -0400
From: Siva Mahadevan <me@...hdvn.name>
To: Jian-Hong Pan <jhp@...lessos.org>,
Rob Herring <robh+dt@...nel.org>,
Heiko Stuebner <heiko@...ech.de>, Soeren Moch <smoch@....de>,
Tobias Schramm <t.schramm@...jaro.org>,
Johan Jonker <jbx6244@...il.com>,
Katsuhiro Suzuki <katsuhiro@...suster.net>,
Hugh Cole-Baker <sigmaris@...il.com>,
Robin Murphy <robin.murphy@....com>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux@...lessm.com
Subject: Re: [PATCH] arm64: dts: rockchip: disable USB type-c DisplayPort
Jian-Hong Pan wrote:
> The cdn-dp sub driver probes the device failed on PINEBOOK Pro.
>
> kernel: cdn-dp fec00000.dp: [drm:cdn_dp_probe [rockchipdrm]] *ERROR* missing extcon or phy
> kernel: cdn-dp: probe of fec00000.dp failed with error -22
>
> Then, the device halts all of the DRM related device jobs. For example,
> the operations: vop_component_ops, vop_component_ops and
> rockchip_dp_component_ops cannot be bound to corresponding devices. So,
> Xorg cannot find the correct DRM device.
>
> The USB type-C DisplayPort does not work for now. So, disable the
> DisplayPort node until the type-C phy work has been done.
>
> Link: https://patchwork.kernel.org/patch/11794141/#23639877
> Signed-off-by: Jian-Hong Pan <jhp@...lessos.org>
> ---
> arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts b/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts
> index 06d48338c836..d624c595c533 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts
> @@ -380,7 +380,7 @@ mains_charger: dc-charger {
> };
>
> &cdn_dp {
> - status = "okay";
> + status = "disabled";
> };
>
> &cpu_b0 {
> --
> 2.28.0
I saw a similar patch posted at https://lkml.org/lkml/2021/7/15/752. I
was wondering if one of these patches will be submitted to mainline, or
what the status on this patch is. I can confirm that this does solve
the issue on my Pinebook Pro. Will this go forward?
Powered by blists - more mailing lists