From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Chaoyi Chen <kernel@airkyi.com>, 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>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dragan Simic <dsimic@manjaro.org>,
Johan Jonker <jbx6244@gmail.com>,
Diederik de Haas <didi.debian@cknow.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
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 v6 1/8] usb: typec: Add default HPD device when register DisplayPort altmode
Date: Tue, 21 Oct 2025 17:44:11 +0800 [thread overview]
Message-ID: <1221dd6c-2035-4e5d-8052-341da279fe81@rock-chips.com> (raw)
In-Reply-To: <aPdI7Vb_djrfCfbT@kuha.fi.intel.com>
On 10/21/2025 4:48 PM, Heikki Krogerus wrote:
> Hi,
>
> On Mon, Oct 20, 2025 at 07:07:46PM +0800, Chaoyi Chen wrote:
>> Hi Heikki,
>>
>> On 10/20/2025 6:02 PM, Heikki Krogerus wrote:
>>> On Thu, Oct 16, 2025 at 10:27:34AM +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>
>>>> ---
>>>>
>>>> Changes in v6:
>>>> - Fix depend in Kconfig.
>>>>
>>>> Changes in v5:
>>>> - Remove the calls related to `drm_aux_hpd_bridge_notify()`.
>>>> - Place the helper functions in the same compilation unit.
>>>> - Add more comments about parent device.
>>>>
>>>> drivers/usb/typec/Kconfig | 2 ++
>>>> drivers/usb/typec/class.c | 26 ++++++++++++++++++++++++++
>>>> include/linux/usb/typec_altmode.h | 2 ++
>>>> 3 files changed, 30 insertions(+)
>>>>
>>>> diff --git a/drivers/usb/typec/Kconfig b/drivers/usb/typec/Kconfig
>>>> index 2f80c2792dbd..a6730fbb576b 100644
>>>> --- a/drivers/usb/typec/Kconfig
>>>> +++ b/drivers/usb/typec/Kconfig
>>>> @@ -2,6 +2,8 @@
>>>> menuconfig TYPEC
>>>> tristate "USB Type-C Support"
>>>> + depends on DRM || DRM=n
>>>> + select DRM_AUX_HPD_BRIDGE if DRM_BRIDGE && OF
>>> This is wrong. DRM should not dictate how this entire subsystem core
>>> is configured. The dependency needs to be on the DRM bridge side.
>>>
>>> You can for example use the bus notification there to see when a new
>>> alternate mode is being registered, or use some other notification
>>> mechanism.
>> Is it a good idea to implement notification functions like
>> drivers/usb/core/notify.c in TCPM, and then let other subsystems (such as DRM)
>> listen to these notifications?
> Don't limit this to tcpm only. I would suggest something similar what
> we have for usb bus: drivers/usb/core/notify.c
>
> So that, but for the typec bus. Then in DRM bridge code you just use
> typec_register/unregister_notify().
I will try to add drivers/usb/typec/notify.c in v7 to implement this. Thank you.
>
> thanks,
>
--
Best,
Chaoyi
next prev parent reply other threads:[~2025-10-21 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 2:27 [PATCH v6 0/8] Add Type-C DP support for RK3399 EVB IND board Chaoyi Chen
2025-10-16 2:27 ` [PATCH v6 1/8] usb: typec: Add default HPD device when register DisplayPort altmode Chaoyi Chen
2025-10-20 10:02 ` Heikki Krogerus
2025-10-20 11:07 ` Chaoyi Chen
2025-10-21 8:48 ` Heikki Krogerus
2025-10-21 9:44 ` Chaoyi Chen [this message]
2025-10-16 2:27 ` [PATCH v6 2/8] dt-bindings: phy: rockchip: rk3399-typec-phy: Support mode-switch Chaoyi Chen
2025-10-16 2:27 ` [PATCH v6 3/8] phy: rockchip: phy-rockchip-typec: Add typec_mux/typec_switch support Chaoyi Chen
2025-10-16 2:27 ` [PATCH v6 4/8] phy: rockchip: phy-rockchip-typec: Add DRM AUX bridge Chaoyi Chen
2025-10-16 2:27 ` [PATCH v6 5/8] drm/rockchip: cdn-dp: Support handle lane info without extcon Chaoyi Chen
2025-10-16 2:27 ` [PATCH v6 6/8] drm/rockchip: cdn-dp: Add multiple bridges to support PHY port selection Chaoyi Chen
2025-10-16 2:27 ` [PATCH v6 7/8] arm64: dts: rockchip: Add missing dp_out port for RK3399 CDN-DP Chaoyi Chen
2025-10-16 2:27 ` [PATCH v6 8/8] arm64: dts: rockchip: rk3399-evb-ind: Add support for DisplayPort Chaoyi Chen
2025-10-16 12:11 ` [PATCH v6 0/8] 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=1221dd6c-2035-4e5d-8052-341da279fe81@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
all inboxes | Powered by JetHome®