From: Abel Vesa <abel.vesa@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Karol Herbst <kherbst@redhat.com>, Lyude Paul <lyude@redhat.com>,
Danilo Krummrich <dakr@redhat.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
nouveau@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org
Subject: Re: [PATCH v2 1/4] drm/dp: Add helper to set LTTPRs in transparent mode
Date: Thu, 26 Dec 2024 15:07:27 +0200 [thread overview]
Message-ID: <Z21VD82XCOVgVJUh@linaro.org> (raw)
In-Reply-To: <Z1mk08SHEd5_vc99@hovoldconsulting.com>
On 24-12-11 15:42:27, Johan Hovold wrote:
> On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote:
>
> > +/**
> > + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode
> > + * @aux: DisplayPort AUX channel
> > + * @enable: Enable or disable transparent mode
> > + *
> > + * Returns 0 on success or a negative error code on failure.
> > + */
> > +int drm_dp_lttpr_set_transparent_mode(struct drm_dp_aux *aux, bool enable)
> > +{
> > + u8 val = enable ? DP_PHY_REPEATER_MODE_TRANSPARENT :
> > + DP_PHY_REPEATER_MODE_NON_TRANSPARENT;
> > + int ret = drm_dp_dpcd_writeb(aux, DP_PHY_REPEATER_MODE, val);
> > +
> > + return ret == 1 ? 0 : ret;
>
> This looks correct, but I had to go look at drm_dp_dpcd_writeb() to make
> sure it never returns 0 (for short transfers).
Will follow Dmitry's proposal here.
if (ret < 0)
return ret;
return (ret == 1) ? 0 : -EIO;
>
> > +}
> > +EXPORT_SYMBOL(drm_dp_lttpr_set_transparent_mode);
>
> This appears to be what the driver currently uses, but why not
> EXPORT_SYMBOL_GPL?
>
> > +
> > +/**
> > + * drm_dp_lttpr_init - init LTTPR transparency mode according to DP standard
> > + *
> > + * @aux: DisplayPort AUX channel
> > + * @lttpr_count: Number of LTTPRs
> > + *
> > + * Returns 0 on success or a negative error code on failure.
> > + */
> > +int drm_dp_lttpr_init(struct drm_dp_aux *aux, int lttpr_count)
> > +{
> > + if (!lttpr_count)
> > + return 0;
> > +
> > + /*
> > + * See DP Standard v2.0 3.6.6.1 about the explicit disabling of
> > + * non-transparent mode and the disable->enable non-transparent mode
> > + * sequence.
> > + */
> > + drm_dp_lttpr_set_transparent_mode(aux, true);
>
> Error handling?
Yes, this makes sense. But other than throwing an error I don't think
there is much to be done. I'll add an drm_err here just in case.
>
> > +
> > + if (lttpr_count > 0 && !drm_dp_lttpr_set_transparent_mode(aux, false))
>
> No need to check lttpr_count again here.
So the logic behind lttpr_count and this transparency mode changing, as
specified in the DP standard, is as follows:
- If there are 0 LTTPRs counted, then nothing to be done, otherwise set to
transparent mode.
- Then, if there are between 0 and 8 LTTPRs counted, set non-transparent
mode successfully.
- Otherwise, rollback to transparent mode.
This last rollback might result in two transparent mode settings without
a non-transparent one in between, but AFAIU, that is OK. Making sure this
doesn't happen would just make the implementation more ugly without any
benefit, IMO.
>
> > + return 0;
>
> I'd check for errors instead of success here and do the rollback before
> returning -EINVAL.
>
Yes, I think it would be more cleaner. Will do that.
> > +
> > + /*
> > + * Roll-back to tranparent mode if setting non-tranparent mode failed or
> > + * the number of LTTPRs is invalid
> > + */
> > + drm_dp_lttpr_set_transparent_mode(aux, true);
> > +
> > + return -EINVAL;
>
> And return 0 explicitly here.
Yes. Will do that.
>
> > +}
> > +EXPORT_SYMBOL(drm_dp_lttpr_init);
>
> In any case this works well and is needed for external display on the
> Lenovo ThinkPad T14s, while not breaking the X13s which does not need
> it:
>
> Tested-by: Johan Hovold <johan+linaro@kernel.org>
>
> Johan
Thanks for reviewing and testing!
Abel
next prev parent reply other threads:[~2024-12-26 13:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 13:04 [PATCH v2 0/4] drm/dp: Rework LTTPR transparent mode handling and add support to msm driver Abel Vesa
2024-12-11 13:04 ` [PATCH v2 1/4] drm/dp: Add helper to set LTTPRs in transparent mode Abel Vesa
2024-12-11 14:42 ` Johan Hovold
2024-12-11 18:32 ` Dmitry Baryshkov
2024-12-12 8:18 ` Jani Nikula
2024-12-11 19:00 ` Dmitry Baryshkov
2024-12-12 8:31 ` neil.armstrong
2024-12-12 8:41 ` Johan Hovold
2024-12-26 13:07 ` Abel Vesa [this message]
2024-12-30 13:18 ` Jani Nikula
2024-12-30 13:44 ` Dmitry Baryshkov
2024-12-30 17:00 ` Jani Nikula
2024-12-11 19:22 ` Dmitry Baryshkov
2024-12-26 12:09 ` Abel Vesa
2024-12-26 19:04 ` Dmitry Baryshkov
2024-12-11 13:04 ` [PATCH v2 2/4] drm/nouveau/dp: Use the generic helper to control LTTPR " Abel Vesa
2024-12-16 20:36 ` Lyude Paul
2024-12-11 13:04 ` [PATCH v2 3/4] drm/i915/dp: " Abel Vesa
2024-12-11 13:04 ` [PATCH v2 4/4] drm/msm/dp: Add support for LTTPR handling Abel Vesa
2024-12-11 14:56 ` Johan Hovold
2024-12-26 12:46 ` Abel Vesa
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=Z21VD82XCOVgVJUh@linaro.org \
--to=abel.vesa@linaro.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=dakr@redhat.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=johan@kernel.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kherbst@redhat.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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