public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tegra20: usb: rework set_host_mode
Date: Tue, 07 Aug 2012 16:00:49 -0600	[thread overview]
Message-ID: <50219011.7000708@wwwdotorg.org> (raw)
In-Reply-To: <1344371727.1477.32.camel@tellur>

On 08/07/2012 02:35 PM, Lucas Stach wrote:
> Am Dienstag, den 07.08.2012, 14:21 -0600 schrieb Stephen Warren:
>> On 08/07/2012 12:19 PM, Lucas Stach wrote:
>>> This allows for two things:
>>> - VBus GPIO may be used on other ports than the OTG one
>>> - VBus GPIO may be low active if specified by DT
>>
>> Hmmm. Why would the board have control over whether VBUS is asserted if
>> the port isn't intended to operate in OTG mode?
>>
>> Perhaps power-saving? In that case, I wonder if representing this as a
>> regulator rather than as a VBUS GPIO would make more sense?
>>
>> But irrespective of those questions, I'm inclined to think the patch is
>> probably OK.
>>
> On Colibri the second USB Port is powered down by default and only
> powered up if we are really going to use it. And the GPIO does exactly
> what it tells you from it's name: turn on VBus by triggering the USB
> power switch.

It's probably fine to do this; the kernel also unconditionally sets up
the VBUS GPIO irrespective of USB port mode.

> Thinking about a regulator for this in U-Boot is a bit of an overkill,
> for the Linux kernel this might be another story.

Device tree content isn't supposed to be influence by the consumer; it
should be identical irrespective of which bootloader/OS/... is using it.

So, in the future I expect this to be reworked to get rid of the
vbus-gpio property and replace it with a regulator.

      reply	other threads:[~2012-08-07 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 18:19 [U-Boot] [PATCH] tegra20: usb: rework set_host_mode Lucas Stach
2012-08-07 20:21 ` Stephen Warren
2012-08-07 20:35   ` Lucas Stach
2012-08-07 22:00     ` Stephen Warren [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=50219011.7000708@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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