From: "Heiko Stübner" <heiko@sntech.de>
To: Jian-Hong Pan <jhp@endlessos.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Robin Murphy <robin.murphy@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux@endlessm.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/rockchip: skip probed failed device
Date: Wed, 23 Sep 2020 13:16:53 +0200 [thread overview]
Message-ID: <4641984.dSft4sXKFs@diego> (raw)
In-Reply-To: <439c4b59-b1e6-88bb-568e-1c2a0feceed4@arm.com>
Am Mittwoch, 23. September 2020, 13:05:26 CEST schrieb Robin Murphy:
> On 2020-09-23 07:59, 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
>
> Wouldn't it make more sense to simply not enable the DisplayPort node in
> the upstream DT, until the type-C phy work has been done to make it
> usable at all?
Or alternatively just disable the cdn-dp Rockchip driver in the kernel config,
which results in it also not getting probed.
> AIUI the "official" Manjaro kernel is carrying a bunch of
> hacks to make type-C work via extcon, but they know that isn't an
> upstreamable solution.
>
> Robin.
>
> > 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.
> >
> > This patch skips the probing failed devices to fix this issue.
> >
> > Link: http://lists.infradead.org/pipermail/linux-rockchip/2020-September/022352.html
> > Signed-off-by: Jian-Hong Pan <jhp@endlessos.org>
> > ---
> > drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > index 0f3eb392fe39..de13588602b4 100644
> > --- a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > +++ b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > @@ -331,6 +331,12 @@ static struct component_match *rockchip_drm_match_add(struct device *dev)
> >
> > if (!d)
> > break;
> > + if (!d->driver) {
> > + DRM_DEV_ERROR(d,
> > + "%s did not probe successfully",
> > + drv->driver.name);
> > + continue;
> > + }
> >
> > device_link_add(dev, d, DL_FLAG_STATELESS);
> > component_match_add(dev, &match, compare_dev, d);
> >
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Jian-Hong Pan <jhp@endlessos.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Robin Murphy <robin.murphy@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux@endlessm.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/rockchip: skip probed failed device
Date: Wed, 23 Sep 2020 13:16:53 +0200 [thread overview]
Message-ID: <4641984.dSft4sXKFs@diego> (raw)
In-Reply-To: <439c4b59-b1e6-88bb-568e-1c2a0feceed4@arm.com>
Am Mittwoch, 23. September 2020, 13:05:26 CEST schrieb Robin Murphy:
> On 2020-09-23 07:59, 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
>
> Wouldn't it make more sense to simply not enable the DisplayPort node in
> the upstream DT, until the type-C phy work has been done to make it
> usable at all?
Or alternatively just disable the cdn-dp Rockchip driver in the kernel config,
which results in it also not getting probed.
> AIUI the "official" Manjaro kernel is carrying a bunch of
> hacks to make type-C work via extcon, but they know that isn't an
> upstreamable solution.
>
> Robin.
>
> > 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.
> >
> > This patch skips the probing failed devices to fix this issue.
> >
> > Link: http://lists.infradead.org/pipermail/linux-rockchip/2020-September/022352.html
> > Signed-off-by: Jian-Hong Pan <jhp@endlessos.org>
> > ---
> > drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > index 0f3eb392fe39..de13588602b4 100644
> > --- a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > +++ b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > @@ -331,6 +331,12 @@ static struct component_match *rockchip_drm_match_add(struct device *dev)
> >
> > if (!d)
> > break;
> > + if (!d->driver) {
> > + DRM_DEV_ERROR(d,
> > + "%s did not probe successfully",
> > + drv->driver.name);
> > + continue;
> > + }
> >
> > device_link_add(dev, d, DL_FLAG_STATELESS);
> > component_match_add(dev, &match, compare_dev, d);
> >
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Jian-Hong Pan <jhp@endlessos.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Robin Murphy <robin.murphy@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux@endlessm.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/rockchip: skip probed failed device
Date: Wed, 23 Sep 2020 13:16:53 +0200 [thread overview]
Message-ID: <4641984.dSft4sXKFs@diego> (raw)
In-Reply-To: <439c4b59-b1e6-88bb-568e-1c2a0feceed4@arm.com>
Am Mittwoch, 23. September 2020, 13:05:26 CEST schrieb Robin Murphy:
> On 2020-09-23 07:59, 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
>
> Wouldn't it make more sense to simply not enable the DisplayPort node in
> the upstream DT, until the type-C phy work has been done to make it
> usable at all?
Or alternatively just disable the cdn-dp Rockchip driver in the kernel config,
which results in it also not getting probed.
> AIUI the "official" Manjaro kernel is carrying a bunch of
> hacks to make type-C work via extcon, but they know that isn't an
> upstreamable solution.
>
> Robin.
>
> > 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.
> >
> > This patch skips the probing failed devices to fix this issue.
> >
> > Link: http://lists.infradead.org/pipermail/linux-rockchip/2020-September/022352.html
> > Signed-off-by: Jian-Hong Pan <jhp@endlessos.org>
> > ---
> > drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > index 0f3eb392fe39..de13588602b4 100644
> > --- a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > +++ b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > @@ -331,6 +331,12 @@ static struct component_match *rockchip_drm_match_add(struct device *dev)
> >
> > if (!d)
> > break;
> > + if (!d->driver) {
> > + DRM_DEV_ERROR(d,
> > + "%s did not probe successfully",
> > + drv->driver.name);
> > + continue;
> > + }
> >
> > device_link_add(dev, d, DL_FLAG_STATELESS);
> > component_match_add(dev, &match, compare_dev, d);
> >
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Jian-Hong Pan <jhp@endlessos.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Robin Murphy <robin.murphy@arm.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, linux@endlessm.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/rockchip: skip probed failed device
Date: Wed, 23 Sep 2020 13:16:53 +0200 [thread overview]
Message-ID: <4641984.dSft4sXKFs@diego> (raw)
In-Reply-To: <439c4b59-b1e6-88bb-568e-1c2a0feceed4@arm.com>
Am Mittwoch, 23. September 2020, 13:05:26 CEST schrieb Robin Murphy:
> On 2020-09-23 07:59, 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
>
> Wouldn't it make more sense to simply not enable the DisplayPort node in
> the upstream DT, until the type-C phy work has been done to make it
> usable at all?
Or alternatively just disable the cdn-dp Rockchip driver in the kernel config,
which results in it also not getting probed.
> AIUI the "official" Manjaro kernel is carrying a bunch of
> hacks to make type-C work via extcon, but they know that isn't an
> upstreamable solution.
>
> Robin.
>
> > 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.
> >
> > This patch skips the probing failed devices to fix this issue.
> >
> > Link: http://lists.infradead.org/pipermail/linux-rockchip/2020-September/022352.html
> > Signed-off-by: Jian-Hong Pan <jhp@endlessos.org>
> > ---
> > drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > index 0f3eb392fe39..de13588602b4 100644
> > --- a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > +++ b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > @@ -331,6 +331,12 @@ static struct component_match *rockchip_drm_match_add(struct device *dev)
> >
> > if (!d)
> > break;
> > + if (!d->driver) {
> > + DRM_DEV_ERROR(d,
> > + "%s did not probe successfully",
> > + drv->driver.name);
> > + continue;
> > + }
> >
> > device_link_add(dev, d, DL_FLAG_STATELESS);
> > component_match_add(dev, &match, compare_dev, d);
> >
>
next prev parent reply other threads:[~2020-09-23 11:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 8:34 [QUESTION] Enable PINEBOOK Pro's display Jian-Hong Pan
2020-09-23 6:59 ` [PATCH] drm/rockchip: skip probed failed device Jian-Hong Pan
2020-09-23 6:59 ` Jian-Hong Pan
2020-09-23 6:59 ` Jian-Hong Pan
2020-09-23 6:59 ` Jian-Hong Pan
2020-09-23 7:38 ` Heiko Stübner
2020-09-23 7:38 ` Heiko Stübner
2020-09-23 7:38 ` Heiko Stübner
2020-09-23 7:38 ` Heiko Stübner
2020-09-23 11:05 ` Robin Murphy
2020-09-23 11:05 ` Robin Murphy
2020-09-23 11:05 ` Robin Murphy
2020-09-23 11:05 ` Robin Murphy
2020-09-23 11:16 ` Heiko Stübner [this message]
2020-09-23 11:16 ` Heiko Stübner
2020-09-23 11:16 ` Heiko Stübner
2020-09-23 11:16 ` Heiko Stübner
2020-09-24 6:07 ` Jian-Hong Pan
2020-09-24 6:07 ` Jian-Hong Pan
2020-09-24 6:07 ` Jian-Hong Pan
2020-09-24 6:07 ` Jian-Hong Pan
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=4641984.dSft4sXKFs@diego \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jhp@endlessos.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@endlessm.com \
--cc=robin.murphy@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.