From: dbaryshkov@gmail.com (Dmitry Eremin-Solenikov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 15/15] pxa2[57]x_udc: drop gpio_pullup handling
Date: Wed, 06 Jul 2011 11:30:52 +0400 [thread overview]
Message-ID: <4E140F2C.2010900@gmail.com> (raw)
In-Reply-To: <20110706072042.GC10729@legolas.emea.dhcp.ti.com>
On 06.07.2011 11:20, Felipe Balbi wrote:
> hi,
>
> On Wed, Jul 06, 2011 at 12:58:48AM +0400, Dmitry Eremin-Solenikov wrote:
>> On 7/6/11, Robert Jarzmik<robert.jarzmik@free.fr> wrote:
>>> On 07/05/2011 03:08 PM, Dmitry Eremin-Solenikov wrote:
>>>> Now as all drivers were converted to using gpio-vbus, drop gpio-pullup
>>>> handling from pxa UDC drivers, thus simplifying them a bit.
>>>
>>> Is this patch compliant with USB 2 specification regarding maximum time
>>> between pullup triggering and UDC ready to answer the "RESET" packet and
>>> be assigned an address ?
>>>
>>> This is the sequence I'm worried about :
>>> (1) The gpio-vbus is loaded
>>> (2) The pxa27x_udc is loaded
>>> (3) USB cable is plugged
>>> => VBUS is sensed
>>> (4) gpio-vbus pulls up the D+ (Dmitry, is that right ?)
>>> (5) the host waits for UDC to settle (100 ms ?)
>>> (5) set address packet(s) are sent from host to UDC
>>> (6) UDC is not enabled, as no gadget is registered
>>> => UDC doesn't answer
>>> => usb host cannot assign it an address
>>> (7) a gadget is loaded (g_ether for example)
>>> => UDC is enabled, but too late
>>>
>>> Alan, Gregh, could you confirm point (5) about a maximum time between D+
>>> line activation and UDC duty to repond to "set address" packets, as well
>>> as the consequence of point (6) where the usb device is rejected because
>>> no address could be assigned ?
>>>
>>> Dmitry, could you confirm the the D+ pullup is done at point (4) ?
>>
>> No, I can't confirm this. IIUC, evrything happens in abit different way:
>> (4) trancseiver notifies udc about VBUS sense
>> (5) a gadget is loaded (g_ether for example)
>> (6) gadget asks udc to enale pullup
>> (7) udc tells gpio_vbus to enable pullup.
>
> yeah, with udc-core.c we only enable pullup after gadget driver is
> loaded.
>
> 290 ret = bind(udc->gadget);
> 291 if (ret)
> 292 goto err1;
> 293 ret = usb_gadget_udc_start(udc->gadget, driver);
> 294 if (ret) {
> 295 driver->unbind(udc->gadget);
> 296 goto err1;
> 297 }
> 298 usb_gadget_connect(udc->gadget);
>
> but this is the new style bind() and many UDCs still need to be
> converted.
This was working before the udc-core. If it doesn't work now for
unconverted drivers (PXA e.g.) that's really a huge regression!
--
With best wishes
Dmitry
next prev parent reply other threads:[~2011-07-06 7:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 13:08 [PATCH 00/15] Big pxa2[57]x_udc cleanup Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 01/15] ARM: pxa/balloon3: drop udc_is_connected Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 02/15] ARM: pxa/mioa701: " Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 03/15] ARM: pxa/stargate2: " Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 04/15] ARM: pxa25x_udc: separate lubbock handling to lubbock-usb transceiver Dmitry Eremin-Solenikov
2011-07-05 13:47 ` Felipe Balbi
2011-07-05 13:08 ` [PATCH 05/15] ARM: pxa/lubbock: switch to using lubbock_usb_xceiv transceiver Dmitry Eremin-Solenikov
2011-07-05 14:47 ` Sergei Shtylyov
2011-07-05 13:08 ` [PATCH 06/15] pxa: drop handling of udc_is_connected Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 07/15] pxa25x_udc: drop support for udc_command Dmitry Eremin-Solenikov
2011-07-05 13:46 ` Felipe Balbi
2011-07-08 21:34 ` Greg KH
2011-07-08 21:54 ` Felipe Balbi
2011-07-08 22:02 ` Greg KH
2011-07-08 22:14 ` Felipe Balbi
2011-07-12 13:41 ` Dmitry Eremin-Solenikov
2011-07-14 2:52 ` Eric Miao
2011-07-14 18:24 ` Robert Jarzmik
2011-07-14 19:01 ` Robert Jarzmik
2011-07-15 10:40 ` Eric Miao
2011-07-18 8:38 ` Felipe Balbi
2011-07-09 8:50 ` Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 08/15] otg: add gpio_pullup OTG transceiver for devices with no VBUS sensing Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 09/15] corgi: convert to use gpio-pullup Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 10/15] poodle: " Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 11/15] h5000: " Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 12/15] gpio-vbus: support disabling D+ pullup on suspend Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 13/15] mioa701: move gpio-pullup functionality to gpio-vbus Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 14/15] gpio-pullup: support disabling D+ pullup on suspend Dmitry Eremin-Solenikov
2011-07-05 13:08 ` [PATCH 15/15] pxa2[57]x_udc: drop gpio_pullup handling Dmitry Eremin-Solenikov
2011-07-05 13:49 ` Felipe Balbi
2011-07-05 20:42 ` Robert Jarzmik
2011-07-05 20:58 ` Dmitry Eremin-Solenikov
2011-07-06 7:20 ` Felipe Balbi
2011-07-06 7:30 ` Dmitry Eremin-Solenikov [this message]
2011-07-06 7:34 ` Felipe Balbi
2011-07-05 13:45 ` [PATCH 00/15] Big pxa2[57]x_udc cleanup Eric Miao
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=4E140F2C.2010900@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).