From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] powerpc/85xx: usb: Limit controllers initialized by usb_init()
Date: Tue, 14 Jun 2016 14:13:38 +0200 [thread overview]
Message-ID: <575FF4F2.6040600@denx.de> (raw)
In-Reply-To: <1465882851528.90355@alliedtelesis.co.nz>
On 06/14/2016 07:40 AM, Matthew Bright wrote:
> Hi,
Hi,
> I am looking for a way to limit which usb host interfaces are initiali-
> zed by usb_init() in order to skip unused interfaces. This is currently
> governed CONFIG_USB_MAX_CONTROLLER_COUNT, which is possible to redefine
> at the board level. However this doesn't cover more complex cases where
> a SoC has multiple host interfaces but a board using that SoC only uses
> a subset that is not necessarily contiguous.
>
> Does there currently exist a way to define such behavior, or should the
> functionality be added to usb_init() to support this?
The driver model should allow you to do exactly that, though I don't
know if it's supposed on the MPC85xx .
> Thanks.
> Matthew Bright
>
>
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2016-06-14 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 5:40 [U-Boot] powerpc/85xx: usb: Limit controllers initialized by usb_init() Matthew Bright
2016-06-14 12:13 ` Marek Vasut [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=575FF4F2.6040600@denx.de \
--to=marex@denx.de \
--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