From: Mike Looijmans <mike.looijmans@topic.nl>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
David Airlie <airlied@gmail.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>, Simona Vetter <simona@ffwll.ch>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] drm: bridge: Add TI tmds181 and sn65dp159 driver
Date: Mon, 13 Oct 2025 16:32:35 +0200 [thread overview]
Message-ID: <13cbad78-26bd-4dd2-98f0-34bdd409203f@topic.nl> (raw)
In-Reply-To: <y6idr5f7cqtkls3oqnzaoc5u5zvrqns3xdl2ijyxegxvqgph7r@6hkc5zc6urql>
On 9/25/25 05:51, Dmitry Baryshkov wrote:
> On Mon, Sep 22, 2025 at 02:18:45PM +0200, Mike Looijmans wrote:
>> The tmds181 and sn65dp159 are "retimers" and hence can be considered
>> HDMI-to-HDMI bridges. Typical usage is to convert the output of an
>> FPGA into a valid HDMI signal, and it will typically be inserted
>> between an encoder and hdmi-connector.
>>
>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>> ---
>>
>> Changes in v6:
>> Add DRM_DISPLAY_HDMI_HELPER to Kconfig
>> Change "ti,mode" to "ti,retimer-mode"
>>
>> Changes in v5:
>> Really added vcc/vdd regulator support
>> "oe" gpio is now "reset" (reversed logic)
>> devicetree enums ti,equalizer and ti,mode
>> Always disable HDMI_SEL (formerly "dvi-mode")
>>
>> Changes in v4:
>> dev_err_probe, this_module, of_match_ptr
>> Use fallback compatible
>> Add vcc-supply and vdd-supply
>>
>> Changes in v3:
>> Lower-case hex values and use defines for EYESCAN registers
>> Remove equalizer code (unlikely to be used)
>> Remove attributes (no longer useful, undocumented)
>> Fix build for 6.17 kernel
>> Use devm_drm_bridge_alloc
>> Sort includes and add linux/bitfield.h
>> Check chip type and complain on mismatch
>>
>> Changes in v2:
>> Use atomic_enable/disable
>> Use #defines for bit fields in registers
>> Allow HDMI 2 compliance
>> Filter modes on clock range
>> Use cross-over pixel frequency instead of manual overides
>> Devicetree bindings according to standards
>>
>> drivers/gpu/drm/bridge/Kconfig | 12 +
>> drivers/gpu/drm/bridge/Makefile | 1 +
>> drivers/gpu/drm/bridge/ti-tmds181.c | 427 ++++++++++++++++++++++++++++
>> 3 files changed, 440 insertions(+)
>> create mode 100644 drivers/gpu/drm/bridge/ti-tmds181.c
>>
>> diff --git a/drivers/gpu/drm/bridge/Kconfig b/drivers/gpu/drm/bridge/Kconfig
>> index b9e0ca85226a..d679180b05b1 100644
>> --- a/drivers/gpu/drm/bridge/Kconfig
>> +++ b/drivers/gpu/drm/bridge/Kconfig
>> @@ -430,6 +430,18 @@ config DRM_TI_SN65DSI86
>> help
>> Texas Instruments SN65DSI86 DSI to eDP Bridge driver
>>
>> +config DRM_TI_TMDS181
>> + tristate "TI TMDS181 and SN65DP159 HDMI retimer bridge driver"
>> + depends on OF
>> + select DRM_KMS_HELPER
> Do you need it here?
Yes, compiling a kernel without it results in:
ld: drivers/gpu/drm/bridge/ti-tmds181.o:(.rodata+0x2f8): undefined
reference to `drm_atomic_helper_bridge_duplicate_state'
ld: drivers/gpu/drm/bridge/ti-tmds181.o:(.rodata+0x2fc): undefined
reference to `drm_atomic_helper_bridge_destroy_state'
ld: drivers/gpu/drm/bridge/ti-tmds181.o:(.rodata+0x30c): undefined
reference to `drm_atomic_helper_bridge_reset'
>
>> + select DRM_DISPLAY_HDMI_HELPER
> missing select DRM_DISPLAY_HELPER
Will add in v7
>
>> + select REGMAP_I2C
>> + help
>> + Enable this to support the TI TMDS181 and SN65DP159 HDMI retimers.
>> + The SN65DP159 provides output into a cable (source) whereas the
>> + TMDS181 is meant to forward a cable signal into a PCB (sink). Either
>> + can be set up as source or sink though.
>> +
>> config DRM_TI_TPD12S015
>> tristate "TI TPD12S015 HDMI level shifter and ESD protection"
>> depends on OF
--
Mike Looijmans
prev parent reply other threads:[~2025-10-13 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.28f0984e-19d0-491e-b8f0-87290b72fea5@emailsignatures365.codetwo.com>
2025-09-22 12:18 ` [PATCH v6 0/2] " Mike Looijmans
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.0c2f242e-bdcc-4862-a215-2a988591f8cc@emailsignatures365.codetwo.com>
2025-09-22 12:18 ` [PATCH v6 1/2] dt-bindings: drm/bridge: ti-tmds181: Add TI TMDS181 and SN65DP159 bindings Mike Looijmans
2025-09-24 17:38 ` Rob Herring (Arm)
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.3ef2b90a-ff78-413f-b853-99ebea0afc4a@emailsignatures365.codetwo.com>
2025-09-22 12:18 ` [PATCH v6 2/2] drm: bridge: Add TI tmds181 and sn65dp159 driver Mike Looijmans
2025-09-25 3:51 ` Dmitry Baryshkov
2025-10-13 14:32 ` Mike Looijmans [this message]
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=13cbad78-26bd-4dd2-98f0-34bdd409203f@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--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
all inboxes | Powered by JetHome®