From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Yashas D <y-d@ti.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, andrzej.hajda@intel.com,
neil.armstrong@linaro.org, rfoss@kernel.org,
Laurent.pinchart@ideasonboard.com, jonas@kwiboo.se,
jernej.skrabec@gmail.com, luca.ceresoli@bootlin.com,
airlied@gmail.com, simona@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, h-shenoy@ti.com, panchuang@vivo.com,
kees@kernel.org, r-ravikumar@ti.com, sjakhade@cadence.com,
yamonkar@cadence.com
Subject: Re: [PATCH v7 0/2] Add no-hpd property to the cadence bridge
Date: Mon, 16 Nov 2026 11:07:09 +0200 [thread overview]
Message-ID: <692d174e-eea4-4b5d-97f8-384de96e4eb4@ideasonboard.com> (raw)
In-Reply-To: <20261009064024.985688-1-y-d@ti.com>
Hi,
On 09/10/2026 09:40, Yashas D wrote:
> This series adds 'no-hpd' device tree property support to the Cadence
> MHDP8546 bridge driver for boards where the HPD line cannot be used for
> hotplug detection.
>
> On TI J721S2 EVMs, the DP0 HPD resistor is DNI from factory, so the HPD
> signal is not physically connected to SoC pin AA24 by default. AA24 must
> still be in DP0_HPD mux mode for the MHDP firmware to operate.
>
> When 'no-hpd' is set, DRM_BRIDGE_OP_HPD is omitted and the framework
> falls back to polling .detect() every ~10 seconds. Presence is detected
> by reading DP_DPCD_REV (0x000) over AUX, with an early exit when the
> monitor is stably connected to avoid re-programming the stream each poll.
How did you test this? I can't get a picture on J721E EVM if I apply this.
Tomi
> Changes since v6:
> - Reverted back to dev_dbg instead of dev_err for the normal hpd case.
> - Picked up Acked-by from Krzysztof Kozlowski from v6 on the bindings patch.
>
> Link to v6: https://lore.kernel.org/all/20260802153825.1570435-1-y-d@ti.com/
>
> Rahul T R (2):
> dt-bindings: display: bridge: cdns,mhdp8546: Add no-hpd property to
> the cadence bridge
> drm: bridge: cdns-mhdp8546: Add no-hpd property
>
> .../display/bridge/cdns,mhdp8546.yaml | 11 +++
> .../drm/bridge/cadence/cdns-mhdp8546-core.c | 69 +++++++++++++++++--
> .../drm/bridge/cadence/cdns-mhdp8546-core.h | 1 +
> 3 files changed, 75 insertions(+), 6 deletions(-)
>
prev parent reply other threads:[~2026-11-16 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 6:40 Yashas D
2026-10-09 6:40 ` [PATCH v7 1/2] dt-bindings: display: bridge: cdns,mhdp8546: " Yashas D
2026-10-09 6:40 ` [PATCH v7 2/2] drm: bridge: cdns-mhdp8546: Add no-hpd property Yashas D
2026-11-16 9:07 ` Tomi Valkeinen [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=692d174e-eea4-4b5d-97f8-384de96e4eb4@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=h-shenoy@ti.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=panchuang@vivo.com \
--cc=r-ravikumar@ti.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=sjakhade@cadence.com \
--cc=tzimmermann@suse.de \
--cc=y-d@ti.com \
--cc=yamonkar@cadence.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 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®