From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: Re: [PATCH v2 3/3] usb: misc: onboard_usb_hub: Add TI USB8041 hub support
Date: Wed, 20 Jul 2022 09:18:50 +0200 [thread overview]
Message-ID: <3525334.R56niFO833@steina-w> (raw)
In-Reply-To: <YtHFEY+iAipCROPl@google.com>
Am Freitag, 15. Juli 2022, 21:50:41 CEST schrieb Matthias Kaehlcke:
> On Fri, Jul 15, 2022 at 09:33:00AM +0200, Alexander Stein wrote:
> > This is a 4-port 3.0 USB hub.
> >
> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> > ---
> > Changes in v2:
> > * Add devtype data containing waiting times
> >
> > drivers/usb/misc/onboard_usb_hub.c | 3 +++
> > drivers/usb/misc/onboard_usb_hub.h | 7 +++++++
> > 2 files changed, 10 insertions(+)
> >
> > diff --git a/drivers/usb/misc/onboard_usb_hub.c
> > b/drivers/usb/misc/onboard_usb_hub.c index 1dd7f4767def..319b4b1748fb
> > 100644
> > --- a/drivers/usb/misc/onboard_usb_hub.c
> > +++ b/drivers/usb/misc/onboard_usb_hub.c
> > @@ -339,6 +339,7 @@ static struct platform_driver onboard_hub_driver = {
> >
> > /************************** USB driver **************************/
> >
> > #define VENDOR_ID_REALTEK 0x0bda
> >
> > +#define VENDOR_ID_TI 0x0451
> >
> > /*
> >
> > * Returns the onboard_hub platform device that is associated with the
> > USB
> >
> > @@ -416,6 +417,8 @@ static const struct usb_device_id
> > onboard_hub_id_table[] = {>
> > { USB_DEVICE(VENDOR_ID_REALTEK, 0x5411) }, /* RTS5411 USB 2.1 */
> > { USB_DEVICE(VENDOR_ID_REALTEK, 0x0414) }, /* RTS5414 USB 3.2 */
> > { USB_DEVICE(VENDOR_ID_REALTEK, 0x5414) }, /* RTS5414 USB 2.1 */
> >
> > + { USB_DEVICE(VENDOR_ID_TI, 0x8140) }, /* TI USB8041 3.0 */
> > + { USB_DEVICE(VENDOR_ID_TI, 0x8142) }, /* TI USB8041 2.0 */
> >
> > {}
> >
> > };
> > MODULE_DEVICE_TABLE(usb, onboard_hub_id_table);
> >
> > diff --git a/drivers/usb/misc/onboard_usb_hub.h
> > b/drivers/usb/misc/onboard_usb_hub.h index 7e743f4c8aaa..fcb6a9024bbd
> > 100644
> > --- a/drivers/usb/misc/onboard_usb_hub.h
> > +++ b/drivers/usb/misc/onboard_usb_hub.h
> > @@ -11,7 +11,14 @@ struct onboard_hub_devtype_data {
> >
> > unsigned long reset_duration; /* reset pulse width in
us */
> >
> > };
> >
> > +static const struct onboard_hub_devtype_data ti_tusb8041_data = {
> > + .power_stable_time = 3000,
> > + .reset_duration = 3000,
>
> Aren't these two values actually the same thing, i.e. the minimum
> duration of the reset?
>
> From the data sheet:
>
> A minimum reset duration of 3 ms is required
>
> td2: VDD and VDD33 stable before de-assertion of GRSTz (>= 3ms)
>
> My understanding is that td2 is just another expression of the first
> requirement.
They may have the same values, but IMHO they are applied differently.
'power_stable_time' (or power_stable_us now) applies after supplying power,
while 'reset_duration' (or reset_us now) applies when you deassert the reset
line.
For that reason I would like to keep them separated.
Thanks and best regards,
Alexander
next prev parent reply other threads:[~2022-07-20 7:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 7:32 [PATCH v2 1/3] dt-bindings: usb: Add binding for TI USB8041 hub controller Alexander Stein
2022-07-15 7:32 ` [PATCH v2 2/3] usb: misc: onboard_usb_hub: Add reset-gpio support Alexander Stein
2022-07-15 19:44 ` Matthias Kaehlcke
2022-07-20 7:15 ` Alexander Stein
2022-07-21 20:25 ` Matthias Kaehlcke
2022-07-15 7:33 ` [PATCH v2 3/3] usb: misc: onboard_usb_hub: Add TI USB8041 hub support Alexander Stein
2022-07-15 19:50 ` Matthias Kaehlcke
2022-07-20 7:18 ` Alexander Stein [this message]
2022-07-21 20:38 ` Matthias Kaehlcke
2022-07-15 8:17 ` [PATCH v2 1/3] dt-bindings: usb: Add binding for TI USB8041 hub controller Krzysztof Kozlowski
2022-07-20 6:58 ` Alexander Stein
2022-07-15 23:53 ` Matthias Kaehlcke
2022-07-20 6:57 ` Alexander Stein
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=3525334.R56niFO833@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-usb@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).