From: Matthias Kaehlcke <mka@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: Fabio Estevam <festevam@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Fabio Estevam <festevam@denx.de>,
linux-arm-kernel@lists.infradead.org,
javier.carrasco@wolfvision.net
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Select CONFIG_USB_ONBOARD_DEV as built-in
Date: Mon, 6 May 2024 15:58:46 +0000 [thread overview]
Message-ID: <Zjj-NtlTwvSvK_3l@google.com> (raw)
In-Reply-To: <Zjjxe7EnjbKFwUxM@finisterre.sirena.org.uk>
On Tue, May 07, 2024 at 12:04:27AM +0900, Mark Brown wrote:
> On Mon, May 06, 2024 at 02:54:12PM +0000, Matthias Kaehlcke wrote:
> > On Fri, May 03, 2024 at 06:13:32PM -0300, Fabio Estevam wrote:
> > > On Fri, May 3, 2024 at 5:11 PM Matthias Kaehlcke <mka@chromium.org> wrote:
>
> > > > I wonder if the problem could be that the sense resistors of the hub
> > > > on the imx6q-udoo are always active and not only when the hub is
> > > > powered, indicating the controller the presence of a device, which
> > > > results in an attempt to enumerate it.
>
> > > The imx6q-udoo schematics are here:
> > > https://udoo.org/download/files/UDOO_QUAD-DUAL/schematics/UDOO_QUAD-DUAL_REV_D_schematics.pdf
>
> > There are no external pull-ups on USB_H1_DP/USB_H1_DN, maybe internal
> > pulls are enabled when the hub isn't powered?
>
> I do note that the vendor BSP worked (and I think also some older
> mainline versions too?).
The official BSP releases pre-date the onboard_usb_dev/hub driver:
https://www.udoo.org/resources-quad-dual/. I guess they use a fixed
regulator hack to power the hub on at boot.
Yup, upstream also still uses a regulator hack:
reg_usb_h1_vbus: regulator-usb-h1-vbus {
compatible = "regulator-fixed";
regulator-name = "usb_h1_vbus";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
enable-active-high;
startup-delay-us = <2>; /* USB2415 requires a POR of 1 us minimum */
gpio = <&gpio7 12 0>;
};
arch/arm/boot/dts/nxp/imx/imx6qdl-udoo.dtsi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-05-06 15:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 14:02 [PATCH] ARM: multi_v7_defconfig: Select CONFIG_USB_ONBOARD_DEV as built-in Fabio Estevam
2024-04-29 22:09 ` Fabio Estevam
2024-04-30 6:28 ` Alexander Stein
2024-04-30 7:52 ` Arnd Bergmann
2024-04-30 19:53 ` Fabio Estevam
2024-04-30 20:24 ` Arnd Bergmann
2024-05-01 23:04 ` Fabio Estevam
2024-05-02 14:49 ` Matthias Kaehlcke
2024-05-02 18:37 ` Arnd Bergmann
2024-05-02 21:45 ` Matthias Kaehlcke
2024-05-02 22:58 ` Fabio Estevam
2024-05-03 17:16 ` Matthias Kaehlcke
2024-05-03 17:51 ` Fabio Estevam
2024-05-03 20:11 ` Matthias Kaehlcke
2024-05-03 21:13 ` Fabio Estevam
2024-05-06 14:54 ` Matthias Kaehlcke
2024-05-06 15:04 ` Mark Brown
2024-05-06 15:58 ` Matthias Kaehlcke [this message]
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=Zjj-NtlTwvSvK_3l@google.com \
--to=mka@chromium.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=javier.carrasco@wolfvision.net \
--cc=linux-arm-kernel@lists.infradead.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).