From: Johan Hovold <johan@kernel.org>
To: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
Cc: Stefan Eichenberger <eichest@gmail.com>,
Johan Hovold <johan+linaro@kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH] USB: xhci-plat: fix legacy PHY double inity
Date: Mon, 6 Nov 2023 11:42:24 +0100 [thread overview]
Message-ID: <ZUjDEC9M7zTsXIRp@hovoldconsulting.com> (raw)
In-Reply-To: <bafbd60ac8134a0782a7ee27c01971ea@realtek.com>
On Mon, Nov 06, 2023 at 10:37:06AM +0000, Stanley Chang[昌育德] wrote:
> > > I use drivers/usb/dwc3/core.c and drivers/usb/dwc3/dwc3-rtk.c I
> > > describe the PHY as generic and legacy PHY in device tree.
> >
> > That's not right. You should just use the generic PHY binding for new platforms.
> >
> > > Our driver needs the API base on a08799cf17c2 ("usb: phy: add usb phy
> > notify port status API").
> > > But generic PHY driver is not support this.
> >
> > Yes, but you added that interface yourself, and that I think merging that was a
> > mistake.
> >
> > We should not be building functionality on top of the legacy USB PHY
> > implementation which is stuck in some transitional limbo.
> >
> > Apparently, your PHY drivers which were merged for 6.6 are the only users of
> > this interface, and there are no upstream devicetrees that use these PHYs.
> >
> > I think we should revert this mess before we dig ourselves into an even deeper
> > hole.
>
> This is an interim method, as the current generic PHY framework does
> not support special operations on USB PHY.
Then you need to add that.
You can't add a new interface which is broken by design and can't be
used unless you abuse the devicetree and describe your PHYs using *both*
the generic 'phy' property and the *deprecated* 'usb-phy' property.
That's just broken.
> Now the generic PHY can't instead USB PHY in this stage.
> For example,
> drivers/phy/ti/phy-twl4030-usb.c
> drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c
> drivers/phy/ti/phy-omap-usb2.c
These should be fixed as well eventually.
Johan
next prev parent reply other threads:[~2023-11-06 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 16:43 [PATCH] USB: xhci-plat: fix legacy PHY double init Johan Hovold
2023-11-04 12:43 ` [PATCH] USB: xhci-plat: fix legacy PHY double inity Stefan Eichenberger
2023-11-06 3:48 ` Stanley Chang[昌育德]
2023-11-06 6:53 ` Stanley Chang[昌育德]
2023-11-06 9:53 ` Johan Hovold
2023-11-06 10:08 ` Stanley Chang[昌育德]
2023-11-06 10:18 ` Johan Hovold
2023-11-06 10:37 ` Stanley Chang[昌育德]
2023-11-06 10:42 ` Johan Hovold [this message]
2023-11-07 1:16 ` Stanley Chang[昌育德]
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=ZUjDEC9M7zTsXIRp@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=eichest@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan+linaro@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mripard@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stanley_chang@realtek.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