From: Imre Deak <imre.deak@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Abel Vesa <abel.vesa@linaro.org>,
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>,
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>,
Johan Hovold <johan@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 RFC 1/4] drm/dp: Add helper to set LTTPRs in transparent mode
Date: Fri, 1 Nov 2024 15:43:40 +0200 [thread overview]
Message-ID: <ZyTbDELVW5vqFoMS@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <87msijjol6.fsf@intel.com>
On Fri, Nov 01, 2024 at 11:22:13AM +0200, Jani Nikula wrote:
> On Thu, 31 Oct 2024, Imre Deak <imre.deak@intel.com> wrote:
> > On Thu, Oct 31, 2024 at 05:12:45PM +0200, Abel Vesa wrote:
> >> According to the DisplayPort standard, LTTPRs have two operating
> >> modes:
> >> - non-transparent - it replies to DPCD LTTPR field specific AUX
> >> requests, while passes through all other AUX requests
> >> - transparent - it passes through all AUX requests.
> >>
> >> Switching between this two modes is done by the DPTX by issuing
> >> an AUX write to the DPCD PHY_REPEATER_MODE register.
> >>
> >> Add a generic helper that allows switching between these modes.
> >>
> >> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> >> ---
> >> drivers/gpu/drm/display/drm_dp_helper.c | 17 +++++++++++++++++
> >> include/drm/display/drm_dp_helper.h | 1 +
> >> 2 files changed, 18 insertions(+)
> >>
> >> diff --git a/drivers/gpu/drm/display/drm_dp_helper.c b/drivers/gpu/drm/display/drm_dp_helper.c
> >> index 6ee51003de3ce616c3a52653c2f1979ad7658e21..38d612345986ad54b42228902ea718a089d169c4 100644
> >> --- a/drivers/gpu/drm/display/drm_dp_helper.c
> >> +++ b/drivers/gpu/drm/display/drm_dp_helper.c
> >> @@ -2694,6 +2694,23 @@ int drm_dp_lttpr_max_link_rate(const u8 caps[DP_LTTPR_COMMON_CAP_SIZE])
> >> }
> >> EXPORT_SYMBOL(drm_dp_lttpr_max_link_rate);
> >>
> >> +/**
> >> + * 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.
> >
> > Should be "Returns 1 on success".
>
> But is that a sensible return value?
It matches what the function returns, but yes, would make more sense to
fix the return value instead to be 0 in case of success.
> >
> >> + */
> >> +
>
> Superfluous newline.
>
> >> +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;
> >> +
> >> + return drm_dp_dpcd_writeb(aux, DP_PHY_REPEATER_MODE, val);
> >> +}
> >> +EXPORT_SYMBOL(drm_dp_lttpr_set_transparent_mode);
> >> +
> >> /**
> >> * drm_dp_lttpr_max_lane_count - get the maximum lane count supported by all LTTPRs
> >> * @caps: LTTPR common capabilities
> >> diff --git a/include/drm/display/drm_dp_helper.h b/include/drm/display/drm_dp_helper.h
> >> index 279624833ea9259809428162f4e845654359f8c9..8821ab2d36b0e04d38ccbdddcb703b34de7ed680 100644
> >> --- a/include/drm/display/drm_dp_helper.h
> >> +++ b/include/drm/display/drm_dp_helper.h
> >> @@ -625,6 +625,7 @@ int drm_dp_read_lttpr_phy_caps(struct drm_dp_aux *aux,
> >> u8 caps[DP_LTTPR_PHY_CAP_SIZE]);
> >> int drm_dp_lttpr_count(const u8 cap[DP_LTTPR_COMMON_CAP_SIZE]);
> >> int drm_dp_lttpr_max_link_rate(const u8 caps[DP_LTTPR_COMMON_CAP_SIZE]);
> >> +int drm_dp_lttpr_set_transparent_mode(struct drm_dp_aux *aux, bool enable);
> >> int drm_dp_lttpr_max_lane_count(const u8 caps[DP_LTTPR_COMMON_CAP_SIZE]);
> >> bool drm_dp_lttpr_voltage_swing_level_3_supported(const u8 caps[DP_LTTPR_PHY_CAP_SIZE]);
> >> bool drm_dp_lttpr_pre_emphasis_level_3_supported(const u8 caps[DP_LTTPR_PHY_CAP_SIZE]);
> >>
> >> --
> >> 2.34.1
> >>
>
> --
> Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-01 13:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 15:12 [PATCH RFC 0/4] drm/dp: Rework LTTPR transparent mode handling and add support to msm driver Abel Vesa
2024-10-31 15:12 ` [PATCH RFC 1/4] drm/dp: Add helper to set LTTPRs in transparent mode Abel Vesa
2024-10-31 21:05 ` Imre Deak
2024-11-01 9:22 ` Jani Nikula
2024-11-01 13:43 ` Imre Deak [this message]
2024-11-01 20:12 ` Dmitry Baryshkov
2024-10-31 15:12 ` [PATCH RFC 2/4] drm/nouveau/dp: Use the generic helper to control LTTPR " Abel Vesa
2024-10-31 16:44 ` Dmitry Baryshkov
2024-12-11 9:08 ` Abel Vesa
2024-10-31 15:12 ` [PATCH RFC 3/4] drm/i915/dp: " Abel Vesa
2024-10-31 21:08 ` Imre Deak
2024-10-31 15:12 ` [PATCH RFC 4/4] drm/msm/dp: Add support for LTTPR handling Abel Vesa
2024-10-31 16:54 ` Dmitry Baryshkov
2024-12-11 9:08 ` Abel Vesa
2024-12-11 9:55 ` Dmitry Baryshkov
2024-12-11 10:52 ` Abel Vesa
2024-11-01 10:56 ` ✓ CI.Patch_applied: success for drm/dp: Rework LTTPR transparent mode handling and add support to msm driver Patchwork
2024-11-01 10:56 ` ✓ CI.checkpatch: " Patchwork
2024-11-01 10:57 ` ✓ CI.KUnit: " Patchwork
2024-11-01 11:09 ` ✓ CI.Build: " Patchwork
2024-11-01 11:11 ` ✓ CI.Hooks: " Patchwork
2024-11-01 11:13 ` ✗ CI.checksparse: warning " Patchwork
2024-11-01 11:36 ` ✓ CI.BAT: success " Patchwork
2024-11-01 12:46 ` ✗ CI.FULL: failure " Patchwork
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=ZyTbDELVW5vqFoMS@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=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