From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 42/46] usb: gadget: move ep_matches() from epautoconf to udc-core
Date: Sat, 25 Jul 2015 13:04:51 +0200 [thread overview]
Message-ID: <87oaj0ebvw.fsf@belgarion.home> (raw)
In-Reply-To: <55B31FC9.1000407@tul.cz> (Petr Cvek's message of "Sat, 25 Jul 2015 07:34:01 +0200")
Petr Cvek <petr.cvek@tul.cz> writes:
> On 23.7.2015 21:46, Alan Stern wrote:
>>> It seems that it allows using a BULK endpoint for requested INT
>>> endpoint. For my PXA27x machine the original code returns BULK EP
>>> even with valid INT endpoint definition (because BULK EPs are defined
>>> earlier than INT EPs).
>>
>> Yes, it does allow a bulk endpoint to be used when an interrupt
>> endpoint was requested. However, it won't return a bulk endpoint if
>> all the bulk endpoints are already in use.
This cannot work for pxa27x.
The pxa27x IP has a hardware limitation which prevents an endpoint from changing
its type once the UDC is enabled (see the comment at the beginning of
pxa27x_udc.c).
If that patchset implies that for a requested INT endpoint a BULK endpoint can
be returned, that won't work. Felipe and Robert, is that what this patchset
implies ?
> A default PXA27x configuration returns BULK for requested INT. Which is
> unfortunate, because PXA27x supports INT endpoints and has one predefined, but
> this function find BULK first (one BULK is allocated and INT is never used).
See above.
> Because if they do, the ep_matches() function works poorly. It returns a BULK
> for device (gadget) side, but host side (PC) thinks that this endpoint is an INT
> and handles it in this way. But the PXA27x thinks the endpoint is a BULK and
> handles it in its way (according to datasheet, settings for a BULK and an INT
> transfers are not 100% compatible).
>
> I cannot test "INT as BULK" behavior for the gadget functions, because all
> gadgets which works on PXA27x does not use INT endpoints (some allocate the
> endpoint but never use it).
Ah a bit of history here.
At least gadget zero does, and it's my main testing point for pxa27x_udc.
Then there should be g_serial (no acm nor obex), but that's something I have not
tried since 2009 ...
For history also, there was already an attempt a long time ago for epautoconf
revamping, done by Rodolfo Giometti IIRC.
Anyway, I need pxa27x_udc to remain functional, so I'd like to understand if
something will stop working, Robert B.
Cheers.
--
Robert
next prev parent reply other threads:[~2015-07-25 11:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55B07048.3000609@tul.cz>
2015-07-23 14:36 ` [PATCH v3 42/46] usb: gadget: move ep_matches() from epautoconf to udc-core Felipe Balbi
2015-07-25 5:29 ` Petr Cvek
2015-07-23 19:46 ` Alan Stern
2015-07-25 5:34 ` Petr Cvek
2015-07-25 11:04 ` Robert Jarzmik [this message]
2015-07-25 15:30 ` Alan Stern
2015-07-25 17:04 ` Robert Jarzmik
2015-07-25 18:08 ` Robert Baldyga
2015-07-25 19:25 ` Petr Cvek
2015-07-25 19:14 ` Petr Cvek
2015-07-25 21:36 ` Alan Stern
2015-07-26 0:20 ` Petr Cvek
2015-07-26 15:14 ` Alan Stern
2015-07-26 18:58 ` Petr Cvek
2015-07-26 19:43 ` Robert Baldyga
2015-07-25 21:15 ` Alan Stern
2015-07-25 19:41 ` Petr Cvek
2015-07-15 6:31 [PATCH v3 00/46] usb: gadget: rework ep matching and claiming mechanism Robert Baldyga
2015-07-15 6:32 ` [PATCH v3 42/46] usb: gadget: move ep_matches() from epautoconf to udc-core Robert Baldyga
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=87oaj0ebvw.fsf@belgarion.home \
--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 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).