From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1] arch/x86: Select USB before selecting host driver
Date: Wed, 5 Jul 2017 09:09:21 -0400 [thread overview]
Message-ID: <20170705130921.GU9889@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmU1JALVM3FvBJsVaRJWXEFZ8BpMoBwVEDaQA3KHH0Ri5w@mail.gmail.com>
On Wed, Jul 05, 2017 at 08:19:27PM +0800, Bin Meng wrote:
> +Marek,
>
> Hi Andy,
>
> On Wed, Jul 5, 2017 at 5:36 PM, Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Wed, Jul 5, 2017 at 12:36 PM, Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
> >> On Wed, Jul 5, 2017 at 8:23 AM, Bin Meng <bmeng.cn@gmail.com> wrote:
> >
> >> So, options are:
> >> 1) apply my patch
> >> 2) remove selection of the host at least for X86.
> >
> > 3) move hosts out of "if USB".
> >
>
> 4) select USB in USB_EHCI_HCD?
>
> Not sure which option is the best way.
So, to be clear, CONFIG_USB is not used in the code. It's a
Kconfig-only option we can / should use to make navigation and
dependencies easier. I would think that USB needs to be enabled for any
USB-related choice to be visible (so things can depends on USB or be
hidden under if USB, depending on overall file context).
So I would expect X86 (and most ARCH_xxx under ARM and other cases) to
at least imply USB, if not select it.
And peeking at the kernel, this maybe should be CONFIG_USB_SUPPORT not
CONFIG_USB, to be clearer?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170705/29c9d15e/attachment.sig>
next prev parent reply other threads:[~2017-07-05 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 16:32 [U-Boot] [PATCH v1] arch/x86: Select USB before selecting host driver Andy Shevchenko
2017-07-05 5:23 ` Bin Meng
2017-07-05 9:36 ` Andy Shevchenko
2017-07-05 9:36 ` Andy Shevchenko
2017-07-05 12:19 ` Bin Meng
2017-07-05 13:09 ` Tom Rini [this message]
2017-07-10 2:14 ` Bin Meng
2017-07-22 5:11 ` Bin Meng
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=20170705130921.GU9889@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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