From: Lyude Paul <lyude@redhat.com>
To: Karol Herbst <kherbst@redhat.com>
Cc: nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Ben Skeggs <bskeggs@redhat.com>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, Dave Airlie <airlied@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/nouveau/nvkm/dp: Add hack to fix DP 1.3+ DPCD issues
Date: Thu, 27 Jul 2023 17:57:33 -0400 [thread overview]
Message-ID: <badef3d33469d97b01a42da520ad22ae4c9485fe.camel@redhat.com> (raw)
In-Reply-To: <CACO55tvfTDu8XcKowWXcSRqp8OMLb8Q4jnPG_Fn5y=yJy-Dqbw@mail.gmail.com>
On Sun, 2023-07-09 at 01:42 +0200, Karol Herbst wrote:
> On Fri, Jul 7, 2023 at 11:58 PM Lyude Paul <lyude@redhat.com> wrote:
> >
> > Currently we use the drm_dp_dpcd_read_caps() helper in the DRM side of
> > nouveau in order to read the DPCD of a DP connector, which makes sure we do
> > the right thing and also check for extended DPCD caps. However, it turns
> > out we're not currently doing this on the nvkm side since we don't have
> > access to the drm_dp_aux structure there - which means that the DRM side of
> > the driver and the NVKM side can end up with different DPCD capabilities
> > for the same connector.
> >
> > Ideally to fix this, we want to start setting up the drm_dp_aux device in
> > NVKM before we've made contact with the DRM side - which should be pretty
> > easy to accomplish (I'm already working on it!). Until then however, let's
> > workaround this problem by porting a copy of drm_dp_read_dpcd_caps() into
> > NVKM - which should fix this issue.
> >
> > Issue: https://gitlab.freedesktop.org/drm/nouveau/-/issues/211
>
> Should a Fixes: or Cc: stable tag be added so it gets backported?
JFYI I think not adding one is fine nowadays? The stable bot seems to be
pretty good at catching anything with the words fix/fixes in it
>
> > Signed-off-by: Lyude Paul <lyude@redhat.com>
> > ---
> > drivers/gpu/drm/nouveau/nvkm/engine/disp/dp.c | 48 ++++++++++++++++++-
> > 1 file changed, 47 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/disp/dp.c b/drivers/gpu/drm/nouveau/nvkm/engine/disp/dp.c
> > index 40c8ea43c42f..b8ac66b4a2c4 100644
> > --- a/drivers/gpu/drm/nouveau/nvkm/engine/disp/dp.c
> > +++ b/drivers/gpu/drm/nouveau/nvkm/engine/disp/dp.c
> > @@ -26,6 +26,8 @@
> > #include "head.h"
> > #include "ior.h"
> >
> > +#include <drm/display/drm_dp.h>
> > +
> > #include <subdev/bios.h>
> > #include <subdev/bios/init.h>
> > #include <subdev/gpio.h>
> > @@ -634,6 +636,50 @@ nvkm_dp_enable_supported_link_rates(struct nvkm_outp *outp)
> > return outp->dp.rates != 0;
> > }
> >
> > +/* XXX: This is a big fat hack, and this is just drm_dp_read_dpcd_caps()
>
> Well.. maybe we should rephrase that _if_ we want to see it
> backported. But is this code really that bad? It kinda looks
> reasonable enough.
>
> > + * converted to work inside nvkm. This is a temporary holdover until we start
> > + * passing the drm_dp_aux device through NVKM
> > + */
> > +static int
> > +nvkm_dp_read_dpcd_caps(struct nvkm_outp *outp)
> > +{
> > + struct nvkm_i2c_aux *aux = outp->dp.aux;
> > + u8 dpcd_ext[DP_RECEIVER_CAP_SIZE];
> > + int ret;
> > +
> > + ret = nvkm_rdaux(aux, DPCD_RC00_DPCD_REV, outp->dp.dpcd, DP_RECEIVER_CAP_SIZE);
> > + if (ret < 0)
> > + return ret;
> > +
> > + /*
> > + * Prior to DP1.3 the bit represented by
> > + * DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT was reserved.
> > + * If it is set DP_DPCD_REV at 0000h could be at a value less than
> > + * the true capability of the panel. The only way to check is to
> > + * then compare 0000h and 2200h.
> > + */
> > + if (!(outp->dp.dpcd[DP_TRAINING_AUX_RD_INTERVAL] &
> > + DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT))
> > + return 0;
> > +
> > + ret = nvkm_rdaux(aux, DP_DP13_DPCD_REV, dpcd_ext, sizeof(dpcd_ext));
> > + if (ret < 0)
> > + return ret;
> > +
> > + if (outp->dp.dpcd[DP_DPCD_REV] > dpcd_ext[DP_DPCD_REV]) {
> > + OUTP_DBG(outp, "Extended DPCD rev less than base DPCD rev (%d > %d)\n",
> > + outp->dp.dpcd[DP_DPCD_REV], dpcd_ext[DP_DPCD_REV]);
> > + return 0;
> > + }
> > +
> > + if (!memcmp(outp->dp.dpcd, dpcd_ext, sizeof(dpcd_ext)))
> > + return 0;
> > +
> > + memcpy(outp->dp.dpcd, dpcd_ext, sizeof(dpcd_ext));
> > +
> > + return 0;
> > +}
> > +
> > void
> > nvkm_dp_enable(struct nvkm_outp *outp, bool auxpwr)
> > {
> > @@ -689,7 +735,7 @@ nvkm_dp_enable(struct nvkm_outp *outp, bool auxpwr)
> > memset(outp->dp.lttpr, 0x00, sizeof(outp->dp.lttpr));
> > }
> >
> > - if (!nvkm_rdaux(aux, DPCD_RC00_DPCD_REV, outp->dp.dpcd, sizeof(outp->dp.dpcd))) {
> > + if (!nvkm_dp_read_dpcd_caps(outp)) {
> > const u8 rates[] = { 0x1e, 0x14, 0x0a, 0x06, 0 };
> > const u8 *rate;
> > int rate_max;
> > --
> > 2.40.1
> >
>
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
next prev parent reply other threads:[~2023-07-27 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 21:58 Lyude Paul
2023-07-08 23:42 ` Karol Herbst
2023-07-27 21:57 ` Lyude Paul [this message]
2023-07-27 23:11 ` Karol Herbst
2023-07-28 9:59 ` Karol Herbst
2023-07-19 5:17 ` Ben Skeggs
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=badef3d33469d97b01a42da520ad22ae4c9485fe.camel@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=bskeggs@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
/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
all inboxes | Powered by JetHome®