initialize (multiple) PHYs for a HCD
Subsystems (11)
Martin Blumenstingl
reviewerv11 cover initialize (multiple) PHYs for a HCD
The goal of this series is to initialize multiple PHYs on a USB host controller, which is needed on Amlogic Meson GXL and GXM SoCs.
- Amlogic Meson GXL and GXM SoCs come with a dwc3 IP block which has two or three USB2 ports enabled on the internal root-hub. The SoCs also provide separate USB2 PHYs, one per port. All USB2 PHYs (which are internally "connected" to the dwc3 roothub) need to be powered on, otherwise USB devices cannot be enumerated (even if just one PHY is disabled and if the device is plugged into another, enabled port)
- dwc3 already takes one USB2 and one USB3 PHY and initializes these correctly
- some other HCI platform drivers (like ehci-platform.c, xhci-mtk.c and ohci-platform.c) do not have a limitation on the number of PHYs - they support any number of USB PHYs (typically one PHY per actual port)
This series adds a new "PHY wrapper". This can be configured through devicetree by passing a "phys" property (with any number of PHY handles) to the USB controller.
Additionally it this integrates this new PHY wrapper into hcd.c which automatically enables it for all USB controller drivers (tested on an Amlogic Meson GXL SoC which uses a dwc3 controller). Since this leaves some duplicate code (which now becomes obsolete!) in various drivers this is being cleaned up as well.
Changes since v10 at [13]:
- added Peter Chen's Acked-by to patch #2 (thank you!)
- rebased to usb-next (134d1fd44221614 "Merge 4.16-rc3 into usb-next")
Changes since v9 at [12]:
- changed "skip_phy_initialization" from PATCH #2 into a bitfield and moved it below the "remove_phy" bitfield as suggested by Alan Stern (thanks!)
- rebased against usb-next (which is currently identical to v4.16-rc1)
Changes since v8 at [10]:
- add new patch #2 which allows disabling "USB PHY management" in the USB HCD core driver. this also affects patch #4 which now checks the skip_phy_initialization flag before calling usb_phy_roothub_{init,power_on} (other functions don't need to be guarded since they are null-safe - see patch #3)
- integrated my other series 'remove driver-specific "multiple PHY" handling' from [11] into this one so the result of this "generic" code (= removing duplicate code in various drivers) can be seen directly. affects patches #5-8. (note: patch #1 "usb: mtu3: remove custom USB PHY handling" from that series was dropped, because it broke device mode support - Chunfeng Yun will come up with a separate patch later. patch #5 "usb: chipidea: do not set the "phy" field in struct usb_hcd" from that series was rewritten and is now integrated into the new patch #2 from this series)
- collected all {Reviewed,Tested,Acked}-by
- dropped RfC prefix since this v8 was out for review for two weeks and it only got Reviewed-by's and Tested-by's since then
Changes since v7 at [8]:
- updated the description in the cover-letter
- wrapped the only call usb_phy_roothub_power_{on,off} in hcd_bus_{resume,suspend} during system-suspend (excluding it from being called during runtime/auto suspend). this also fixes a problem on Meson GXL which does not detect that a new device has been connected if the PHYs are powered off. Thanks to Manu Gautam for suggesting this! (affects patch #3)
- after a discussion about the dt-bindings of this patch I went back to simply specifying a "phys" property (without a corresponding phy-names property) to pass all PHYs directly in the node of the USB controller. From my understanding the root hub node was "artificial" and we should describe it's properties as part of the controller, rather than introducing a sub-node. see also the discussion with Arnd in [9] (this affects patch #1 and #2)
- dropped patch #4 ("dt-bindings: usb: xhci: include the roothub and a device in the example") because we're back to just specifying a "phys" property directly within the controller.
NOTE: some HCI platform drivers are using the "phys" property as well. With this series phy_{init,power_on,power_off,exit} will be called twice for each PHY when using a ehci-platform.c or xhci-mtk.c USB controller (because the controller driver and our new, generic code now manage the PHYs). the PHY framework handles this gracefully (by ref-counting all operations). a follow-up series will be sent which removes the custom handling from the affected drivers (so only the new PHY wrapper will manage the PHYs state after that follow-up series).
- fixed an unnecessary whitespace change spotted by Alan Stern (thanks!) in patch #3
- removed all Tested-by's since we're changing code again
Changes since v6 at [6]:
- fixed unnecessary whitespace change (noticed by Alan Stern - thanks)
- added PATCH #4 to clarify (with an example) how I understood how Rob wanted the dt-binding to look like (see [0]). please wait for an ACK from Rob on this one to make sure that we're not introducing some broken binding (as discussed with Arnd: [7])
- added Alan Stern's ACK on PATCH #3
- added Neil's Tested-by on PATCH #2 and #3
Changes since RfC v5 at [5]:
- dropped RfC prefix
- removed noisy dev_err if no roothub node was found (spotted by Xiaolong Ye's kbuild test robot - thank you for that!)
- moved the call to usb_phy_roothub_power_off() within hcd_bus_suspend() to make sure that the PHYs are turned off if the "race with a root-hub wakeup event" condition is met (in this case the PHYs are turned on again, with the old code we did break the PHYs internal ref-counting because we never turned the PHYs off before turning them on again in case of that special "race with a root-hub wakeup event").
additionally we're not handling the status returned by usb_phy_roothub_power_off() anymore (the bus is already turned off and we tried to turn off all PHYs as well - only the PHYs which failed to power off will stay in the current state). thanks to Alan Stern for the suggestion
- removed return value from usb_phy_roothub_power_off() because none of my code uses it anymore. thanks to Alan Stern for the suggestion
Changes since v4 at [4]:
- renamed the subject of the cover-letter (old name was:
"initialize (multiple) PHYs in xhci-plat")
- back into RFC status (see below for the reasons)
- dropped Tested-by from Chunfeng Yun (same reasons as RFC status)
- reworded cover-letter and commit messages from "platform-roothub" to "roothub PHY wrapper"
- moved code from drivers/usb/host/platform-roothub.* to drivers/usb/core/phy.* and the changes to drivers/usb/host/xhci-plat.c to drivers/usb/core/hcd.c as suggested by Mathias Nyman (as a benefit this will enable the new logic for non-xHCI controllers as well - however this was not tested yet)
- rename the structs, function names, etc from platform_roothub_* to usb_phy_roothub*
Changes since RFCv3 at [3]:
- moved the DT binding change from patch #3 to patch #1 as suggested by Rob Herring (and slightly adjusted the commit message to account for that)
- added Tested-by from Chunfeng Yun (who confirmed that the whole concept and implementation works fine on Mediatek SoCs - many thanks again!) to patch #2
- added Rob Herring's ACK to patches 1 and 3
- dropped RFC status (RFCv3 -> PATCH v4)
Changes since RFCv2 at [2]:
- split phy_{init,exit} and phy_power_{on,off} handling. up until RFCv2 I called phy_init plus phy_power_on in platform_roothub_power_on and phy_power_off plus phy_exit in platform_roothub_power_off. However, Chunfeng Yun (a Mediatek SoC developer - many thanks for testing my series and providing great feedback) reported that only using phy_power_off (and omitting phy_exit) during system suspend fixes an issue where USB devices would be re-enumerated when resuming. His original problem description: "In order to keep link state on mt8173, we just power off all phys(not exit) when system enter suspend, then power on them again (needn't init, otherwise device will be disconnected) when system resume, this can avoid re-enumerating device.". This fix affects patch #2 and #3 as we now have platform_roothub_init (which calls phy_init internally), platform_roothub_power_on (which calls phy_power_on internally), platform_roothub_power_off (which calls phy_power_off internally) and platform_roothub_exit (which calls phy_exit internally). suspend and resume only call platform_roothub_power_{on,off} to prevent the issue described by Chunfeng Yun (unfortunately I cannot test this because the Amlogic platform currently does not support system suspend).
- dropped two struct forward declarations from platform-roothub.h which are not used in the header file (thanks to Chunfeng Yun for spotting this)
Changes since RFCv1 at [1]:
- split the usb-xhci dt-binding documentation into a separate patch
- fixed a typo ("usb-phy" -> "phys" in the dt-binding example)
- rebased to apply against latest usb-next
[0] http://lists.infradead.org/pipermail/linux-amlogic/2016-November/001818.html
[1] http://marc.info/?l=linux-usb&m=148414866303604&w=2
[2] https://www.spinics.net/lists/linux-usb/msg158967.html
[3] https://www.spinics.net/lists/devicetree/msg190426.html
[4] http://lists.infradead.org/pipermail/linux-amlogic/2017-September/004685.html
[5] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/004924.html
[6] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/005049.html
[7] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/005121.html
[8] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/005124.html
[9] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/005192.html
[10] http://lists.infradead.org/pipermail/linux-amlogic/2018-January/006274.html
[11] https://marc.info/?l=linux-usb&m=151683941207898&w=2
[12] http://lists.infradead.org/pipermail/linux-amlogic/2018-February/006412.html
[13] http://lists.infradead.org/pipermail/linux-amlogic/2018-February/006478.html
Martin Blumenstingl (8):
dt-bindings: usb: add the documentation for USB HCDs
usb: add a flag to skip PHY initialization to struct usb_hcd
usb: core: add a wrapper for the USB PHYs on the HCD
usb: core: hcd: integrate the PHY wrapper into the HCD core
usb: host: xhci-mtk: remove custom USB PHY handling
usb: host: ehci-platform: remove custom USB PHY handling
usb: host: ohci-platform: remove custom USB PHY handling
usb: core: hcd: remove support for initializing a single PHY
.../devicetree/bindings/usb/mediatek,mtk-xhci.txt | 5 +- .../devicetree/bindings/usb/mediatek,mtu3.txt | 5 +- Documentation/devicetree/bindings/usb/usb-ehci.txt | 6 +- Documentation/devicetree/bindings/usb/usb-hcd.txt | 9 ++ Documentation/devicetree/bindings/usb/usb-ohci.txt | 6 +- Documentation/devicetree/bindings/usb/usb-uhci.txt | 3 + Documentation/devicetree/bindings/usb/usb-xhci.txt | 5 + drivers/usb/chipidea/host.c | 6 +- drivers/usb/core/Makefile | 2 +- drivers/usb/core/hcd.c | 64 ++++----- drivers/usb/core/phy.c | 158 +++++++++++++++++++++ drivers/usb/core/phy.h | 7 + drivers/usb/host/ehci-fsl.c | 2 + drivers/usb/host/ehci-platform.c | 55 +------ drivers/usb/host/ehci-tegra.c | 1 + drivers/usb/host/ohci-omap.c | 1 + drivers/usb/host/ohci-platform.c | 56 +------- drivers/usb/host/xhci-mtk.c | 98 +------------ drivers/usb/host/xhci-plat.c | 1 + include/linux/usb/hcd.h | 8 +- 20 files changed, 253 insertions(+), 245 deletions(-) create mode 100644 Documentation/devicetree/bindings/usb/usb-hcd.txt create mode 100644 drivers/usb/core/phy.c create mode 100644 drivers/usb/core/phy.h
Signature · 1 line
2.16.2
Martin Blumenstingl
reviewerPATCH v11 1/8 dt-bindings: usb: add the documentation for USB HCDs
A USB HCD may have several PHYs which need to be configured before the the HCD starts working.
This adds the documentation for such a USB HCD as well as a reference to the new "usb-hcd.txt" from all bindings that implement a USB HCD which support one USB PHY per port.
--- Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt | 5 ++++- Documentation/devicetree/bindings/usb/mediatek,mtu3.txt | 5 ++++- Documentation/devicetree/bindings/usb/usb-ehci.txt | 6 ++++-- Documentation/devicetree/bindings/usb/usb-hcd.txt | 9 +++++++++ Documentation/devicetree/bindings/usb/usb-ohci.txt | 6 ++++-- Documentation/devicetree/bindings/usb/usb-uhci.txt | 3 +++ Documentation/devicetree/bindings/usb/usb-xhci.txt | 5 +++++ 7 files changed, 33 insertions(+), 6 deletions(-) create mode 100644 Documentation/devicetree/bindings/usb/usb-hcd.txt
Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt +4 -1
@@ -32,7 +32,7 @@ Required properties: "mcu_ck": mcu_bus clock for register access, "dma_ck": dma_bus clock for data transfer by DMA - - phys : a list of phandle + phy specifier pairs + - phys : see usb-hcd.txt in the current directory Optional properties: - wakeup-source : enable USB remote wakeup;
@@ -52,6 +52,9 @@ Optional properties: See: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt - imod-interval-ns: default interrupt moderation interval is 5000ns +additionally the properties from usb-hcd.txt (in the current directory) are +supported. + Example: usb30: usb at 11270000 { compatible = "mediatek,mt8173-xhci";
Documentation/devicetree/bindings/usb/mediatek,mtu3.txt +4 -1
@@ -17,7 +17,7 @@ Required properties: - clock-names : must contain "sys_ck" for clock of controller, the following clocks are optional: "ref_ck", "mcu_ck" and "dam_ck"; - - phys : a list of phandle + phy specifier pairs + - phys : see usb-hcd.txt in the current directory - dr_mode : should be one of "host", "peripheral" or "otg", refer to usb/generic.txt
@@ -53,6 +53,9 @@ Optional properties: - mediatek,u3p-dis-msk : mask to disable u3ports, bit0 for u3port0, bit1 for u3port1, ... etc; +additionally the properties from usb-hcd.txt (in the current directory) are +supported. + Sub-nodes: The xhci should be added as subnode to mtu3 as shown in the following example if host mode is enabled. The DT binding details of xhci can be found in:
Documentation/devicetree/bindings/usb/usb-ehci.txt +4 -2
@@ -16,10 +16,12 @@ Optional properties: - has-transaction-translator : boolean, set this if EHCI have a Transaction Translator built into the root hub. - clocks : a list of phandle + clock specifier pairs - - phys : phandle + phy specifier pair - - phy-names : "usb" + - phys : see usb-hcd.txt in the current directory - resets : phandle + reset specifier pair +additionally the properties from usb-hcd.txt (in the current directory) are +supported. + Example (Sequoia 440EPx): ehci at e0000300 { compatible = "ibm,usb-ehci-440epx", "usb-ehci";
Documentation/devicetree/bindings/usb/usb-hcd.txt new file +9 -0
@@ -0,0 +1,9 @@ +Generic USB HCD (Host Controller Device) Properties + +Optional properties: +- phys: a list of all USB PHYs on this HCD + +Example: + &usb1 { + phys = <&usb2_phy1>, <&usb3_phy1>; + };
Documentation/devicetree/bindings/usb/usb-ohci.txt +4 -2
@@ -13,10 +13,12 @@ Optional properties: - remote-wakeup-connected: remote wakeup is wired on the platform - num-ports : u32, to override the detected port count - clocks : a list of phandle + clock specifier pairs -- phys : phandle + phy specifier pair -- phy-names : "usb" +- phys : see usb-hcd.txt in the current directory - resets : a list of phandle + reset specifier pairs +additionally the properties from usb-hcd.txt (in the current directory) are +supported. + Example: ohci0: usb at 1c14400 {
Documentation/devicetree/bindings/usb/usb-uhci.txt +3 -0
@@ -6,6 +6,9 @@ Required properties: - reg : Should contain 1 register ranges(address and length) - interrupts : UHCI controller interrupt +additionally the properties from usb-hcd.txt (in the current directory) are +supported. + Example: uhci at d8007b00 {
Documentation/devicetree/bindings/usb/usb-xhci.txt +5 -0
@@ -32,6 +32,11 @@ Optional properties: - usb3-lpm-capable: determines if platform is USB3 LPM capable - quirk-broken-port-ped: set if the controller has broken port disable mechanism - imod-interval-ns: default interrupt moderation interval is 5000ns + - phys : see usb-hcd.txt in the current directory + +additionally the properties from usb-hcd.txt (in the current directory) are +supported. + Example: usb at f0931000 {
Signature · 1 line
2.16.2
Martin Blumenstingl
reviewerPATCH v11 2/8 usb: add a flag to skip PHY initialization to struct usb_hcd
In reply to Martin BlumenstinglThe USB HCD core driver parses the device-tree node for "phys" and "usb-phys" properties. It also manages the power state of these PHYs automatically.
However, drivers may opt-out of this behavior by setting "phy" or "usb_phy" in struct usb_hcd to a non-null value. An example where this is required is the "Qualcomm USB2 controller", implemented by the chipidea driver. The hardware requires that the PHY is only powered on after the "reset completed" event from the controller is received.
A follow-up patch will allow the USB HCD core driver to manage more than one PHY. Add a new "skip_phy_initialization" bitflag to struct usb_hcd so drivers can opt-out of any PHY management provided by the USB HCD core driver.
This also updates the existing drivers so they use the new flag if they want to opt out of the PHY management provided by the USB HCD core driver. This means that for these drivers the new "multiple PHY" handling (which will be added in a follow-up patch) will be disabled as well.
--- drivers/usb/chipidea/host.c | 6 ++---- drivers/usb/core/hcd.c | 4 ++-- drivers/usb/host/ehci-fsl.c | 2 ++ drivers/usb/host/ehci-platform.c | 4 ++-- drivers/usb/host/ehci-tegra.c | 1 + drivers/usb/host/ohci-omap.c | 1 + drivers/usb/host/ohci-platform.c | 4 ++-- drivers/usb/host/xhci-plat.c | 1 + include/linux/usb/hcd.h | 6 ++++++ 9 files changed, 19 insertions(+), 10 deletions(-)
drivers/usb/chipidea/host.c +2 -4
@@ -124,10 +124,8 @@ static int host_start(struct ci_hdrc *ci) hcd->power_budget = ci->platdata->power_budget; hcd->tpl_support = ci->platdata->tpl_support; -if (ci->phy) - hcd->phy = ci->phy; -else - hcd->usb_phy = ci->usb_phy; +if (ci->phy || ci->usb_phy) + hcd->skip_phy_initialization =1 ; ehci =hcd_to_ehci (hcd); ehci->caps = ci->hw_bank.cap;
drivers/usb/core/hcd.c +2 -2
@@ -2727,7 +2727,7 @@ int usb_add_hcd(struct usb_hcd *hcd,int retval;struct usb_device *rhdev; -if (IS_ENABLED (CONFIG_USB_PHY ) && !hcd->usb_phy) { +if (IS_ENABLED (CONFIG_USB_PHY ) && !hcd->skip_phy_initialization) {struct usb_phy *phy =usb_get_phy_dev (hcd->self.sysdev,0 );if (IS_ERR (phy)) {
@@ -2745,7 +2745,7 @@ int usb_add_hcd(struct usb_hcd *hcd, } } -if (IS_ENABLED (CONFIG_GENERIC_PHY ) && !hcd->phy) { +if (IS_ENABLED (CONFIG_GENERIC_PHY ) && !hcd->skip_phy_initialization) {struct phy *phy =phy_get (hcd->self.sysdev,"usb" );if (IS_ERR (phy)) {
drivers/usb/host/ehci-fsl.c +2 -0
@@ -155,6 +155,8 @@ static int fsl_ehci_drv_probe(struct platform_device *pdev) retval = -ENODEV ; goto err2; } + + hcd->skip_phy_initialization =1 ; }#endif return retval;
drivers/usb/host/ehci-platform.c +2 -2
@@ -219,9 +219,9 @@ static int ehci_platform_probe(struct platform_device *dev)if (IS_ERR (priv->phys[phy_num])) { err =PTR_ERR (priv->phys[phy_num]); goto err_put_hcd; - }else if (!hcd->phy) { + }else {/* Avoiding phy_get() in usb_add_hcd() */ - hcd->phy = priv->phys[phy_num]; + hcd->skip_phy_initialization =1 ; } }
drivers/usb/host/ehci-tegra.c +1 -0
@@ -461,6 +461,7 @@ static int tegra_ehci_probe(struct platform_device *pdev) goto cleanup_clk_en; } hcd->usb_phy = u_phy; + hcd->skip_phy_initialization =1 ; tegra->needs_double_reset =of_property_read_bool (pdev->dev.of_node,"nvidia,needs-double-reset" );
drivers/usb/host/ohci-omap.c +1 -0
@@ -230,6 +230,7 @@ static int ohci_omap_reset(struct usb_hcd *hcd) } else {return -EPROBE_DEFER ; } + hcd->skip_phy_initialization =1 ; ohci->start_hnp = start_hnp; }#endif
drivers/usb/host/ohci-platform.c +2 -2
@@ -186,9 +186,9 @@ static int ohci_platform_probe(struct platform_device *dev)if (IS_ERR (priv->phys[phy_num])) { err =PTR_ERR (priv->phys[phy_num]); goto err_put_hcd; - }else if (!hcd->phy) { + }else {/* Avoiding phy_get() in usb_add_hcd() */ - hcd->phy = priv->phys[phy_num]; + hcd->skip_phy_initialization =1 ; } }
drivers/usb/host/xhci-plat.c +1 -0
@@ -284,6 +284,7 @@ static int xhci_plat_probe(struct platform_device *pdev) ret =usb_phy_init (hcd->usb_phy);if (ret) goto put_usb3_hcd; + hcd->skip_phy_initialization =1 ; } ret =usb_add_hcd (hcd, irq,IRQF_SHARED );
include/linux/usb/hcd.h +6 -0
@@ -151,6 +151,12 @@ struct usb_hcd { unsigned msix_enabled:1; /* driver has MSI-X enabled? */ unsigned msi_enabled:1; /* driver has MSI enabled? */ unsigned remove_phy:1; /* auto-remove USB phy */ +/* +* do not manage the PHY state in the HCD core, instead let the driver +* handle this (for example if the PHY can only be turned on after a +* specific event) +*/ + unsigned skip_phy_initialization:1;/* The next flag is a stopgap, to be removed when all the HCDs * support the new root-hub polling mechanism. */
Signature · 1 line
2.16.2
Martin Blumenstingl
reviewerPATCH v11 3/8 usb: core: add a wrapper for the USB PHYs on the HCD
In reply to Martin BlumenstinglMany SoC platforms have separate devices for the USB PHY which are registered through the generic PHY framework. These PHYs have to be enabled to make the USB controller actually work. They also have to be disabled again on shutdown/suspend.
Currently (at least) the following HCI platform drivers are using custom code to obtain all PHYs via devicetree for the roothub/controller and disable/enable them when required:
- ehci-platform.c has ehci_platform_power_{on,off}
- xhci-mtk.c has xhci_mtk_phy_{init,exit,power_on,power_off}
- ohci-platform.c has ohci_platform_power_{on,off}
With this new wrapper the USB PHYs can be specified directly in the USB controller's devicetree node (just like on the drivers listed above). This allows SoCs like the Amlogic Meson GXL family to operate correctly once this is wired up correctly. These SoCs use a dwc3 controller and require all USB PHYs to be initialized (if one of the USB PHYs it not initialized then none of USB port works at all).
--- drivers/usb/core/Makefile | 2 +- drivers/usb/core/phy.c | 158 ++++++++++++++++++++++++++++++++++++++++++++++ drivers/usb/core/phy.h | 7 ++ 3 files changed, 166 insertions(+), 1 deletion(-) create mode 100644 drivers/usb/core/phy.c create mode 100644 drivers/usb/core/phy.h
drivers/usb/core/Makefile +1 -1
@@ -6,7 +6,7 @@ usbcore-y := usb.o hub.o hcd.o urb.o message.o driver.o usbcore-y += config.o file.o buffer.o sysfs.o endpoint.o usbcore-y += devio.o notify.o generic.o quirks.o devices.o -usbcore-y += port.o +usbcore-y += phy.o port.o usbcore-$(CONFIG_OF) += of.o usbcore-$(CONFIG_USB_PCI) += hcd-pci.o
drivers/usb/core/phy.c new file +158 -0
158 lines not on this page · raw message
drivers/usb/core/phy.h new file +7 -0
@@ -0,0 +1,7 @@ +struct usb_phy_roothub ; + +struct usb_phy_roothub *usb_phy_roothub_init (struct device *dev); +int usb_phy_roothub_exit (struct usb_phy_roothub *phy_roothub); + +int usb_phy_roothub_power_on (struct usb_phy_roothub *phy_roothub); +void usb_phy_roothub_power_off (struct usb_phy_roothub *phy_roothub);
Signature · 1 line
2.16.2
PATCH v11 3/8 usb: core: add a wrapper for the USB PHYs on the HCD
2018-03-04 6:43 GMT+09:00 Martin Blumenstingl
<[email protected]>:
Quoted 121 lines
Many SoC platforms have separate devices for the USB PHY which are registered through the generic PHY framework. These PHYs have to be enabled to make the USB controller actually work. They also have to be disabled again on shutdown/suspend.
Currently (at least) the following HCI platform drivers are using custom code to obtain all PHYs via devicetree for the roothub/controller and disable/enable them when required:
-ehci-platform.chas ehci_platform_power_{on,off}
-xhci-mtk.chas xhci_mtk_phy_{init,exit,power_on,power_off}
-ohci-platform.chas ohci_platform_power_{on,off}With this new wrapper the USB PHYs can be specified directly in the USB controller's devicetree node (just like on the drivers listed above). This allows SoCs like the Amlogic Meson GXL family to operate correctly once this is wired up correctly. These SoCs use a dwc3 controller and require all USB PHYs to be initialized (if one of the USB PHYs it not initialized then none of USB port works at all).
Signed-off-by Martin Blumenstingl <[email protected]>Tested-by Yixun Lan <[email protected]>Cc Neil Armstrong <[email protected]>Cc Chunfeng Yun <[email protected]>--- drivers/usb/core/Makefile | 2 +- drivers/usb/core/phy.c | 158 ++++++++++++++++++++++++++++++++++++++++++++++ drivers/usb/core/phy.h | 7 ++ 3 files changed, 166 insertions(+), 1 deletion(-) create mode 100644 drivers/usb/core/phy.c create mode 100644 drivers/usb/core/phy.hdrivers/usb/core/Makefile +1
-1@@ -6,7 +6,7 @@ usbcore-y := usb.o hub.o hcd.o urb.o message.o driver.o usbcore-y += config.o file.o buffer.o sysfs.o endpoint.o usbcore-y += devio.o notify.o generic.o quirks.o devices.o -usbcore-y += port.o +usbcore-y += phy.o port.o usbcore-$(CONFIG_OF) += of.o usbcore-$(CONFIG_USB_PCI) += hcd-pci.odrivers/usb/core/phy.c new file +71
-0@@ -0,0 +1,158 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* +* A wrapper for multiple PHYs which passes all phy_* function calls to +* multiple (actual) PHY devices. This is comes handy when initializing +* all PHYs on a HCD and to keep them all in the same state. +* +* Copyright (C) 2018 Martin Blumenstingl <[email protected]> +*/ + +#include <linux/device.h> +#include <linux/list.h> +#include <linux/phy/phy.h> +#include <linux/of.h> + +#include "phy.h" + +struct usb_phy_roothub { +struct phy *phy; +struct list_head list; +}; + +static struct usb_phy_roothub *usb_phy_roothub_alloc (struct device *dev) +{ +struct usb_phy_roothub *roothub_entry; + + roothub_entry =devm_kzalloc (dev,sizeof (*roothub_entry),GFP_KERNEL ); +if (!roothub_entry) +return ERR_PTR (-ENOMEM ); + +INIT_LIST_HEAD (&roothub_entry->list); + +return roothub_entry; +} + +static int usb_phy_roothub_add_phy (struct device *dev,int index, +struct list_head *list) +{ +struct usb_phy_roothub *roothub_entry; +struct phy *phy =devm_of_phy_get_by_index (dev, dev->of_node, index); + +if (IS_ERR_OR_NULL (phy)) { +if (!phy ||PTR_ERR (phy) == -ENODEV ) +return 0 ; +else +return PTR_ERR (phy); + } + + roothub_entry =usb_phy_roothub_alloc (dev); +if (IS_ERR (roothub_entry)) +return PTR_ERR (roothub_entry); + + roothub_entry->phy = phy; + +list_add_tail (&roothub_entry->list, list); + +return 0 ; +} + +struct usb_phy_roothub *usb_phy_roothub_init (struct device *dev) +{ +struct usb_phy_roothub *phy_roothub; +struct usb_phy_roothub *roothub_entry; +struct list_head *head; +int i, num_phys, err; + + num_phys =of_count_phandle_with_args (dev->of_node,"phys" , +"#phy-cells" ); +if (num_phys <=0 ) +return NULL ; + + phy_roothub =usb_phy_roothub_alloc (dev);
drivers/usb/core/phy.c line 81
Quoted 10 lines
drivers/usb/core/phy.c new file +10
-0+if (IS_ERR (phy_roothub)) +return phy_roothub; + +for (i =0 ; i < num_phys; i++) { + err =usb_phy_roothub_add_phy (dev, i, &phy_roothub->list); +if (err) + goto err_out; + } + + head = &phy_roothub->list;
I think phy_roothub->phy is always empty,
and only phy_roothub->list is used.
I just wondered if we can directly put 'struct list_head' into 'struct usb_hcd'.
drivers/usb/core/phy.h line 1
Quoted 7 lines
drivers/usb/core/phy.h new file +1
-0@@ -0,0 +1,7 @@ +struct usb_phy_roothub ;
struct device;
is also needed for usb_phy_roothub_init().
drivers/usb/core/phy.h line 7
Quoted 5 lines
drivers/usb/core/phy.h new file +5
-0+struct usb_phy_roothub *usb_phy_roothub_init (struct device *dev); +int usb_phy_roothub_exit (struct usb_phy_roothub *phy_roothub); + +int usb_phy_roothub_power_on (struct usb_phy_roothub *phy_roothub); +void usb_phy_roothub_power_off (struct usb_phy_roothub *phy_roothub);
Better to add an include guard?
SPDX-License-Identifier for this header too?
Signature · 2 lines
Best Regards Masahiro Yamada
Martin Blumenstingl
reviewerPATCH v11 3/8 usb: core: add a wrapper for the USB PHYs on the HCD
Hello,
(great to hear that this might be useful on Socionext SoCs as well :))
Quoted 139 lines · Masahiro Yamada
2018-03-04 6:43 GMT+09:00 Martin Blumenstingl
<[email protected]>:Quoted 121 lines
Many SoC platforms have separate devices for the USB PHY which are registered through the generic PHY framework. These PHYs have to be enabled to make the USB controller actually work. They also have to be disabled again on shutdown/suspend.
Currently (at least) the following HCI platform drivers are using custom code to obtain all PHYs via devicetree for the roothub/controller and disable/enable them when required:
-ehci-platform.chas ehci_platform_power_{on,off}
-xhci-mtk.chas xhci_mtk_phy_{init,exit,power_on,power_off}
-ohci-platform.chas ohci_platform_power_{on,off}With this new wrapper the USB PHYs can be specified directly in the USB controller's devicetree node (just like on the drivers listed above). This allows SoCs like the Amlogic Meson GXL family to operate correctly once this is wired up correctly. These SoCs use a dwc3 controller and require all USB PHYs to be initialized (if one of the USB PHYs it not initialized then none of USB port works at all).
Signed-off-by Martin Blumenstingl <[email protected]>Tested-by Yixun Lan <[email protected]>Cc Neil Armstrong <[email protected]>Cc Chunfeng Yun <[email protected]>--- drivers/usb/core/Makefile | 2 +- drivers/usb/core/phy.c | 158 ++++++++++++++++++++++++++++++++++++++++++++++ drivers/usb/core/phy.h | 7 ++ 3 files changed, 166 insertions(+), 1 deletion(-) create mode 100644 drivers/usb/core/phy.c create mode 100644 drivers/usb/core/phy.hdrivers/usb/core/Makefile +1
-1@@ -6,7 +6,7 @@ usbcore-y := usb.o hub.o hcd.o urb.o message.o driver.o usbcore-y += config.o file.o buffer.o sysfs.o endpoint.o usbcore-y += devio.o notify.o generic.o quirks.o devices.o -usbcore-y += port.o +usbcore-y += phy.o port.o usbcore-$(CONFIG_OF) += of.o usbcore-$(CONFIG_USB_PCI) += hcd-pci.odrivers/usb/core/phy.c new file +71
-0@@ -0,0 +1,158 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* +* A wrapper for multiple PHYs which passes all phy_* function calls to +* multiple (actual) PHY devices. This is comes handy when initializing +* all PHYs on a HCD and to keep them all in the same state. +* +* Copyright (C) 2018 Martin Blumenstingl <[email protected]> +*/ + +#include <linux/device.h> +#include <linux/list.h> +#include <linux/phy/phy.h> +#include <linux/of.h> + +#include "phy.h" + +struct usb_phy_roothub { +struct phy *phy; +struct list_head list; +}; + +static struct usb_phy_roothub *usb_phy_roothub_alloc (struct device *dev) +{ +struct usb_phy_roothub *roothub_entry; + + roothub_entry =devm_kzalloc (dev,sizeof (*roothub_entry),GFP_KERNEL ); +if (!roothub_entry) +return ERR_PTR (-ENOMEM ); + +INIT_LIST_HEAD (&roothub_entry->list); + +return roothub_entry; +} + +static int usb_phy_roothub_add_phy (struct device *dev,int index, +struct list_head *list) +{ +struct usb_phy_roothub *roothub_entry; +struct phy *phy =devm_of_phy_get_by_index (dev, dev->of_node, index); + +if (IS_ERR_OR_NULL (phy)) { +if (!phy ||PTR_ERR (phy) == -ENODEV ) +return 0 ; +else +return PTR_ERR (phy); + } + + roothub_entry =usb_phy_roothub_alloc (dev); +if (IS_ERR (roothub_entry)) +return PTR_ERR (roothub_entry); + + roothub_entry->phy = phy; + +list_add_tail (&roothub_entry->list, list); + +return 0 ; +} + +struct usb_phy_roothub *usb_phy_roothub_init (struct device *dev) +{ +struct usb_phy_roothub *phy_roothub; +struct usb_phy_roothub *roothub_entry; +struct list_head *head; +int i, num_phys, err; + + num_phys =of_count_phandle_with_args (dev->of_node,"phys" , +"#phy-cells" ); +if (num_phys <=0 ) +return NULL ; + + phy_roothub =usb_phy_roothub_alloc (dev);drivers/usb/core/phy.c line 81
Quoted 10 lines
drivers/usb/core/phy.c new file +10
-0+if (IS_ERR (phy_roothub)) +return phy_roothub; + +for (i =0 ; i < num_phys; i++) { + err =usb_phy_roothub_add_phy (dev, i, &phy_roothub->list); +if (err) + goto err_out; + } + + head = &phy_roothub->list;I think
phy_roothub->phyis always empty,
and onlyphy_roothub->listis used.
Quoted 2 lines
I just wondered if we can directly put 'struct
list_head' into 'structusb_hcd'.
maybe you can try it and send a patch (note: please wait until v4.17-rc2-ish because there are some fixes that will be applied by Greg after v4.17-rc1 is out, as well as the issues you noted below)? I believe it's not critical so there's plenty of time to get it into v4.18
Quoted 11 lines
drivers/usb/core/phy.h line 1
Quoted 7 lines
drivers/usb/core/phy.h new file +1
-0@@ -0,0 +1,7 @@ +struct usb_phy_roothub ;struct device;
is also needed for
usb_phy_roothub_init().
do you think that I should still fix this in 4.17?
Quoted 9 lines
drivers/usb/core/phy.h line 7
Quoted 5 lines
drivers/usb/core/phy.h new file +5
-0+struct usb_phy_roothub *usb_phy_roothub_init (struct device *dev); +int usb_phy_roothub_exit (struct usb_phy_roothub *phy_roothub); + +int usb_phy_roothub_power_on (struct usb_phy_roothub *phy_roothub); +void usb_phy_roothub_power_off (struct usb_phy_roothub *phy_roothub);Better to add an include guard?
SPDX-License-Identifier for this header too?
good catch - I'll send a patch for this too (along with the missing forward declaration for struct device)
Regards
Martin
PATCH v11 3/8 usb: core: add a wrapper for the USB PHYs on the HCD
2018-04-06 5:04 GMT+09:00 Martin Blumenstingl
<[email protected]>:
Quoted 145 lines
Hello,
(great to hear that this might be useful on Socionext SoCs as well :))
Quoted 139 lines · Masahiro Yamada
2018-03-04 6:43 GMT+09:00 Martin Blumenstingl
<[email protected]>:Quoted 121 lines
Many SoC platforms have separate devices for the USB PHY which are registered through the generic PHY framework. These PHYs have to be enabled to make the USB controller actually work. They also have to be disabled again on shutdown/suspend.
Currently (at least) the following HCI platform drivers are using custom code to obtain all PHYs via devicetree for the roothub/controller and disable/enable them when required:
-ehci-platform.chas ehci_platform_power_{on,off}
-xhci-mtk.chas xhci_mtk_phy_{init,exit,power_on,power_off}
-ohci-platform.chas ohci_platform_power_{on,off}With this new wrapper the USB PHYs can be specified directly in the USB controller's devicetree node (just like on the drivers listed above). This allows SoCs like the Amlogic Meson GXL family to operate correctly once this is wired up correctly. These SoCs use a dwc3 controller and require all USB PHYs to be initialized (if one of the USB PHYs it not initialized then none of USB port works at all).
Signed-off-by Martin Blumenstingl <[email protected]>Tested-by Yixun Lan <[email protected]>Cc Neil Armstrong <[email protected]>Cc Chunfeng Yun <[email protected]>--- drivers/usb/core/Makefile | 2 +- drivers/usb/core/phy.c | 158 ++++++++++++++++++++++++++++++++++++++++++++++ drivers/usb/core/phy.h | 7 ++ 3 files changed, 166 insertions(+), 1 deletion(-) create mode 100644 drivers/usb/core/phy.c create mode 100644 drivers/usb/core/phy.hdrivers/usb/core/Makefile +1
-1@@ -6,7 +6,7 @@ usbcore-y := usb.o hub.o hcd.o urb.o message.o driver.o usbcore-y += config.o file.o buffer.o sysfs.o endpoint.o usbcore-y += devio.o notify.o generic.o quirks.o devices.o -usbcore-y += port.o +usbcore-y += phy.o port.o usbcore-$(CONFIG_OF) += of.o usbcore-$(CONFIG_USB_PCI) += hcd-pci.odrivers/usb/core/phy.c new file +71
-0@@ -0,0 +1,158 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* +* A wrapper for multiple PHYs which passes all phy_* function calls to +* multiple (actual) PHY devices. This is comes handy when initializing +* all PHYs on a HCD and to keep them all in the same state. +* +* Copyright (C) 2018 Martin Blumenstingl <[email protected]> +*/ + +#include <linux/device.h> +#include <linux/list.h> +#include <linux/phy/phy.h> +#include <linux/of.h> + +#include "phy.h" + +struct usb_phy_roothub { +struct phy *phy; +struct list_head list; +}; + +static struct usb_phy_roothub *usb_phy_roothub_alloc (struct device *dev) +{ +struct usb_phy_roothub *roothub_entry; + + roothub_entry =devm_kzalloc (dev,sizeof (*roothub_entry),GFP_KERNEL ); +if (!roothub_entry) +return ERR_PTR (-ENOMEM ); + +INIT_LIST_HEAD (&roothub_entry->list); + +return roothub_entry; +} + +static int usb_phy_roothub_add_phy (struct device *dev,int index, +struct list_head *list) +{ +struct usb_phy_roothub *roothub_entry; +struct phy *phy =devm_of_phy_get_by_index (dev, dev->of_node, index); + +if (IS_ERR_OR_NULL (phy)) { +if (!phy ||PTR_ERR (phy) == -ENODEV ) +return 0 ; +else +return PTR_ERR (phy); + } + + roothub_entry =usb_phy_roothub_alloc (dev); +if (IS_ERR (roothub_entry)) +return PTR_ERR (roothub_entry); + + roothub_entry->phy = phy; + +list_add_tail (&roothub_entry->list, list); + +return 0 ; +} + +struct usb_phy_roothub *usb_phy_roothub_init (struct device *dev) +{ +struct usb_phy_roothub *phy_roothub; +struct usb_phy_roothub *roothub_entry; +struct list_head *head; +int i, num_phys, err; + + num_phys =of_count_phandle_with_args (dev->of_node,"phys" , +"#phy-cells" ); +if (num_phys <=0 ) +return NULL ; + + phy_roothub =usb_phy_roothub_alloc (dev);drivers/usb/core/phy.c line 81
Quoted 10 lines
drivers/usb/core/phy.c new file +10
-0+if (IS_ERR (phy_roothub)) +return phy_roothub; + +for (i =0 ; i < num_phys; i++) { + err =usb_phy_roothub_add_phy (dev, i, &phy_roothub->list); +if (err) + goto err_out; + } + + head = &phy_roothub->list;I think
phy_roothub->phyis always empty,
and onlyphy_roothub->listis used.
Quoted 6 lines
Quoted 2 lines
I just wondered if we can directly put 'struct
list_head' into 'structusb_hcd'.maybe you can try it and send a patch (note: please wait until v4.17-rc2-ish because there are some fixes that will be applied by Greg after v4.17-rc1 is out, as well as the issues you noted below)? I believe it's not critical so there's plenty of time to get it into v4.18
Oh, I was misunderstanding - I thought this patch series was under review. (Greg does not post patch-apply announce to ML.)
I see this in linux-next now.
When will this be available in Linus' tree? In the current MW?
Sure, I can send a patch after some flaws are ironed-out.
Signature · 2 lines
Best Regards Masahiro Yamada
Martin Blumenstingl
reviewerPATCH v11 3/8 usb: core: add a wrapper for the USB PHYs on the HCD
Quoted 154 lines · Masahiro Yamada
2018-04-06 5:04 GMT+09:00 Martin Blumenstingl
<[email protected]>:Quoted 145 lines
Hello,
(great to hear that this might be useful on Socionext SoCs as well :))
Quoted 139 lines · Masahiro Yamada
2018-03-04 6:43 GMT+09:00 Martin Blumenstingl
<[email protected]>:Quoted 121 lines
Many SoC platforms have separate devices for the USB PHY which are registered through the generic PHY framework. These PHYs have to be enabled to make the USB controller actually work. They also have to be disabled again on shutdown/suspend.
Currently (at least) the following HCI platform drivers are using custom code to obtain all PHYs via devicetree for the roothub/controller and disable/enable them when required:
-ehci-platform.chas ehci_platform_power_{on,off}
-xhci-mtk.chas xhci_mtk_phy_{init,exit,power_on,power_off}
-ohci-platform.chas ohci_platform_power_{on,off}With this new wrapper the USB PHYs can be specified directly in the USB controller's devicetree node (just like on the drivers listed above). This allows SoCs like the Amlogic Meson GXL family to operate correctly once this is wired up correctly. These SoCs use a dwc3 controller and require all USB PHYs to be initialized (if one of the USB PHYs it not initialized then none of USB port works at all).
Signed-off-by Martin Blumenstingl <[email protected]>Tested-by Yixun Lan <[email protected]>Cc Neil Armstrong <[email protected]>Cc Chunfeng Yun <[email protected]>--- drivers/usb/core/Makefile | 2 +- drivers/usb/core/phy.c | 158 ++++++++++++++++++++++++++++++++++++++++++++++ drivers/usb/core/phy.h | 7 ++ 3 files changed, 166 insertions(+), 1 deletion(-) create mode 100644 drivers/usb/core/phy.c create mode 100644 drivers/usb/core/phy.hdrivers/usb/core/Makefile +1
-1@@ -6,7 +6,7 @@ usbcore-y := usb.o hub.o hcd.o urb.o message.o driver.o usbcore-y += config.o file.o buffer.o sysfs.o endpoint.o usbcore-y += devio.o notify.o generic.o quirks.o devices.o -usbcore-y += port.o +usbcore-y += phy.o port.o usbcore-$(CONFIG_OF) += of.o usbcore-$(CONFIG_USB_PCI) += hcd-pci.odrivers/usb/core/phy.c new file +71
-0@@ -0,0 +1,158 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* +* A wrapper for multiple PHYs which passes all phy_* function calls to +* multiple (actual) PHY devices. This is comes handy when initializing +* all PHYs on a HCD and to keep them all in the same state. +* +* Copyright (C) 2018 Martin Blumenstingl <[email protected]> +*/ + +#include <linux/device.h> +#include <linux/list.h> +#include <linux/phy/phy.h> +#include <linux/of.h> + +#include "phy.h" + +struct usb_phy_roothub { +struct phy *phy; +struct list_head list; +}; + +static struct usb_phy_roothub *usb_phy_roothub_alloc (struct device *dev) +{ +struct usb_phy_roothub *roothub_entry; + + roothub_entry =devm_kzalloc (dev,sizeof (*roothub_entry),GFP_KERNEL ); +if (!roothub_entry) +return ERR_PTR (-ENOMEM ); + +INIT_LIST_HEAD (&roothub_entry->list); + +return roothub_entry; +} + +static int usb_phy_roothub_add_phy (struct device *dev,int index, +struct list_head *list) +{ +struct usb_phy_roothub *roothub_entry; +struct phy *phy =devm_of_phy_get_by_index (dev, dev->of_node, index); + +if (IS_ERR_OR_NULL (phy)) { +if (!phy ||PTR_ERR (phy) == -ENODEV ) +return 0 ; +else +return PTR_ERR (phy); + } + + roothub_entry =usb_phy_roothub_alloc (dev); +if (IS_ERR (roothub_entry)) +return PTR_ERR (roothub_entry); + + roothub_entry->phy = phy; + +list_add_tail (&roothub_entry->list, list); + +return 0 ; +} + +struct usb_phy_roothub *usb_phy_roothub_init (struct device *dev) +{ +struct usb_phy_roothub *phy_roothub; +struct usb_phy_roothub *roothub_entry; +struct list_head *head; +int i, num_phys, err; + + num_phys =of_count_phandle_with_args (dev->of_node,"phys" , +"#phy-cells" ); +if (num_phys <=0 ) +return NULL ; + + phy_roothub =usb_phy_roothub_alloc (dev);drivers/usb/core/phy.c line 81
Quoted 10 lines
drivers/usb/core/phy.c new file +10
-0+if (IS_ERR (phy_roothub)) +return phy_roothub; + +for (i =0 ; i < num_phys; i++) { + err =usb_phy_roothub_add_phy (dev, i, &phy_roothub->list); +if (err) + goto err_out; + } + + head = &phy_roothub->list;I think
phy_roothub->phyis always empty,
and onlyphy_roothub->listis used.Quoted 6 lines
Quoted 2 lines
I just wondered if we can directly put 'struct
list_head' into 'structusb_hcd'.maybe you can try it and send a patch (note: please wait until v4.17-rc2-ish because there are some fixes that will be applied by Greg after v4.17-rc1 is out, as well as the issues you noted below)? I believe it's not critical so there's plenty of time to get it into v4.18
Quoted 6 lines
Oh, I was misunderstanding - I thought this patch series was under review. (Greg does not post patch-apply announce to ML.)
I see this in linux-next now.
When will this be available in Linus' tree? In the current MW?
this is already available in Linus' tree. the commit for this specific patch (#3) is known as 07dbff0ddbd86c
Quoted 1 line
Sure, I can send a patch after some flaws are ironed-out.
great, thank you!
could you also let me know once you have tested this on one of your SoCs?
Regards
Martin
PATCH v11 3/8 usb: core: add a wrapper for the USB PHYs on the HCD
2018-04-06 14:15 GMT+09:00 Martin Blumenstingl
<[email protected]>:
Quoted 4 lines
Quoted 2 lines
When will this be available in Linus' tree? In the current MW?
this is already available in Linus' tree. the commit for this specific patch (#3) is known as
07dbff0ddbd86c
Oh, great! Thank you.
Quoted 3 lines
Quoted 1 line
Sure, I can send a patch after some flaws are ironed-out.
great, thank you!
could you also let me know once you have tested this on one of your SoCs?
I will.
Signature · 2 lines
Best Regards Masahiro Yamada
Martin Blumenstingl
reviewerPATCH v11 4/8 usb: core: hcd: integrate the PHY wrapper into the HCD core
In reply to Martin BlumenstinglThis integrates the PHY wrapper into the core hcd infrastructure. Multiple PHYs which are part of the HCD's device tree node are now managed (= powered on/off when needed), by the new usb_phy_roothub code.
Suspend and resume is also supported, however not for runtime/auto-suspend (which is triggered for example when no devices are connected to the USB bus). This is needed on some SoCs (for example Amlogic Meson GXL) because if the PHYs are disabled during auto-suspend then devices which are plugged in afterwards are not seen by the host.
One example where this is required is the Amlogic GXL and GXM SoCs:
They are using a dwc3 USB controller with up to three ports enabled on the internal roothub. Each port has it's own PHY which must be enabled (if one of the PHYs is left disabled then none of the USB ports works at all).
The new logic works on the Amlogic GXL and GXM SoCs because the dwc3 driver internally creates a xhci-hcd which then registers a HCD which then triggers our new PHY wrapper.
USB controller drivers can opt out of this by setting "skip_phy_initialization" in struct usb_hcd to true. This is identical to how it works for a single USB PHY, so the "multiple PHY" handling is disabled for drivers that opted out of the management logic of a single PHY.
--- drivers/usb/core/hcd.c | 31 +++++++++++++++++++++++++++++++ include/linux/usb/hcd.h | 1 + 2 files changed, 32 insertions(+)
drivers/usb/core/hcd.c +31 -0
@@ -37,6 +37,7 @@#include <linux/usb/otg.h> #include "usb.h" +#include "phy.h" /*-------------------------------------------------------------------------*/
@@ -2260,6 +2261,9 @@ int hcd_bus_suspend(struct usb_device *rhdev, pm_message_t msg)usb_set_device_state (rhdev,USB_STATE_SUSPENDED ); hcd->state =HC_STATE_SUSPENDED ; +if (!PMSG_IS_AUTO (msg)) +usb_phy_roothub_power_off (hcd->phy_roothub); +/* Did we race with a root-hub wakeup event? */ if (rhdev->do_remote_wakeup) {char buffer[6 ];
@@ -2296,6 +2300,13 @@ int hcd_bus_resume(struct usb_device *rhdev, pm_message_t msg)dev_dbg (&rhdev->dev,"skipped %s of dead bus\n" ,"resume" );return 0 ; } + +if (!PMSG_IS_AUTO (msg)) { + status =usb_phy_roothub_power_on (hcd->phy_roothub); +if (status) +return status; + } +if (!hcd->driver->bus_resume)return -ENOENT ;if (HCD_RH_RUNNING (hcd))
@@ -2333,6 +2344,7 @@ int hcd_bus_resume(struct usb_device *rhdev, pm_message_t msg) } }else { hcd->state = old_state; +usb_phy_roothub_power_off (hcd->phy_roothub);dev_dbg (&rhdev->dev,"bus %s fail, err %d\n" ,"resume" , status);if (status != -ESHUTDOWN )
@@ -2769,6 +2781,18 @@ int usb_add_hcd(struct usb_hcd *hcd, } } +if (!hcd->skip_phy_initialization) { + hcd->phy_roothub =usb_phy_roothub_init (hcd->self.sysdev); +if (IS_ERR (hcd->phy_roothub)) { + retval =PTR_ERR (hcd->phy_roothub); + goto err_phy_roothub_init; + } + + retval =usb_phy_roothub_power_on (hcd->phy_roothub); +if (retval) + goto err_usb_phy_roothub_power_on; + } +dev_info (hcd->self.controller,"%s\n" , hcd->product_desc);/* Keep old behaviour if authorized_default is not in [0, 1]. */
@@ -2933,6 +2957,10 @@ int usb_add_hcd(struct usb_hcd *hcd, err_register_bus:hcd_buffer_destroy (hcd); err_create_buf: +usb_phy_roothub_power_off (hcd->phy_roothub); +err_usb_phy_roothub_power_on: +usb_phy_roothub_exit (hcd->phy_roothub); +err_phy_roothub_init:if (IS_ENABLED (CONFIG_GENERIC_PHY ) && hcd->remove_phy && hcd->phy) {phy_power_off (hcd->phy);phy_exit (hcd->phy);
@@ -3017,6 +3045,9 @@ void usb_remove_hcd(struct usb_hcd *hcd)usb_deregister_bus (&hcd->self);hcd_buffer_destroy (hcd); +usb_phy_roothub_power_off (hcd->phy_roothub); +usb_phy_roothub_exit (hcd->phy_roothub); +if (IS_ENABLED (CONFIG_GENERIC_PHY ) && hcd->remove_phy && hcd->phy) {phy_power_off (hcd->phy);phy_exit (hcd->phy);
include/linux/usb/hcd.h +1 -0
@@ -104,6 +104,7 @@ struct usb_hcd {*/ struct usb_phy *usb_phy;struct phy *phy; +struct usb_phy_roothub *phy_roothub;/* Flags that need to be manipulated atomically because they can * change while the host controller is running. Always use
Signature · 1 line
2.16.2
Martin Blumenstingl
reviewerPATCH v11 5/8 usb: host: xhci-mtk: remove custom USB PHY handling
In reply to Martin BlumenstinglThe new PHY wrapper is now wired up in the core HCD code. This means that PHYs are now controlled (initialized, enabled, disabled, exited) without requiring any host-driver specific code.
Remove the custom USB PHY handling from the xhci-mtk driver as the core HCD code now handles this.
--- drivers/usb/host/xhci-mtk.c | 98 +-------------------------------------------- 1 file changed, 2 insertions(+), 96 deletions(-)
drivers/usb/host/xhci-mtk.c +2 -96
@@ -14,7 +14,6 @@#include <linux/mfd/syscon.h> #include <linux/module.h> #include <linux/of.h> -#include <linux/phy/phy.h> #include <linux/platform_device.h> #include <linux/pm_runtime.h> #include <linux/regmap.h>
@@ -352,62 +351,6 @@ static const struct xhci_driver_overrides xhci_mtk_overrides __initconst = {static struct hc_driver __read_mostly xhci_mtk_hc_driver; -static int xhci_mtk_phy_init (struct xhci_hcd_mtk *mtk) -{ -int i; -int ret; - -for (i =0 ; i < mtk->num_phys; i++) { - ret =phy_init (mtk->phys[i]); -if (ret) - goto exit_phy; - } -return 0 ; - -exit_phy: -for (; i >0 ; i--) -phy_exit (mtk->phys[i -1 ]); - -return ret; -} - -static int xhci_mtk_phy_exit (struct xhci_hcd_mtk *mtk) -{ -int i; - -for (i =0 ; i < mtk->num_phys; i++) -phy_exit (mtk->phys[i]); - -return 0 ; -} - -static int xhci_mtk_phy_power_on (struct xhci_hcd_mtk *mtk) -{ -int i; -int ret; - -for (i =0 ; i < mtk->num_phys; i++) { - ret =phy_power_on (mtk->phys[i]); -if (ret) - goto power_off_phy; - } -return 0 ; - -power_off_phy: -for (; i >0 ; i--) -phy_power_off (mtk->phys[i -1 ]); - -return ret; -} - -static void xhci_mtk_phy_power_off (struct xhci_hcd_mtk *mtk) -{ -unsigned int i; - -for (i =0 ; i < mtk->num_phys; i++) -phy_power_off (mtk->phys[i]); -} -static int xhci_mtk_ldos_enable (struct xhci_hcd_mtk *mtk) {int ret;
@@ -488,8 +431,6 @@ static int xhci_mtk_probe(struct platform_device *pdev)struct xhci_hcd *xhci;struct resource *res;struct usb_hcd *hcd; -struct phy *phy; -int phy_num;int ret = -ENODEV ;int irq;
@@ -529,16 +470,6 @@ static int xhci_mtk_probe(struct platform_device *pdev)return ret; } - mtk->num_phys =of_count_phandle_with_args (node, -"phys" ,"#phy-cells" ); -if (mtk->num_phys >0 ) { - mtk->phys =devm_kcalloc (dev, mtk->num_phys, -sizeof (*mtk->phys),GFP_KERNEL ); -if (!mtk->phys) -return -ENOMEM ; - }else { - mtk->num_phys =0 ; - }pm_runtime_enable (dev);pm_runtime_get_sync (dev);device_enable_async_suspend (dev);
@@ -596,23 +527,6 @@ static int xhci_mtk_probe(struct platform_device *pdev) mtk->has_ippc = false; } -for (phy_num =0 ; phy_num < mtk->num_phys; phy_num++) { - phy =devm_of_phy_get_by_index (dev, node, phy_num); -if (IS_ERR (phy)) { - ret =PTR_ERR (phy); - goto put_usb2_hcd; - } - mtk->phys[phy_num] = phy; - } - - ret =xhci_mtk_phy_init (mtk); -if (ret) - goto put_usb2_hcd; - - ret =xhci_mtk_phy_power_on (mtk); -if (ret) - goto exit_phys; -device_init_wakeup (dev, true); xhci =hcd_to_xhci (hcd);
@@ -630,7 +544,7 @@ static int xhci_mtk_probe(struct platform_device *pdev) dev_name(dev), hcd);if (!xhci->shared_hcd) { ret = -ENOMEM ; - goto power_off_phys; + goto disable_device_wakeup; } ret =usb_add_hcd (hcd, irq,IRQF_SHARED );
@@ -653,13 +567,9 @@ static int xhci_mtk_probe(struct platform_device *pdev)xhci_mtk_sch_exit (mtk);usb_put_hcd (xhci->shared_hcd); -power_off_phys: -xhci_mtk_phy_power_off (mtk); +disable_device_wakeup:device_init_wakeup (dev, false); -exit_phys: -xhci_mtk_phy_exit (mtk); - put_usb2_hcd:usb_put_hcd (hcd);
@@ -682,8 +592,6 @@ static int xhci_mtk_remove(struct platform_device *dev)struct xhci_hcd *xhci =hcd_to_xhci (hcd);usb_remove_hcd (xhci->shared_hcd); -xhci_mtk_phy_power_off (mtk); -xhci_mtk_phy_exit (mtk);device_init_wakeup (&dev->dev, false);usb_remove_hcd (hcd);
@@ -718,7 +626,6 @@ static int __maybe_unused xhci_mtk_suspend(struct device *dev)del_timer_sync (&xhci->shared_hcd->rh_timer);xhci_mtk_host_disable (mtk); -xhci_mtk_phy_power_off (mtk);xhci_mtk_clks_disable (mtk);usb_wakeup_set (mtk, true);return 0 ;
@@ -732,7 +639,6 @@ static int __maybe_unused xhci_mtk_resume(struct device *dev)usb_wakeup_set (mtk, false);xhci_mtk_clks_enable (mtk); -xhci_mtk_phy_power_on (mtk);xhci_mtk_host_enable (mtk);xhci_dbg (xhci,"%s: restart port polling\n" , __func__);
Signature · 1 line
2.16.2
PATCH v11 5/8 usb: host: xhci-mtk: remove custom USB PHY handling
Hi, Martin
I've tested the series with U2 storage and U3 ethernet devices on both boards MT7623 BPI-R2 and MT7622 RFB1 using xhci-mtk driver, they are still working well.
Below is related logs for test devices probing
----
# [ 42.590356] usb 2-1: new SuperSpeed USB device number 2 using
xhci-mtk
[ 42.719883] usb-storage 2-1:1.0: USB Mass Storage device detected [ 42.726339] scsi host2: usb-storage 2-1:1.0 [ 43.815572] scsi 2:0:0:0: Direct-Access Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6 [ 44.792938] sd 2:0:0:0: [sda] 30728832 512-byte logical blocks: (15.7 GB/14.7 GiB) [ 44.800658] sd 2:0:0:0: [sda] Write Protect is off [ 44.805582] sd 2:0:0:0: [sda] No Caching mode page found [ 44.810888] sd 2:0:0:0: [sda] Assuming drive cache: write through
----
# [ 134.270617] usb 2-1: new SuperSpeed USB device number 3 using xhci-mtk
[ 134.664163] ax88179_178a 2-1:1.0 eth1: register 'ax88179_178a' at
usb-1a1c0000.usb-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:11:6b:68:4c:9e
Quoted 185 lines · Martin Blumenstingl
The new PHY wrapper is now wired up in the core HCD code. This means that PHYs are now controlled (initialized, enabled, disabled, exited) without requiring any host-driver specific code.
Remove the custom USB PHY handling from the xhci-mtk driver as the core HCD code now handles this.Signed-off-by Martin Blumenstingl <[email protected]>--- drivers/usb/host/xhci-mtk.c | 98 +-------------------------------------------- 1 file changed, 2 insertions(+), 96 deletions(-)drivers/usb/host/xhci-mtk.c +2
-96@@ -14,7 +14,6 @@#include <linux/mfd/syscon.h> #include <linux/module.h> #include <linux/of.h> -#include <linux/phy/phy.h> #include <linux/platform_device.h> #include <linux/pm_runtime.h> #include <linux/regmap.h> @@ -352,62 +351,6 @@ static const struct xhci_driver_overrides xhci_mtk_overrides __initconst = {static struct hc_driver __read_mostly xhci_mtk_hc_driver; -static int xhci_mtk_phy_init (struct xhci_hcd_mtk *mtk) -{ -int i; -int ret; - -for (i =0 ; i < mtk->num_phys; i++) { - ret =phy_init (mtk->phys[i]); -if (ret) - goto exit_phy; - } -return 0 ; - -exit_phy: -for (; i >0 ; i--) -phy_exit (mtk->phys[i -1 ]); - -return ret; -} - -static int xhci_mtk_phy_exit (struct xhci_hcd_mtk *mtk) -{ -int i; - -for (i =0 ; i < mtk->num_phys; i++) -phy_exit (mtk->phys[i]); - -return 0 ; -} - -static int xhci_mtk_phy_power_on (struct xhci_hcd_mtk *mtk) -{ -int i; -int ret; - -for (i =0 ; i < mtk->num_phys; i++) { - ret =phy_power_on (mtk->phys[i]); -if (ret) - goto power_off_phy; - } -return 0 ; - -power_off_phy: -for (; i >0 ; i--) -phy_power_off (mtk->phys[i -1 ]); - -return ret; -} - -static void xhci_mtk_phy_power_off (struct xhci_hcd_mtk *mtk) -{ -unsigned int i; - -for (i =0 ; i < mtk->num_phys; i++) -phy_power_off (mtk->phys[i]); -} -static int xhci_mtk_ldos_enable (struct xhci_hcd_mtk *mtk) {int ret;@@ -488,8 +431,6 @@ static int xhci_mtk_probe(struct platform_device *pdev)struct xhci_hcd *xhci;struct resource *res;struct usb_hcd *hcd; -struct phy *phy; -int phy_num;int ret = -ENODEV ;int irq;@@ -529,16 +470,6 @@ static int xhci_mtk_probe(struct platform_device *pdev)return ret; } - mtk->num_phys =of_count_phandle_with_args (node, -"phys" ,"#phy-cells" ); -if (mtk->num_phys >0 ) { - mtk->phys =devm_kcalloc (dev, mtk->num_phys, -sizeof (*mtk->phys),GFP_KERNEL ); -if (!mtk->phys) -return -ENOMEM ; - }else { - mtk->num_phys =0 ; - }pm_runtime_enable (dev);pm_runtime_get_sync (dev);device_enable_async_suspend (dev);@@ -596,23 +527,6 @@ static int xhci_mtk_probe(struct platform_device *pdev) mtk->has_ippc = false; } -for (phy_num =0 ; phy_num < mtk->num_phys; phy_num++) { - phy =devm_of_phy_get_by_index (dev, node, phy_num); -if (IS_ERR (phy)) { - ret =PTR_ERR (phy); - goto put_usb2_hcd; - } - mtk->phys[phy_num] = phy; - } - - ret =xhci_mtk_phy_init (mtk); -if (ret) - goto put_usb2_hcd; - - ret =xhci_mtk_phy_power_on (mtk); -if (ret) - goto exit_phys; -device_init_wakeup (dev, true); xhci =hcd_to_xhci (hcd);@@ -630,7 +544,7 @@ static int xhci_mtk_probe(struct platform_device *pdev) dev_name(dev), hcd);if (!xhci->shared_hcd) { ret = -ENOMEM ; - goto power_off_phys; + goto disable_device_wakeup; } ret =usb_add_hcd (hcd, irq,IRQF_SHARED );@@ -653,13 +567,9 @@ static int xhci_mtk_probe(struct platform_device *pdev)xhci_mtk_sch_exit (mtk);usb_put_hcd (xhci->shared_hcd); -power_off_phys: -xhci_mtk_phy_power_off (mtk); +disable_device_wakeup:device_init_wakeup (dev, false); -exit_phys: -xhci_mtk_phy_exit (mtk); - put_usb2_hcd:usb_put_hcd (hcd);@@ -682,8 +592,6 @@ static int xhci_mtk_remove(struct platform_device *dev)struct xhci_hcd *xhci =hcd_to_xhci (hcd);usb_remove_hcd (xhci->shared_hcd); -xhci_mtk_phy_power_off (mtk); -xhci_mtk_phy_exit (mtk);device_init_wakeup (&dev->dev, false);usb_remove_hcd (hcd);@@ -718,7 +626,6 @@ static int __maybe_unused xhci_mtk_suspend(struct device *dev)del_timer_sync (&xhci->shared_hcd->rh_timer);xhci_mtk_host_disable (mtk); -xhci_mtk_phy_power_off (mtk);xhci_mtk_clks_disable (mtk);usb_wakeup_set (mtk, true);return 0 ;@@ -732,7 +639,6 @@ static int __maybe_unused xhci_mtk_resume(struct device *dev)usb_wakeup_set (mtk, false);xhci_mtk_clks_enable (mtk); -xhci_mtk_phy_power_on (mtk);xhci_mtk_host_enable (mtk);xhci_dbg (xhci,"%s: restart port polling\n" , __func__);
Martin Blumenstingl
reviewerPATCH v11 6/8 usb: host: ehci-platform: remove custom USB PHY handling
In reply to Martin BlumenstinglThe new PHY wrapper is now wired up in the core HCD code. This means that PHYs are now controlled (initialized, enabled, disabled, exited) without requiring any host-driver specific code.
Remove the custom USB PHY handling from the ehci-platform driver as the core HCD code now handles this.
--- drivers/usb/host/ehci-platform.c | 55 +++------------------------------------- 1 file changed, 4 insertions(+), 51 deletions(-)
drivers/usb/host/ehci-platform.c +4 -51
@@ -27,7 +27,6 @@#include <linux/io.h> #include <linux/module.h> #include <linux/of.h> -#include <linux/phy/phy.h> #include <linux/platform_device.h> #include <linux/reset.h> #include <linux/usb.h>
@@ -44,8 +43,6 @@struct ehci_platform_priv {struct clk *clks[EHCI_MAX_CLKS ];struct reset_control *rsts; -struct phy **phys; -int num_phys;bool reset_on_resume; };
@@ -80,7 +77,7 @@ static int ehci_platform_power_on(struct platform_device *dev) {struct usb_hcd *hcd =platform_get_drvdata (dev);struct ehci_platform_priv *priv =hcd_to_ehci_priv (hcd); -int clk, ret, phy_num; +int clk, ret;for (clk =0 ; clk <EHCI_MAX_CLKS && priv->clks[clk]; clk++) { ret =clk_prepare_enable (priv->clks[clk]);
@@ -88,24 +85,8 @@ static int ehci_platform_power_on(struct platform_device *dev) goto err_disable_clks; } -for (phy_num =0 ; phy_num < priv->num_phys; phy_num++) { - ret =phy_init (priv->phys[phy_num]); -if (ret) - goto err_exit_phy; - ret =phy_power_on (priv->phys[phy_num]); -if (ret) { -phy_exit (priv->phys[phy_num]); - goto err_exit_phy; - } - } -return 0 ; -err_exit_phy: -while (--phy_num >=0 ) { -phy_power_off (priv->phys[phy_num]); -phy_exit (priv->phys[phy_num]); - } err_disable_clks:while (--clk >=0 )clk_disable_unprepare (priv->clks[clk]);
@@ -117,12 +98,7 @@ static void ehci_platform_power_off(struct platform_device *dev) {struct usb_hcd *hcd =platform_get_drvdata (dev);struct ehci_platform_priv *priv =hcd_to_ehci_priv (hcd); -int clk, phy_num; - -for (phy_num =0 ; phy_num < priv->num_phys; phy_num++) { -phy_power_off (priv->phys[phy_num]); -phy_exit (priv->phys[phy_num]); - } +int clk;for (clk =EHCI_MAX_CLKS -1 ; clk >=0 ; clk--)if (priv->clks[clk])
@@ -149,7 +125,7 @@ static int ehci_platform_probe(struct platform_device *dev)struct usb_ehci_pdata *pdata =dev_get_platdata (&dev->dev);struct ehci_platform_priv *priv;struct ehci_hcd *ehci; -int err, irq, phy_num, clk =0 ; +int err, irq, clk =0 ;if (usb_disabled ())return -ENODEV ;
@@ -202,29 +178,6 @@ static int ehci_platform_probe(struct platform_device *dev) "has-transaction-translator")) hcd->has_tt =1 ; - priv->num_phys =of_count_phandle_with_args (dev->dev.of_node, -"phys" ,"#phy-cells" ); - -if (priv->num_phys >0 ) { - priv->phys =devm_kcalloc (&dev->dev, priv->num_phys, -sizeof (struct phy *),GFP_KERNEL ); -if (!priv->phys) -return -ENOMEM ; - }else - priv->num_phys =0 ; - -for (phy_num =0 ; phy_num < priv->num_phys; phy_num++) { - priv->phys[phy_num] =devm_of_phy_get_by_index ( - &dev->dev, dev->dev.of_node, phy_num); -if (IS_ERR (priv->phys[phy_num])) { - err =PTR_ERR (priv->phys[phy_num]); - goto err_put_hcd; - }else { -/* Avoiding phy_get() in usb_add_hcd() */ - hcd->skip_phy_initialization =1 ; - } - } -for (clk =0 ; clk <EHCI_MAX_CLKS ; clk++) { priv->clks[clk] =of_clk_get (dev->dev.of_node, clk);if (IS_ERR (priv->clks[clk])) {
@@ -306,7 +259,7 @@ static int ehci_platform_probe(struct platform_device *dev) err_put_clks:while (--clk >=0 )clk_put (priv->clks[clk]); -err_put_hcd: +if (pdata == &ehci_platform_defaults) dev->dev.platform_data =NULL ;
Signature · 1 line
2.16.2
Martin Blumenstingl
reviewerPATCH v11 7/8 usb: host: ohci-platform: remove custom USB PHY handling
In reply to Martin BlumenstinglThe new PHY wrapper is now wired up in the core HCD code. This means that PHYs are now controlled (initialized, enabled, disabled, exited) without requiring any host-driver specific code.
Remove the custom USB PHY handling from the ohci-platform driver as the core HCD code now handles this.
--- drivers/usb/host/ohci-platform.c | 56 ++++------------------------------------ 1 file changed, 5 insertions(+), 51 deletions(-)
drivers/usb/host/ohci-platform.c +5 -51
@@ -21,7 +21,7 @@#include <linux/kernel.h> #include <linux/module.h> #include <linux/err.h> -#include <linux/phy/phy.h> +#include <linux/of.h> #include <linux/platform_device.h> #include <linux/pm_runtime.h> #include <linux/reset.h>
@@ -38,8 +38,6 @@struct ohci_platform_priv {struct clk *clks[OHCI_MAX_CLKS ];struct reset_control *resets; -struct phy **phys; -int num_phys; };static const char hcd_name[] ="ohci-platform" ;
@@ -48,7 +46,7 @@ static int ohci_platform_power_on(struct platform_device *dev) {struct usb_hcd *hcd =platform_get_drvdata (dev);struct ohci_platform_priv *priv =hcd_to_ohci_priv (hcd); -int clk, ret, phy_num; +int clk, ret;for (clk =0 ; clk <OHCI_MAX_CLKS && priv->clks[clk]; clk++) { ret =clk_prepare_enable (priv->clks[clk]);
@@ -56,24 +54,8 @@ static int ohci_platform_power_on(struct platform_device *dev) goto err_disable_clks; } -for (phy_num =0 ; phy_num < priv->num_phys; phy_num++) { - ret =phy_init (priv->phys[phy_num]); -if (ret) - goto err_exit_phy; - ret =phy_power_on (priv->phys[phy_num]); -if (ret) { -phy_exit (priv->phys[phy_num]); - goto err_exit_phy; - } - } -return 0 ; -err_exit_phy: -while (--phy_num >=0 ) { -phy_power_off (priv->phys[phy_num]); -phy_exit (priv->phys[phy_num]); - } err_disable_clks:while (--clk >=0 )clk_disable_unprepare (priv->clks[clk]);
@@ -85,12 +67,7 @@ static void ohci_platform_power_off(struct platform_device *dev) {struct usb_hcd *hcd =platform_get_drvdata (dev);struct ohci_platform_priv *priv =hcd_to_ohci_priv (hcd); -int clk, phy_num; - -for (phy_num =0 ; phy_num < priv->num_phys; phy_num++) { -phy_power_off (priv->phys[phy_num]); -phy_exit (priv->phys[phy_num]); - } +int clk;for (clk =OHCI_MAX_CLKS -1 ; clk >=0 ; clk--)if (priv->clks[clk])
@@ -117,7 +94,7 @@ static int ohci_platform_probe(struct platform_device *dev)struct usb_ohci_pdata *pdata =dev_get_platdata (&dev->dev);struct ohci_platform_priv *priv;struct ohci_hcd *ohci; -int err, irq, phy_num, clk =0 ; +int err, irq, clk =0 ;if (usb_disabled ())return -ENODEV ;
@@ -169,29 +146,6 @@ static int ohci_platform_probe(struct platform_device *dev)of_property_read_u32 (dev->dev.of_node,"num-ports" , &ohci->num_ports); - priv->num_phys =of_count_phandle_with_args (dev->dev.of_node, -"phys" ,"#phy-cells" ); - -if (priv->num_phys >0 ) { - priv->phys =devm_kcalloc (&dev->dev, priv->num_phys, -sizeof (struct phy *),GFP_KERNEL ); -if (!priv->phys) -return -ENOMEM ; - }else - priv->num_phys =0 ; - -for (phy_num =0 ; phy_num < priv->num_phys; phy_num++) { - priv->phys[phy_num] =devm_of_phy_get_by_index ( - &dev->dev, dev->dev.of_node, phy_num); -if (IS_ERR (priv->phys[phy_num])) { - err =PTR_ERR (priv->phys[phy_num]); - goto err_put_hcd; - }else { -/* Avoiding phy_get() in usb_add_hcd() */ - hcd->skip_phy_initialization =1 ; - } - } -for (clk =0 ; clk <OHCI_MAX_CLKS ; clk++) { priv->clks[clk] =of_clk_get (dev->dev.of_node, clk);if (IS_ERR (priv->clks[clk])) {
@@ -277,7 +231,7 @@ static int ohci_platform_probe(struct platform_device *dev) err_put_clks:while (--clk >=0 )clk_put (priv->clks[clk]); -err_put_hcd: +if (pdata == &ohci_platform_defaults) dev->dev.platform_data =NULL ;
Signature · 1 line
2.16.2
Martin Blumenstingl
reviewerPATCH v11 8/8 usb: core: hcd: remove support for initializing a single PHY
In reply to Martin BlumenstinglWith the new PHY wrapper in place we can now handle multiple PHYs. Remove the code which handles only one generic PHY as this is now covered (with support for multiple PHYs as well as suspend/resume support) by the new PHY wrapper.
--- drivers/usb/core/hcd.c | 37 ------------------------------------- include/linux/usb/hcd.h | 1 - 2 files changed, 38 deletions(-)
drivers/usb/core/hcd.c +0 -37
@@ -2757,30 +2757,6 @@ int usb_add_hcd(struct usb_hcd *hcd, } } -if (IS_ENABLED (CONFIG_GENERIC_PHY ) && !hcd->skip_phy_initialization) { -struct phy *phy =phy_get (hcd->self.sysdev,"usb" ); - -if (IS_ERR (phy)) { - retval =PTR_ERR (phy); -if (retval == -EPROBE_DEFER ) - goto err_phy; - }else { - retval =phy_init (phy); -if (retval) { -phy_put (phy); - goto err_phy; - } - retval =phy_power_on (phy); -if (retval) { -phy_exit (phy); -phy_put (phy); - goto err_phy; - } - hcd->phy = phy; - hcd->remove_phy =1 ; - } - } -if (!hcd->skip_phy_initialization) { hcd->phy_roothub =usb_phy_roothub_init (hcd->self.sysdev);if (IS_ERR (hcd->phy_roothub)) {
@@ -2961,13 +2937,6 @@ int usb_add_hcd(struct usb_hcd *hcd, err_usb_phy_roothub_power_on:usb_phy_roothub_exit (hcd->phy_roothub); err_phy_roothub_init: -if (IS_ENABLED (CONFIG_GENERIC_PHY ) && hcd->remove_phy && hcd->phy) { -phy_power_off (hcd->phy); -phy_exit (hcd->phy); -phy_put (hcd->phy); - hcd->phy =NULL ; - } -err_phy:if (hcd->remove_phy && hcd->usb_phy) {usb_phy_shutdown (hcd->usb_phy);usb_put_phy (hcd->usb_phy);
@@ -3048,12 +3017,6 @@ void usb_remove_hcd(struct usb_hcd *hcd)usb_phy_roothub_power_off (hcd->phy_roothub);usb_phy_roothub_exit (hcd->phy_roothub); -if (IS_ENABLED (CONFIG_GENERIC_PHY ) && hcd->remove_phy && hcd->phy) { -phy_power_off (hcd->phy); -phy_exit (hcd->phy); -phy_put (hcd->phy); - hcd->phy =NULL ; - }if (hcd->remove_phy && hcd->usb_phy) {usb_phy_shutdown (hcd->usb_phy);usb_put_phy (hcd->usb_phy);
include/linux/usb/hcd.h +0 -1
@@ -103,7 +103,6 @@ struct usb_hcd {* other external phys should be software-transparent */ struct usb_phy *usb_phy; -struct phy *phy;struct usb_phy_roothub *phy_roothub;/* Flags that need to be manipulated atomically because they can
Signature · 1 line
2.16.2
v11 cover initialize (multiple) PHYs for a HCD
In reply to Martin BlumenstinglQuoted 208 lines · Martin Blumenstingl
The goal of this series is to initialize multiple PHYs on a USB host controller, which is needed on Amlogic Meson GXL and GXM SoCs.
- Amlogic Meson GXL and GXM SoCs come with a dwc3 IP block which has two or three USB2 ports enabled on the internal root-hub. The SoCs also provide separate USB2 PHYs, one per port. All USB2 PHYs (which are internally "connected" to the dwc3 roothub) need to be powered on, otherwise USB devices cannot be enumerated (even if just one PHY is disabled and if the device is plugged into another, enabled port)
- dwc3 already takes one USB2 and one USB3 PHY and initializes these correctly
- some other HCI platform drivers (likeehci-platform.c,xhci-mtk.candohci-platform.c) do not have a limitation on the number of PHYs - they support any number of USB PHYs (typically one PHY per actual port)This series adds a new "PHY wrapper". This can be configured through devicetree by passing a "phys" property (with any number of PHY handles) to the USB controller.
Additionally it this integrates this new PHY wrapper intohcd.cwhich automatically enables it for all USB controller drivers (tested on an Amlogic Meson GXL SoC which uses a dwc3 controller). Since this leaves some duplicate code (which now becomes obsolete!) in various drivers this is being cleaned up as well.Changes since v10 at [13]:
- added Peter Chen's Acked-by to patch #2 (thank you!)
- rebased to usb-next (134d1fd44221614"Merge 4.16-rc3 into usb-next")Changes since v9 at [12]:
- changed "skip_phy_initialization" from PATCH #2 into a bitfield and moved it below the "remove_phy" bitfield as suggested by Alan Stern (thanks!)
- rebased against usb-next (which is currently identical to v4.16-rc1)Changes since v8 at [10]:
- add new patch #2 which allows disabling "USB PHY management" in the USB HCD core driver. this also affects patch #4 which now checks theskip_phy_initializationflag before calling usb_phy_roothub_{init,power_on} (other functions don't need to be guarded since they are null-safe - see patch #3)
- integrated my other series 'remove driver-specific "multiple PHY" handling' from [11] into this one so the result of this "generic" code (= removing duplicate code in various drivers) can be seen directly. affects patches #5-8. (note: patch #1 "usb: mtu3: remove custom USB PHY handling" from that series was dropped, because it broke device mode support - Chunfeng Yun will come up with a separate patch later. patch #5 "usb: chipidea: do not set the "phy" field in structusb_hcd" from that series was rewritten and is now integrated into the new patch #2 from this series)
- collected all {Reviewed,Tested,Acked}-by
- dropped RfC prefix since this v8 was out for review for two weeks and it only got Reviewed-by's and Tested-by's since thenChanges since v7 at [8]:
- updated the description in the cover-letter
- wrapped the only call usb_phy_roothub_power_{on,off} in hcd_bus_{resume,suspend} during system-suspend (excluding it from being called during runtime/auto suspend). this also fixes a problem on Meson GXL which does not detect that a new device has been connected if the PHYs are powered off. Thanks to Manu Gautam for suggesting this! (affects patch #3)
- after a discussion about the dt-bindings of this patch I went back to simply specifying a "phys" property (without a corresponding phy-names property) to pass all PHYs directly in the node of the USB controller. From my understanding the root hub node was "artificial" and we should describe it's properties as part of the controller, rather than introducing a sub-node. see also the discussion with Arnd in [9] (this affects patch #1 and #2)
- dropped patch #4 ("dt-bindings: usb: xhci: include the roothub and a device in the example") because we're back to just specifying a "phys" property directly within the controller.
NOTE: some HCI platform drivers are using the "phys" property as well. With this series phy_{init,power_on,power_off,exit} will be called twice for each PHY when using aehci-platform.corxhci-mtk.cUSB controller (because the controller driver and our new, generic code now manage the PHYs). the PHY framework handles this gracefully (by ref-counting all operations). a follow-up series will be sent which removes the custom handling from the affected drivers (so only the new PHY wrapper will manage the PHYs state after that follow-up series).
- fixed an unnecessary whitespace change spotted by Alan Stern (thanks!) in patch #3
- removed all Tested-by's since we're changing code againChanges since v6 at [6]:
- fixed unnecessary whitespace change (noticed by Alan Stern - thanks)
- added PATCH #4 to clarify (with an example) how I understood how Rob wanted the dt-binding to look like (see [0]). please wait for an ACK from Rob on this one to make sure that we're not introducing some broken binding (as discussed with Arnd: [7])
- added Alan Stern's ACK on PATCH #3
- added Neil's Tested-by on PATCH #2 and #3Changes since RfC v5 at [5]:
- dropped RfC prefix
- removed noisydev_errif no roothub node was found (spotted by Xiaolong Ye's kbuild test robot - thank you for that!)
- moved the call tousb_phy_roothub_power_off()withinhcd_bus_suspend()to make sure that the PHYs are turned off if the "race with a root-hub wakeup event" condition is met (in this case the PHYs are turned on again, with the old code we did break the PHYs internal ref-counting because we never turned the PHYs off before turning them on again in case of that special "race with a root-hub wakeup event").
additionally we're not handling the status returned byusb_phy_roothub_power_off()anymore (the bus is already turned off and we tried to turn off all PHYs as well - only the PHYs which failed to power off will stay in the current state). thanks to Alan Stern for the suggestion
- removed return value fromusb_phy_roothub_power_off()because none of my code uses it anymore. thanks to Alan Stern for the suggestionChanges since v4 at [4]:
- renamed the subject of the cover-letter (old name was:
"initialize (multiple) PHYs in xhci-plat")
- back into RFC status (see below for the reasons)
- dropped Tested-by from Chunfeng Yun (same reasons as RFC status)
- reworded cover-letter and commit messages from "platform-roothub" to "roothub PHY wrapper"
- moved code fromdrivers/usb/host/platform-roothub.*todrivers/usb/core/phy.*and the changes todrivers/usb/host/xhci-plat.ctodrivers/usb/core/hcd.cas suggested by Mathias Nyman (as a benefit this will enable the new logic for non-xHCI controllers as well - however this was not tested yet)
- rename the structs, function names, etc from platform_roothub_* to usb_phy_roothub*Changes since RFCv3 at [3]:
- moved the DT binding change from patch #3 to patch #1 as suggested by Rob Herring (and slightly adjusted the commit message to account for that)
- added Tested-by from Chunfeng Yun (who confirmed that the whole concept and implementation works fine on Mediatek SoCs - many thanks again!) to patch #2
- added Rob Herring's ACK to patches 1 and 3
- dropped RFC status (RFCv3 -> PATCH v4)Changes since RFCv2 at [2]:
- split phy_{init,exit} and phy_power_{on,off} handling. up until RFCv2 I calledphy_initplusphy_power_oninplatform_roothub_power_onandphy_power_offplusphy_exitinplatform_roothub_power_off. However, Chunfeng Yun (a Mediatek SoC developer - many thanks for testing my series and providing great feedback) reported that only usingphy_power_off(and omittingphy_exit) during system suspend fixes an issue where USB devices would be re-enumerated when resuming. His original problem description: "In order to keep link state on mt8173, we just power off all phys(not exit) when system enter suspend, then power on them again (needn't init, otherwise device will be disconnected) when system resume, this can avoid re-enumerating device.". This fix affects patch #2 and #3 as we now haveplatform_roothub_init(which callsphy_initinternally),platform_roothub_power_on(which callsphy_power_oninternally),platform_roothub_power_off(which callsphy_power_offinternally) andplatform_roothub_exit(which callsphy_exitinternally). suspend and resume only call platform_roothub_power_{on,off} to prevent the issue described by Chunfeng Yun (unfortunately I cannot test this because the Amlogic platform currently does not support system suspend).
- dropped two struct forward declarations fromplatform-roothub.hwhich are not used in the header file (thanks to Chunfeng Yun for spotting this)Changes since RFCv1 at [1]:
- split the usb-xhci dt-binding documentation into a separate patch
- fixed a typo ("usb-phy" -> "phys" in the dt-binding example)
- rebased to apply against latest usb-next[0] http://lists.infradead.org/pipermail/linux-amlogic/2016-November/001818.html
[1] http://marc.info/?l=linux-usb&m=148414866303604&w=2
[2] https://www.spinics.net/lists/linux-usb/msg158967.html
[3] https://www.spinics.net/lists/devicetree/msg190426.html
[4] http://lists.infradead.org/pipermail/linux-amlogic/2017-September/004685.html
[5] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/004924.html
[6] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/005049.html
[7] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/005121.html
[8] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/005124.html
[9] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/005192.html
[10] http://lists.infradead.org/pipermail/linux-amlogic/2018-January/006274.html
[11] https://marc.info/?l=linux-usb&m=151683941207898&w=2
[12] http://lists.infradead.org/pipermail/linux-amlogic/2018-February/006412.html
[13] http://lists.infradead.org/pipermail/linux-amlogic/2018-February/006478.htmlMartin Blumenstingl (8):
dt-bindings: usb: add the documentation for USB HCDs
usb: add a flag to skip PHY initialization to structusb_hcd
usb: core: add a wrapper for the USB PHYs on the HCD
usb: core: hcd: integrate the PHY wrapper into the HCD core
usb: host: xhci-mtk: remove custom USB PHY handling
usb: host: ehci-platform: remove custom USB PHY handling
usb: host: ohci-platform: remove custom USB PHY handling
usb: core: hcd: remove support for initializing a single PHY.../devicetree/bindings/usb/mediatek,mtk-xhci.txt | 5 +- .../devicetree/bindings/usb/mediatek,mtu3.txt | 5 +- Documentation/devicetree/bindings/usb/usb-ehci.txt | 6 +- Documentation/devicetree/bindings/usb/usb-hcd.txt | 9 ++ Documentation/devicetree/bindings/usb/usb-ohci.txt | 6 +- Documentation/devicetree/bindings/usb/usb-uhci.txt | 3 + Documentation/devicetree/bindings/usb/usb-xhci.txt | 5 + drivers/usb/chipidea/host.c | 6 +- drivers/usb/core/Makefile | 2 +- drivers/usb/core/hcd.c | 64 ++++----- drivers/usb/core/phy.c | 158 +++++++++++++++++++++ drivers/usb/core/phy.h | 7 + drivers/usb/host/ehci-fsl.c | 2 + drivers/usb/host/ehci-platform.c | 55 +------ drivers/usb/host/ehci-tegra.c | 1 + drivers/usb/host/ohci-omap.c | 1 +
Quoted 9 lines
drivers/usb/host/ohci-platform.c | 56 +------- drivers/usb/host/xhci-mtk.c | 98 +------------ drivers/usb/host/xhci-plat.c | 1 + include/linux/usb/hcd.h | 8 +- 20 files changed, 253 insertions(+), 245 deletions(-) create mode 100644 Documentation/devicetree/bindings/usb/usb-hcd.txt create mode 100644 drivers/usb/core/phy.c create mode 100644 drivers/usb/core/phy.h
Hi Martin,
Successfully tested on Amlogic Q200 Reference Design board with a Meson GXM S912 SoC.
Other patchsets included :
- improvements and fixes for the phy-meson-gxl-usb2 driver https://lkml.kernel.org/r/20180128202245.25021-1-martin.blumenstingl at googlemail.com
- DWC3 support for Amlogic Meson AXG and GXL SoCs V2 https://lkml.kernel.org/r/20180211211517.5846-1-martin.blumenstingl at googlemail.com
- Meson GXL USB3 PHY driver V4 https://lkml.kernel.org/r/20180303184700.21480-1-martin.blumenstingl at googlemail.com
Thanks,
Neil