From: Prahlad Valluru <venkata.valluru@oss.qualcomm.com>
To: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Prahlad Valluru <venkata.valluru@oss.qualcomm.com>
Subject: [PATCH 2/2] drm: bridge: add enable gpio for display-connector
Date: Tue, 28 Oct 2025 20:56:50 +0530 [thread overview]
Message-ID: <20251028-enable-gpio-dp-connector-v1-2-2babdf1d2289@oss.qualcomm.com> (raw)
In-Reply-To: <20251028-enable-gpio-dp-connector-v1-0-2babdf1d2289@oss.qualcomm.com>
In some cases, need gpio to be set for the connector
enable. Add optional enable gpio to display-connector.
Signed-off-by: Prahlad Valluru <venkata.valluru@oss.qualcomm.com>
---
drivers/gpu/drm/bridge/display-connector.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpu/drm/bridge/display-connector.c b/drivers/gpu/drm/bridge/display-connector.c
index e9f16dbc9535..52f5e4175e64 100644
--- a/drivers/gpu/drm/bridge/display-connector.c
+++ b/drivers/gpu/drm/bridge/display-connector.c
@@ -21,6 +21,7 @@ struct display_connector {
struct drm_bridge bridge;
struct gpio_desc *hpd_gpio;
+ struct gpio_desc *enable_gpio;
int hpd_irq;
struct regulator *supply;
@@ -298,6 +299,12 @@ static int display_connector_probe(struct platform_device *pdev)
"Unable to retrieve HPD GPIO\n");
conn->hpd_irq = gpiod_to_irq(conn->hpd_gpio);
+
+ conn->enable_gpio = devm_gpiod_get_optional(&pdev->dev, "enable",
+ GPIOD_OUT_HIGH);
+ if (IS_ERR(conn->enable_gpio))
+ return dev_err_probe(&pdev->dev, PTR_ERR(conn->enable_gpio),
+ "Unable to retrieve enable GPIO\n");
} else {
conn->hpd_irq = -EINVAL;
}
--
2.34.1
next prev parent reply other threads:[~2025-10-28 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 15:26 [PATCH 0/2] Add enable gpio to display connector Prahlad Valluru
2025-10-28 15:26 ` [PATCH 1/2] dt-bindings: dp-connector: describe enable gpio Prahlad Valluru
2025-10-28 15:55 ` Krzysztof Kozlowski
2025-10-28 15:26 ` Prahlad Valluru [this message]
2025-10-28 15:49 ` [PATCH 2/2] drm: bridge: add enable gpio for display-connector Laurent Pinchart
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=20251028-enable-gpio-dp-connector-v1-2-2babdf1d2289@oss.qualcomm.com \
--to=venkata.valluru@oss.qualcomm.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=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--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=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ti.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).