All of lore.kernel.org
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: PXA: Handling of UDC with no VBUS pins
Date: Fri, 20 May 2011 20:12:23 +0200	[thread overview]
Message-ID: <4DD6AF07.9060306@free.fr> (raw)
In-Reply-To: <20110518120633.GA9860@doriath.ww600.siemens.net>

On 05/18/2011 02:06 PM, Dmitry Eremin-Solenikov wrote:
> Hello, colleagues,
>
> There are several PXA platforms which on the UDC tranceiver part have
> a pullup pin to support connect/disconnect but no VBUS pin to detect
> host presense. Currently such platforms are supported through udc driver
> itself. I'd like to clean that part of pxa25x_udc/pxa27x_udc drivers and
> to move gpio pullup handling to tranceiver.
So, you want to concentrate USB pullup handling, right ?
> My question is what would be better: to extend gpio-vbus to work w/o
> VBUS pin or to write new transceiver driver only handling gpio-pullup?
My personnal feeling is neither, let them be. The generic pullup would 
have to ask itself :
   - should the pullup be applied on D+ (on USB 2.0 and 3.0 devices) ?
   - should the pullup be applied on D- (on USB 1.1 devices) ?
The common driver will have to handle the suspend/resume in an 
homogenous way.
If the gadget driver is removed, the pullup should be pulled low.

All of this work for only 2 drivers looks overkill to me.

And if you want to gather it in a driver, "gpio-vbus" purpose was to 
handle VBUS sensing, ie. power presence on +5V/Gnd lines. The D+ 
handling was not part of its duties, and you'll probably end up with a 
new driver, which is ... overkill IMHO.

Cheers.

--
Robert

  reply	other threads:[~2011-05-20 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 12:06 PXA: Handling of UDC with no VBUS pins Dmitry Eremin-Solenikov
2011-05-20 18:12 ` Robert Jarzmik [this message]
2011-05-21 18:35   ` Dmitry Eremin-Solenikov
2011-05-22  8:51     ` Robert Jarzmik
2011-05-22  9:20       ` Dmitry Eremin-Solenikov
2011-05-22 12:32   ` Sergei Shtylyov

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=4DD6AF07.9060306@free.fr \
    --to=robert.jarzmik@free.fr \
    --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.