From: Vinod Koul <vkoul@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heiko Stuebner <heiko@sntech.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Igor Paunovic <royalnet026@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-phy@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v16 1/6] phy: core: add notifier infrastructure
Date: Sat, 3 Oct 2026 11:04:13 +0200 [thread overview]
Message-ID: <asDFBIVf06-VaWdx@parshuram> (raw)
In-Reply-To: <20260924-b4-rockchip-dwc3-rockchip-glue-v16-1-126a2e9133c3@collabora.com>
Hello Sebastian,
On 24-09-26, 19:25, Sebastian Reichel wrote:
> Some PHY devices with multiple ports (e.g. USB3 and DP) require a reset
> if the configuration changes or cable orientation changes. This is a
> problem, as the consumer device will run into undefined behavior.
>
> With the new PHY notifier API introduced in this patch, the consumer
> driver can hook into reset events coming from a PHY device to handle the
> PHY going down gracefully.
>
> Note that this uses -ENOSYS instead of the more sensible -ENOTSUP for
> the stub functions when GENERIC_PHY is disabled to stay consistent with
> the existing ones.
I dont think this series has the usage of this.
I think I am still not convinced why a phy should notify as I dont feel
we have any mechanism to notifying. Checking status and letting people
know if not really a notification mechanism... Maybe add a status call
instead?
--
~Vinod
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heiko Stuebner <heiko@sntech.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Igor Paunovic <royalnet026@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-phy@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v16 1/6] phy: core: add notifier infrastructure
Date: Sat, 3 Oct 2026 11:04:13 +0200 [thread overview]
Message-ID: <asDFBIVf06-VaWdx@parshuram> (raw)
In-Reply-To: <20260924-b4-rockchip-dwc3-rockchip-glue-v16-1-126a2e9133c3@collabora.com>
Hello Sebastian,
On 24-09-26, 19:25, Sebastian Reichel wrote:
> Some PHY devices with multiple ports (e.g. USB3 and DP) require a reset
> if the configuration changes or cable orientation changes. This is a
> problem, as the consumer device will run into undefined behavior.
>
> With the new PHY notifier API introduced in this patch, the consumer
> driver can hook into reset events coming from a PHY device to handle the
> PHY going down gracefully.
>
> Note that this uses -ENOSYS instead of the more sensible -ENOTSUP for
> the stub functions when GENERIC_PHY is disabled to stay consistent with
> the existing ones.
I dont think this series has the usage of this.
I think I am still not convinced why a phy should notify as I dont feel
we have any mechanism to notifying. Checking status and letting people
know if not really a notification mechanism... Maybe add a status call
instead?
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heiko Stuebner <heiko@sntech.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Igor Paunovic <royalnet026@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-phy@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v16 1/6] phy: core: add notifier infrastructure
Date: Sat, 3 Oct 2026 11:04:13 +0200 [thread overview]
Message-ID: <asDFBIVf06-VaWdx@parshuram> (raw)
In-Reply-To: <20260924-b4-rockchip-dwc3-rockchip-glue-v16-1-126a2e9133c3@collabora.com>
Hello Sebastian,
On 24-09-26, 19:25, Sebastian Reichel wrote:
> Some PHY devices with multiple ports (e.g. USB3 and DP) require a reset
> if the configuration changes or cable orientation changes. This is a
> problem, as the consumer device will run into undefined behavior.
>
> With the new PHY notifier API introduced in this patch, the consumer
> driver can hook into reset events coming from a PHY device to handle the
> PHY going down gracefully.
>
> Note that this uses -ENOSYS instead of the more sensible -ENOTSUP for
> the stub functions when GENERIC_PHY is disabled to stay consistent with
> the existing ones.
I dont think this series has the usage of this.
I think I am still not convinced why a phy should notify as I dont feel
we have any mechanism to notifying. Checking status and letting people
know if not really a notification mechanism... Maybe add a status call
instead?
--
~Vinod
next prev parent reply other threads:[~2026-10-03 9:04 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 17:25 [PATCH v16 0/6] usb: dwc3: introduce Rockchip glue driver Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` [PATCH v16 1/6] phy: core: add notifier infrastructure Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:35 ` sashiko-bot
2026-09-26 7:47 ` Manivannan Sadhasivam
2026-09-26 7:47 ` Manivannan Sadhasivam
2026-09-26 7:47 ` Manivannan Sadhasivam
2026-10-03 9:04 ` Vinod Koul [this message]
2026-10-03 9:04 ` Vinod Koul
2026-10-03 9:04 ` Vinod Koul
2026-10-04 12:44 ` Sebastian Reichel
2026-10-04 12:44 ` Sebastian Reichel
2026-10-04 12:44 ` Sebastian Reichel
2026-10-05 8:30 ` Vinod Koul
2026-10-05 8:30 ` Vinod Koul
2026-10-05 8:30 ` Vinod Koul
2026-10-06 1:11 ` Sebastian Reichel
2026-10-06 1:11 ` Sebastian Reichel
2026-10-06 1:11 ` Sebastian Reichel
2026-09-24 17:25 ` [PATCH v16 2/6] usb: dwc3: rockchip: introduce glue driver Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:36 ` sashiko-bot
2026-09-24 17:25 ` [PATCH v16 3/6] usb: dwc3: core: add post PHY registration hook for platform glue Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` [PATCH v16 4/6] usb: dwc3: rockchip: support PHY reset notifications Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:38 ` sashiko-bot
2026-09-26 7:51 ` Manivannan Sadhasivam
2026-09-26 7:51 ` Manivannan Sadhasivam
2026-09-26 7:51 ` Manivannan Sadhasivam
2026-10-02 23:39 ` Thinh Nguyen
2026-10-02 23:39 ` Thinh Nguyen
2026-10-02 23:39 ` Thinh Nguyen
2026-09-24 17:25 ` [PATCH v16 5/6] usb: gadget: define stub for usb_udc_vbus_handler Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` [PATCH v16 6/6] usb: dwc3: rockchip: fix USB-C reconnect in gadget mode Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:25 ` Sebastian Reichel
2026-09-24 17:40 ` sashiko-bot
2026-09-27 12:02 ` Igor Paunovic
2026-09-27 12:02 ` Igor Paunovic
2026-09-27 12:02 ` Igor Paunovic
2026-10-02 22:57 ` Thinh Nguyen
2026-10-02 22:57 ` Thinh Nguyen
2026-10-02 22:57 ` Thinh Nguyen
2026-09-27 12:02 ` [PATCH v16 0/6] usb: dwc3: introduce Rockchip glue driver Igor Paunovic
2026-09-27 12:02 ` Igor Paunovic
2026-09-27 12:02 ` Igor Paunovic
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=asDFBIVf06-VaWdx@parshuram \
--to=vkoul@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--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=mani@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=royalnet026@gmail.com \
--cc=sebastian.reichel@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.