On Tue, May 12, 2026 at 5:12 PM Marek Vasut <[email protected]> wrote:
>
> On 5/12/26 11:41 AM, Alexey Charkov wrote:
> > CoreChips SL6341 is a 4-port USB 2.0 and 3.0 hub controller. It always
> > requires external 1v1
>
> 1V1 (V in caps), fix globally.

Ack

> > power and can optionally use external 3v3 power
> > (or alternatively it has a 5v->3v3 LDO built in to derive 3v3 power from
> > VBUS). It also exposes a reset pin.
> >
> > Device tree bindings are queued up for upstream release with Linux 7.1
> >
> > Link: 
> > https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/usb/corechips%2Csl6341.yaml
> > Signed-off-by: Alexey Charkov <[email protected]>
> > ---
> >   common/usb_onboard_hub.c | 12 ++++++++++++
> >   1 file changed, 12 insertions(+)
> >
> > diff --git a/common/usb_onboard_hub.c b/common/usb_onboard_hub.c
> > index 6fc34489a98f..d15d7bbff87d 100644
> > --- a/common/usb_onboard_hub.c
> > +++ b/common/usb_onboard_hub.c
> > @@ -262,6 +262,12 @@ static int usb_onboard_hub_remove(struct udevice *dev)
> >       return ret;
> >   }
> >
> > +static const struct onboard_hub_data corechips_sl6341_data = {
> > +     .reset_us = 10000,
> > +     .num_supplies = 2,
> > +     .supply_names = { "vdd1v1-supply", "vdd3v3-supply" },
>
> Is there a YAML binding document patch which describes these supplies
> already , maybe a patch posted to devicetree@ ?

Yes, the link is in the commit message :) Merged for 7.1 as commit
bfcb86e58f3a ("dt-bindings: usb: Add Corechips SL6341 USB2.0/3.0 hub
controller")

> > +};
> > +
> >   static const struct onboard_hub_data usb2514_data = {
> >       .power_on_delay_us = 500,
> >       .reset_us = 1,
> > @@ -299,6 +305,12 @@ static const struct udevice_id usb_onboard_hub_ids[] = 
> > {
> >       }, {
> >               .compatible = "usb4b4,6506",    /* Cypress HX3 USB 2.0 */
> >               .data = (ulong)&usbhx3_data,
> > +     }, {
> > +             .compatible = "usb3431,6241",   /* Corechips SL6341 USB 2.0 */
> Keep the list sorted, 3 goes before 4 .

Alright. My thinking was that 0x04b4 goes before 0x3431. Will move further up.

Best regards,
Alexey

Reply via email to