From: neil.armstrong@linaro.org
To: Xiangxu Yin <quic_xiangxuy@quicinc.com>,
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>,
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>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
quic_lliu6@quicinc.com, quic_fangez@quicinc.com
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH 8/8] drm/msm/dp: Support external GPIO HPD with 3rd pinctrl chip
Date: Fri, 29 Nov 2024 14:54:36 +0100 [thread overview]
Message-ID: <2c1ffbc6-0d67-4787-9fbe-03255b377c76@linaro.org> (raw)
In-Reply-To: <20241129-add-displayport-support-for-qcs615-platform-v1-8-09a4338d93ef@quicinc.com>
On 29/11/2024 08:57, Xiangxu Yin wrote:
> Add support for handling HPD (Hot Plug Detect) signals via external
> GPIOs connected through pinctrl chips (e.g., Semtech SX1509Q). This
> involves reinitializing the relevant GPIO and binding an interrupt
> handler to process hot plug events. Since external GPIOs only support
> edge interrupts (rising or falling) rather than state interrupts, the
> GPIO state must be read during the first DP bridge HPD enablement. This
> ensures the current connection state is determined and a hot plug event
> is reported accordingly.
>
> Signed-off-by: Xiangxu Yin <quic_xiangxuy@quicinc.com>
> ---
> drivers/gpu/drm/msm/dp/dp_display.c | 83 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 83 insertions(+)
>
> diff --git a/drivers/gpu/drm/msm/dp/dp_display.c b/drivers/gpu/drm/msm/dp/dp_display.c
> index eb6fb76c68e505fafbec563440e9784f51e1894b..22c288ca61b9b444a7b8d4a574c614bfef9d88be 100644
> --- a/drivers/gpu/drm/msm/dp/dp_display.c
> +++ b/drivers/gpu/drm/msm/dp/dp_display.c
> @@ -13,6 +13,8 @@
> #include <linux/delay.h>
> #include <drm/display/drm_dp_aux_bus.h>
> #include <drm/drm_edid.h>
> +#include <linux/gpio/consumer.h>
> +#include <linux/of_gpio.h>
>
> #include "msm_drv.h"
> #include "msm_kms.h"
> @@ -78,6 +80,10 @@ struct msm_dp_display_private {
>
> unsigned int id;
>
> + bool ext_gpio;
> + int gpio_num;
> + struct work_struct gpio_work;
> +
> /* state variables */
> bool core_initialized;
> bool phy_initialized;
> @@ -1182,6 +1188,42 @@ static irqreturn_t msm_dp_display_irq_handler(int irq, void *dev_id)
> return ret;
> }
>
> +
> +static void msm_dp_gpio_work_handler(struct work_struct *work)
> +{
> + struct msm_dp_display_private *dp = container_of(work,
> + struct msm_dp_display_private, gpio_work);
> + struct gpio_desc *desc;
> + bool hpd;
> +
> + if (dp->ext_gpio) {
> + desc = gpio_to_desc(dp->gpio_num);
> + if (!desc) {
> + pr_err("Failed to get gpio_desc for GPIO %d\n", dp->gpio_num);
> + return;
> + }
> +
> + hpd = gpiod_get_value_cansleep(desc);
> + if (hpd)
> + msm_dp_add_event(dp, EV_HPD_PLUG_INT, 0, 0);
> + else
> + msm_dp_add_event(dp, EV_HPD_UNPLUG_INT, 0, 0);
> + }
> +}
> +
> +static irqreturn_t msm_dp_gpio_isr(int unused, void *data)
> +{
> + struct msm_dp_display_private *dp = data;
> +
> + if (!dp) {
> + DRM_ERROR("NULL data\n");
> + return IRQ_NONE;
> + }
> +
> + schedule_work(&dp->gpio_work);
this msm_dp_gpio_isr is already threaded, would would you also schedule a work ?
> + return IRQ_HANDLED;
> +}
> +
> static int msm_dp_display_request_irq(struct msm_dp_display_private *dp)
> {
> int rc = 0;
> @@ -1193,6 +1235,21 @@ static int msm_dp_display_request_irq(struct msm_dp_display_private *dp)
> return dp->irq;
> }
>
> + if (dp->ext_gpio) {
> + int edge, gpio_irq;
> +
> + gpio_irq = gpio_to_irq(dp->gpio_num);
But as Dmitry reported, the system should use a dp-connected as a next bridge
instead which already supports all this much better:
drivers/gpu/drm/bridge/display-connector.c
Documentation/devicetree/bindings/display/connector/dp-connector.yaml
> + edge = IRQF_TRIGGER_FALLING | IRQF_TRIGGER_RISING;
> +
> + rc = devm_request_threaded_irq(&pdev->dev, gpio_irq, NULL,
> + msm_dp_gpio_isr, edge, "dp_gpio_isr", dp);
> + if (rc < 0) {
> + DRM_ERROR("failed to request ext-gpio IRQ%u: %d\n",
> + gpio_irq, rc);
> + return rc;
> + }
> + }
> +
> rc = devm_request_irq(&pdev->dev, dp->irq, msm_dp_display_irq_handler,
> IRQF_TRIGGER_HIGH|IRQF_NO_AUTOEN,
> "dp_display_isr", dp);
> @@ -1308,10 +1365,32 @@ static int msm_dp_display_probe(struct platform_device *pdev)
> return -EPROBE_DEFER;
> }
>
> + if (of_find_property(pdev->dev.of_node, "dp-hpd-gpio", NULL)) {
> + dp->ext_gpio = true;
> + dp->gpio_num = of_get_named_gpio(pdev->dev.of_node, "dp-hpd-gpio", 0);
> + if (dp->gpio_num < 0) {
> + dev_err(&pdev->dev, "Failed to get gpio:%d\n", dp->gpio_num);
> + return dp->gpio_num;
> + }
> +
> + if (!gpio_is_valid(dp->gpio_num)) {
> + DRM_ERROR("gpio(%d) invalid\n", dp->gpio_num);
> + return -EINVAL;
> + }
> +
> + rc = gpio_request(dp->gpio_num, "dp-hpd-gpio");
> + if (rc) {
> + dev_err(&pdev->dev, "Failed to request gpio:%d\n", dp->gpio_num);
> + return rc;
> + }
> + gpio_direction_input(dp->gpio_num);
> + }
> +
> /* setup event q */
> mutex_init(&dp->event_mutex);
> init_waitqueue_head(&dp->event_q);
> spin_lock_init(&dp->event_lock);
> + INIT_WORK(&dp->gpio_work, msm_dp_gpio_work_handler);
>
> /* Store DP audio handle inside DP display */
> dp->msm_dp_display.msm_dp_audio = dp->audio;
> @@ -1678,6 +1757,10 @@ void msm_dp_bridge_hpd_enable(struct drm_bridge *bridge)
> msm_dp_catalog_hpd_config_intr(dp->catalog, DP_DP_HPD_INT_MASK, true);
>
> msm_dp_display->internal_hpd = true;
> +
> + if (dp->ext_gpio)
> + schedule_work(&dp->gpio_work);
> +
> mutex_unlock(&dp->event_mutex);
> }
>
>
prev parent reply other threads:[~2024-11-29 13:54 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 7:57 [PATCH 0/8] Add DisplayPort support for QCS615 platform Xiangxu Yin
2024-11-29 7:57 ` [PATCH 1/8] dt-bindings: display/msm: Document DP on QCS615 Xiangxu Yin
2024-11-29 8:11 ` Krzysztof Kozlowski
2024-11-29 7:57 ` [PATCH 2/8] dt-bindings: phy: qcom,msm8998-qmp-usb3-phy: Add DP support for QCS615 Xiangxu Yin
2024-11-29 8:14 ` Krzysztof Kozlowski
2024-11-29 7:57 ` [PATCH 3/8] phy: qcom: qmp-usbc: Add DP phy mode support on QCS615 Xiangxu Yin
2024-11-29 8:18 ` Krzysztof Kozlowski
2024-12-02 10:31 ` Xiangxu Yin
2024-12-02 15:48 ` Dmitry Baryshkov
2024-11-29 12:12 ` kernel test robot
2024-11-29 14:33 ` Dmitry Baryshkov
2024-12-05 13:26 ` Xiangxu Yin
2024-12-05 18:31 ` Dmitry Baryshkov
2024-12-10 15:09 ` Dmitry Baryshkov
2024-12-11 0:46 ` Xiangxu Yin
2024-12-11 9:46 ` Dmitry Baryshkov
2024-12-11 12:50 ` Xiangxu Yin
2024-12-11 19:15 ` Dmitry Baryshkov
2024-12-18 12:55 ` Xiangxu Yin
2024-12-19 21:38 ` Dmitry Baryshkov
2024-12-20 0:01 ` Dmitry Baryshkov
2025-03-05 10:20 ` Xiangxu Yin
2025-03-05 21:25 ` Dmitry Baryshkov
2025-03-21 10:17 ` Xiangxu Yin
2025-03-21 12:19 ` Dmitry Baryshkov
2024-11-29 7:57 ` [PATCH 4/8] drm/msm/dp: Add DisplayPort support for QCS615 Xiangxu Yin
2024-11-29 13:54 ` Dmitry Baryshkov
2024-11-29 7:57 ` [PATCH 5/8] drm/msm/dp: Add support for lane mapping configuration Xiangxu Yin
2024-11-29 13:50 ` Dmitry Baryshkov
2024-12-02 8:40 ` Xiangxu Yin
2024-12-02 10:46 ` Dmitry Baryshkov
2024-12-05 11:28 ` Xiangxu Yin
2024-12-05 11:40 ` Dmitry Baryshkov
2024-12-19 10:36 ` Xiangxu Yin
2024-12-19 21:45 ` Dmitry Baryshkov
2025-03-05 10:16 ` Xiangxu Yin
2025-03-05 21:14 ` Dmitry Baryshkov
2025-05-19 8:20 ` Xiangxu Yin
2025-05-19 9:58 ` Dmitry Baryshkov
2024-11-29 7:57 ` [PATCH 6/8] drm/msm/dp: Add maximum width limitation for modes Xiangxu Yin
2024-11-29 13:52 ` Dmitry Baryshkov
2024-12-02 9:05 ` Xiangxu Yin
2024-12-02 9:32 ` Dmitry Baryshkov
2024-12-03 7:41 ` Xiangxu Yin
2024-12-03 13:58 ` Dmitry Baryshkov
2024-12-06 20:13 ` Abhinav Kumar
2024-12-09 1:57 ` Xiangxu Yin
2024-12-09 20:18 ` Abhinav Kumar
2024-11-29 7:57 ` [PATCH 7/8] drm/msm/dp: Retry Link Training 2 with lower pattern Xiangxu Yin
2024-11-29 13:53 ` Dmitry Baryshkov
2024-12-03 8:13 ` Xiangxu Yin
2024-12-03 14:07 ` Dmitry Baryshkov
2025-05-27 20:49 ` Konrad Dybcio
2025-07-09 9:16 ` Xiangxu Yin
2025-07-19 9:43 ` Dmitry Baryshkov
2025-07-21 4:18 ` Xiangxu Yin
2024-11-29 7:57 ` [PATCH 8/8] drm/msm/dp: Support external GPIO HPD with 3rd pinctrl chip Xiangxu Yin
2024-11-29 8:21 ` Krzysztof Kozlowski
2024-11-29 13:45 ` Dmitry Baryshkov
2024-11-29 13:54 ` neil.armstrong [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=2c1ffbc6-0d67-4787-9fbe-03255b377c76@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=airlied@gmail.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_fangez@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_lliu6@quicinc.com \
--cc=quic_xiangxuy@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vkoul@kernel.org \
/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).