From: Chris Morgan <macroalpha82@gmail.com>
To: linux-rockchip@lists.infradead.org
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
cristian.ciocaltea@collabora.com,
sebastian.reichel@collabora.com, jernej.skrabec@gmail.com,
jonas@kwiboo.se, Laurent.pinchart@ideasonboard.com,
rfoss@kernel.org, neil.armstrong@linaro.org,
andrzej.hajda@intel.com, conor+dt@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, tzimmermann@suse.de, mripard@kernel.org,
andy.yan@rock-chips.com, heiko@sntech.de,
Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 1/3] dt-bindings: display: rockchip: Add no-hpd for dw-hdmi-qp controller
Date: Thu, 6 Nov 2025 12:09:12 -0600 [thread overview]
Message-ID: <20251106180914.768502-2-macroalpha82@gmail.com> (raw)
In-Reply-To: <20251106180914.768502-1-macroalpha82@gmail.com>
From: Chris Morgan <macromorgan@hotmail.com>
Add an attribute of "no-hpd" for the Rockchip dw-hdmi-qp controller.
This is used to describe implementations where the HPD pin is not
connected or used for other purposes, such as in the RK3588S based
Gameforce Ace which repurposed the GPIO for an additional face
button.
The "no-hpd" option was chosen to be consistent with other devices
which already define this parameter for broken or missing hpd
functionality.
Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
---
.../display/rockchip/rockchip,rk3588-dw-hdmi-qp.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip,rk3588-dw-hdmi-qp.yaml b/Documentation/devicetree/bindings/display/rockchip/rockchip,rk3588-dw-hdmi-qp.yaml
index 96b4b088eebe..07342838cd52 100644
--- a/Documentation/devicetree/bindings/display/rockchip/rockchip,rk3588-dw-hdmi-qp.yaml
+++ b/Documentation/devicetree/bindings/display/rockchip/rockchip,rk3588-dw-hdmi-qp.yaml
@@ -69,6 +69,12 @@ properties:
- const: main
- const: hpd
+ no-hpd:
+ type: boolean
+ description:
+ The HPD pin is not present or used for another purpose, and the EDID
+ must be polled instead to determine if a device is attached.
+
phys:
maxItems: 1
description: The HDMI/eDP PHY
--
2.43.0
next prev parent reply other threads:[~2025-11-06 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 18:09 [PATCH 0/3] Add HDMI for Gameforce Ace Chris Morgan
2025-11-06 18:09 ` Chris Morgan [this message]
2025-11-07 17:26 ` [PATCH 1/3] dt-bindings: display: rockchip: Add no-hpd for dw-hdmi-qp controller Conor Dooley
2025-11-06 18:09 ` [PATCH 2/3] drm/bridge: dw-hdmi-qp: Add support for missing HPD Chris Morgan
2025-11-06 19:40 ` Heiko Stuebner
2025-11-06 23:46 ` Chris Morgan
2025-11-07 10:08 ` Sebastian Reichel
2025-11-06 18:09 ` [PATCH 3/3] arm64: dts: rockchip: Add HDMI to Gameforce Ace Chris Morgan
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=20251106180914.768502-2-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--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;
as well as URLs for NNTP newsgroup(s).