lkml.org 
[lkml]   [2020]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] dt-bindings: usb: Add binding for onboard USB hubs
Hi Rob,

On Tue, Sep 15, 2020 at 08:21:45AM -0600, Rob Herring wrote:
> On Mon, Sep 14, 2020 at 11:27:48AM -0700, Matthias Kaehlcke wrote:
> > Onboard USB hubs need to be powered and may require initiaization of
> > other resources (like GPIOs or clocks) to work properly. This adds
> > a device tree binding for these hubs.
>
> We already have bindings for these. 2 in fact as I2C controlled hubs are
> often described under the I2C bus.

Yes, these are I2C controlled hubs, which need hub specific drivers. This
driver is for hubs without an additional bus that share similar
initialization requirements and can benefit from common functionality.

> > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> > ---
> >
> > .../bindings/usb/onboard_usb_hub.yaml | 70 +++++++++++++++++++
> > 1 file changed, 70 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/usb/onboard_usb_hub.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/usb/onboard_usb_hub.yaml b/Documentation/devicetree/bindings/usb/onboard_usb_hub.yaml
> > new file mode 100644
> > index 000000000000..f82d8f459eed
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/usb/onboard_usb_hub.yaml
> > @@ -0,0 +1,70 @@
> > +# SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/usb/onboard_usb_hub.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Binding for onboard USB hubs
> > +
> > +maintainers:
> > + - Matthias Kaehlcke <mka@chromium.org>
> > +
> > +allOf:
> > + - $ref: /schemas/usb/onboard_usb_hub.yaml#
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - onboard-usb-hub
> > + - realtek,rts5411
> > +
> > + power-off-in-suspend:
> > + description:
> > + The hub should be powered off during system suspend. When the
> > + "wakeup-source" property is also provided the hub is only powered
> > + off during suspend when no wakeup capable descendants are connected.
> > + type: boolean
> > +
> > + vdd-supply:
> > + description:
> > + phandle to the regulator that provides power to the hub.
> > +
> > + wakeup-source:
> > + description:
> > + Wakeup capable USB devices connected to this hub can be used as
> > + wakeup source.
> > + type: boolean
> > +
> > +required:
> > + - compatible
> > + - vdd-supply
> > +
> > +examples:
> > + - |
> > + usb_hub: usb-hub {
> > + compatible = "realtek,rts5411", "onboard-usb-hub";
> > + vdd-supply = <&pp3300_hub>;
> > + power-off-in-suspend;
> > + wakeup-source;
>
> This is the hub device?

This is the physical hub device on the platform bus, which is the
equivalent to this entry for a usb2512b hub on an I2C bus:

usb2512b@2c {
compatible = "microchip,usb2512b";
reg = <0x2c>;
reset-gpios = <&gpio1 4 GPIO_ACTIVE_LOW>;
};

(source: Documentation/devicetree/bindings/usb/usb251xb.txt)

It doesn't have an I2C, SPI or other bus, hence the platform bus is
used.

> > + };
> > +
> > + &usb_1_dwc3 {
> > + dr_mode = "host";
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + /* 2.0 hub on port 1 */
> > + hub@1 {
> > + compatible = "usbbda,5411";
> > + reg = <1>;
> > + hub = <&usb_hub>;
>
> Or this node is?

It is the USB 2.0 part of the hub. The device is instantiated by
Linux even without this node, but the system associates the node
with the device, which suggests it 'exists'.

The usb2512b mentioned above implicitly also has a node here, it just
isn't specified since the USB controller autodetects it.

> > + };
> > +
> > + /* 3.0 hub on port 2 */
> > + hub@2 {
> > + compatible = "usbbda,411";
> > + reg = <2>;
> > + hub = <&usb_hub>;
>
> Or this node is?

It is the USB 3.0 part of the hub.

> The hub node belongs here.

The platform device isn't probed when the node is inside the USB
controller node. I haven't investigated why that's the case.

> If you really have it connected to 2 upstream ports, then just do
> one node with 'reg = <1 2>;'.

Yes, it is connected to two upstream ports. The platform driver needs a
reference to both/all hubs, to be able to determine whether to keep the
hub powered during system suspend or not.

Technically the hub with product id 0x5411 is connected to port 1 and the
one with product id 0x411 to port 2, so I would say the above is more
accurate than pretending one of the hubs is connected to both ports.

I would argue that the two hub nodes are similar to a SDIO BT/WiFi combo,
where you have one chip/module with multiple functions. The DT has entries
for both functions, even though they reside in the same chip and share the
same bus.

\
 
 \ /
  Last update: 2020-09-16 02:01    [W:0.110 / U:1.532 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site