From: dbaryshkov@gmail.com (Dmitry Eremin-Solenikov)
To: linux-arm-kernel@lists.infradead.org
Subject: PXA: Handling of UDC with no VBUS pins
Date: Sun, 22 May 2011 13:20:14 +0400 [thread overview]
Message-ID: <BANLkTimfe8x=UDp3tw94q0UPX=Zonqa6dg@mail.gmail.com> (raw)
In-Reply-To: <4DD8CEAA.2010601@free.fr>
On Sun, May 22, 2011 at 12:51 PM, Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> On 05/21/2011 08:35 PM, Dmitry Eremin-Solenikov wrote:
>>
>> 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) ?
>>
>> gpio-vbus driver doesn't do this. It simply handles D+ pullup. I think I'd
>> start with simple D+ pullup driver and the one may add D- functionality
>> if required.
>
> OK, as long as you don't touch the code in pxa27x_udc.c.
Let's do it step by step. My plan would be to drop all non-tranceiver code
for handling pullup and VBUS from both pxa25x_udc and pxa27x_udc.
>>>
>>> The common driver will have to handle the suspend/resume in an
>>> homogenous way.
>>
>> Do pxa25x_udc/pxa27x_udc handle pullup during suspend/resume?
>
> At least pxa27x_udc does, on suspend to RAM (you should look at
> pxa_udc_suspend()).
I see... Thanks for pointing to it.
>>>
>>> If the gadget driver is removed, the pullup should be pulled low.
>>>
>>> All of this work for only 2 drivers looks overkill to me.
>>
>> 3 boards only from PXA. I don't know about other platforms/soc-families.
>
> One other point I've forgotten is that pxa27x_udc in its current state only
> supports gpio pullup/pulldown (ie. an external transciever handles D+
> stimulation). But the PXA sillicon has an internal transciever which can be
> handled directly by pxa27x_udc (register UP2OCR).
>
> Now, nobody uses it. If a board manufacturer is crazy enough to use it, the
> pullup can only be done from inside the pxa27x_udc driver (IO mappings
> driving).
Actually I've thought about this. At least several boards use UP2OCR
handling (balloon3, collibri, cm-x300, em-x270, spitz, stargate, voipac, zeus).
> I still think this driver is a bad idea. But if you wish to do it, go ahead.
> The only thing I'll block is removing the existing pullup code from
> pxa27x_udc.c.
Even if I provide full replacement (from the pulldown-on-suspend POV)?
--
With best wishes
Dmitry
next prev parent reply other threads:[~2011-05-22 9:20 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
2011-05-21 18:35 ` Dmitry Eremin-Solenikov
2011-05-22 8:51 ` Robert Jarzmik
2011-05-22 9:20 ` Dmitry Eremin-Solenikov [this message]
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='BANLkTimfe8x=UDp3tw94q0UPX=Zonqa6dg@mail.gmail.com' \
--to=dbaryshkov@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).