All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Fabio Estevam <festevam@denx.de>
Cc: arnd@arndb.de, linux-arm-kernel@lists.infradead.org,
	broonie@kernel.org, javier.carrasco@wolfvision.net,
	linux-arm-kernel@lists.infradead.org,
	Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Select CONFIG_USB_ONBOARD_DEV as built-in
Date: Tue, 30 Apr 2024 08:28:09 +0200	[thread overview]
Message-ID: <4910905.GXAFRqVoOG@steina-w> (raw)
In-Reply-To: <CAOMZO5A6-WhOTuZww+hio-JjKz61JUAczF=2FgwckVY4ovGcyA@mail.gmail.com>

Hi,

Am Dienstag, 30. April 2024, 00:09:52 CEST schrieb Fabio Estevam:
> Hi Arnd,
> 
> On Mon, Apr 8, 2024 at 11:03 AM Fabio Estevam <festevam@gmail.com> wrote:
> >
> > From: Fabio Estevam <festevam@denx.de>
> >
> > Selecting CONFIG_USB_ONBOARD_DEV as a module may cause the following
> > run-time error when probing a USB2514 hub on a imx6q-udoo board:
> >
> > usb 1-1: device not accepting address 5, error -71
> > usb usb1-port1: unable to enumerate USB device
> >
> > Fix this issue by selecting CONFIG_USB_ONBOARD_DEV as built-in so
> > that the USB hub reset line and clock can be activated earlier.
> >
> > Signed-off-by: Fabio Estevam <festevam@denx.de>
> > ---
> > Here is the imx6q-udoo boot log from Mark's farm that shows the problem:
> >
> > https://storage.kernelci.org/next/master/next-20240408/arm/multi_v7_defconfig/gcc-10/lab-broonie/baseline-imx6dl-udoo.html
> 
> A gentle ping.

Despite the change to the defconfig. If this driver causes problems when
being built as module, shouldn't it be bool instead of tristate then?

Best regards,
Alexander

-- 
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-04-30  6:28 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 [this message]
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

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=4910905.GXAFRqVoOG@steina-w \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.