From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Chaoyi Chen <kernel@airkyi.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Sandy Huang <hjc@rock-chips.com>,
Andy Yan <andy.yan@rock-chips.com>,
Yubing Zhang <yubing.zhang@rock-chips.com>,
Frank Wang <frank.wang@rock-chips.com>,
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>,
Amit Sunil Dhamne <amitsd@google.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dragan Simic <dsimic@manjaro.org>,
Johan Jonker <jbx6244@gmail.com>,
Diederik de Haas <didi.debian@cknow.org>,
Peter Robinson <pbrobinson@gmail.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4 1/7] usb: typec: Add default HPD device when register DisplayPort altmode
Date: Tue, 23 Sep 2025 09:34:39 +0800 [thread overview]
Message-ID: <e9cf0aa8-ed32-4ffb-a755-150742455808@rock-chips.com> (raw)
In-Reply-To: <mygbqhiom6pkwsadzz2bqf5bth3ogsbd6iku5a7r5swxrakein@fjhz7udnkcks>
On 9/23/2025 9:10 AM, Dmitry Baryshkov wrote:
> On Mon, Sep 22, 2025 at 09:20:33AM +0800, Chaoyi Chen wrote:
>> From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
>>
>> Add default DRM AUX HPD bridge device when register DisplayPort
>> altmode. That makes it redundant for each Type-C driver to implement
>> a similar registration process in embedded scenarios.
>>
>> Signed-off-by: Chaoyi Chen <chaoyi.chen@rock-chips.com>
>> ---
>> drivers/usb/typec/altmodes/displayport.c | 27 ++++++++++++++++++++++++
>> drivers/usb/typec/altmodes/displayport.h | 2 ++
>> drivers/usb/typec/class.c | 8 +++++++
>> include/linux/usb/typec_altmode.h | 2 ++
>> 4 files changed, 39 insertions(+)
>>
>> diff --git a/drivers/usb/typec/altmodes/displayport.c b/drivers/usb/typec/altmodes/displayport.c
>> index 1dcb77faf85d..e026dc6e5430 100644
>> --- a/drivers/usb/typec/altmodes/displayport.c
>> +++ b/drivers/usb/typec/altmodes/displayport.c
>> @@ -14,6 +14,7 @@
>> #include <linux/property.h>
>> #include <linux/usb/pd_vdo.h>
>> #include <linux/usb/typec_dp.h>
>> +#include <drm/bridge/aux-bridge.h>
>> #include <drm/drm_connector.h>
>> #include "displayport.h"
>>
>> @@ -182,6 +183,10 @@ static int dp_altmode_status_update(struct dp_altmode *dp)
>> dp->pending_irq_hpd = true;
>> }
>> } else {
>> + if (dp->port->hpd_dev)
>> + drm_aux_hpd_bridge_notify(dp->port->hpd_dev,
>> + hpd ? connector_status_connected :
>> + connector_status_disconnected);
> There should be no need for these calls. Once the HPD bridge is added to
> a correct fwnode, the drm_connector_oob_hotplug_event() calls should
> deliver the signal as expected.
It seems that only drm_bridge_connector can do this. I'm not sure if I remember correctly. I'll give it a try.
>
>> drm_connector_oob_hotplug_event(dp->connector_fwnode,
>> hpd ? connector_status_connected :
>> connector_status_disconnected);
>> @@ -206,6 +211,9 @@ static int dp_altmode_configured(struct dp_altmode *dp)
>> * configuration is complete to signal HPD.
>> */
>> if (dp->pending_hpd) {
>> + if (dp->port->hpd_dev)
>> + drm_aux_hpd_bridge_notify(dp->port->hpd_dev,
>> + connector_status_connected);
>> drm_connector_oob_hotplug_event(dp->connector_fwnode,
>> connector_status_connected);
>> sysfs_notify(&dp->alt->dev.kobj, "displayport", "hpd");
>> @@ -391,6 +399,9 @@ static int dp_altmode_vdm(struct typec_altmode *alt,
>> dp->data.status = 0;
>> dp->data.conf = 0;
>> if (dp->hpd) {
>> + if (dp->port->hpd_dev)
>> + drm_aux_hpd_bridge_notify(dp->port->hpd_dev,
>> + connector_status_disconnected);
>> drm_connector_oob_hotplug_event(dp->connector_fwnode,
>> connector_status_disconnected);
>> dp->hpd = false;
>> @@ -751,6 +762,18 @@ static const struct attribute_group *displayport_groups[] = {
>> NULL,
>> };
>>
>> +void dp_altmode_hpd_device_register(struct typec_altmode *alt)
>> +{
>> + if (alt->svid != USB_TYPEC_DP_SID)
>> + return;
>> +
>> + alt->hpd_dev = drm_dp_hpd_bridge_register(alt->dev.parent->parent,
>> + dev_of_node(alt->dev.parent->parent));
> This needs at least a comment, what is dev.parent->parent. Also, the
> of_node is not correct here. It should be a node of the connector,
> rather than the device itself. Consider USB-C controllers which handle
> several USB-C connectors (e.g. UCSI). The DRM core won't be able to
> identify the correct bridge.
I think alt.dev->parent->parent is the connector device. Am I missing something?
>
>> + if (IS_ERR(alt->hpd_dev))
>> + alt->hpd_dev = NULL;
>> +}
>> +EXPORT_SYMBOL_GPL(dp_altmode_hpd_device_register);
> Having the function here will bring a typec -> displayport dependency
> between drivers (which you didn't document). It means it won't be
> possible to build typec core into the kernel, having the DP AltMode
> driver in the module (which also doesn't sound like a good idea).
It make sense. Perhaps moving it into class.c would be a good idea.
>
>> +
>> int dp_altmode_probe(struct typec_altmode *alt)
>> {
>> const struct typec_altmode *port = typec_altmode_get_partner(alt);
--
Best,
Chaoyi
next prev parent reply other threads:[~2025-09-23 1:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 1:20 [PATCH v4 0/7] Add Type-C DP support for RK3399 EVB IND board Chaoyi Chen
2025-09-22 1:20 ` [PATCH v4 1/7] usb: typec: Add default HPD device when register DisplayPort altmode Chaoyi Chen
2025-09-22 7:56 ` kernel test robot
2025-09-22 8:49 ` kernel test robot
2025-09-23 1:10 ` Dmitry Baryshkov
2025-09-23 1:34 ` Chaoyi Chen [this message]
2025-09-23 3:11 ` Dmitry Baryshkov
2025-09-23 9:07 ` Chaoyi Chen
2025-09-23 10:40 ` Dmitry Baryshkov
2025-09-24 9:55 ` Chaoyi Chen
2025-09-25 4:01 ` Dmitry Baryshkov
2025-09-22 1:20 ` [PATCH v4 2/7] dt-bindings: phy: rockchip: rk3399-typec-phy: Support mode-switch Chaoyi Chen
2025-09-23 1:12 ` Dmitry Baryshkov
2025-09-23 1:53 ` Chaoyi Chen
2025-09-23 3:17 ` Dmitry Baryshkov
2025-09-23 3:40 ` Chaoyi Chen
2025-09-23 4:51 ` Dmitry Baryshkov
2025-09-23 7:17 ` Chaoyi Chen
2025-09-23 10:45 ` Dmitry Baryshkov
2025-09-23 3:42 ` Chaoyi Chen
2025-09-22 1:20 ` [PATCH v4 3/7] phy: rockchip: phy-rockchip-typec: Add typec_mux/typec_switch support Chaoyi Chen
2025-09-22 9:58 ` Dmitry Baryshkov
2025-09-22 1:20 ` [PATCH v4 4/7] drm/rockchip: cdn-dp: Support handle lane info without extcon Chaoyi Chen
2025-09-22 10:01 ` Dmitry Baryshkov
2025-09-23 1:15 ` Chaoyi Chen
2025-09-22 1:20 ` [PATCH v4 5/7] drm/rockchip: cdn-dp: Add multiple bridges to support PHY port selection Chaoyi Chen
2025-09-23 1:50 ` Dmitry Baryshkov
2025-09-23 2:09 ` Chaoyi Chen
2025-09-23 3:22 ` Dmitry Baryshkov
2025-09-23 3:33 ` Chaoyi Chen
2025-09-28 9:52 ` Chaoyi Chen
2025-09-28 21:27 ` Dmitry Baryshkov
2025-09-29 3:55 ` Chaoyi Chen
2025-09-22 1:20 ` [PATCH v4 6/7] arm64: dts: rockchip: Add missing dp_out port for RK3399 CDN-DP Chaoyi Chen
2025-09-22 1:20 ` [PATCH v4 7/7] arm64: dts: rockchip: rk3399-evb-ind: Add support for DisplayPort Chaoyi Chen
2025-09-22 17:27 ` [PATCH v4 0/7] Add Type-C DP support for RK3399 EVB IND board Rob Herring (Arm)
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=e9cf0aa8-ed32-4ffb-a755-150742455808@rock-chips.com \
--to=chaoyi.chen@rock-chips.com \
--cc=airlied@gmail.com \
--cc=amitsd@google.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsimic@manjaro.org \
--cc=frank.wang@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jbx6244@gmail.com \
--cc=kernel@airkyi.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pbrobinson@gmail.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vkoul@kernel.org \
--cc=yubing.zhang@rock-chips.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