From: Michal Nazarewicz <mina86@mina86.com>
To: Felipe Balbi <balbi@kernel.org>, Baolin Wang <baolin.wang@linaro.org>
Cc: gregkh@linuxfoundation.org, eu@felipetonello.com,
r.baldyga@samsung.com, dan.carpenter@oracle.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
broonie@kernel.org, baolin.wang@linaro.org
Subject: Re: [PATCH] usb: gadget: f_midi: Add checking if it need align buffer's size to an ep's maxpacketsize
Date: Fri, 08 Jul 2016 16:04:31 +0200 [thread overview]
Message-ID: <xa1t4m80teds.fsf@mina86.com> (raw)
In-Reply-To: <87lh1ci7tt.fsf@linux.intel.com>
> Baolin Wang <baolin.wang@linaro.org> writes:
>> @@ -359,10 +361,12 @@ static int f_midi_set_alt(struct usb_function *f, unsigned intf, unsigned alt)
>>
>> /* allocate a bunch of read buffers and queue them all at once. */
>> for (i = 0; i < midi->qlen && err == 0; i++) {
>> - struct usb_request *req =
>> - midi_alloc_ep_req(midi->out_ep,
>> - max_t(unsigned, midi->buflen,
>> - bulk_out_desc.wMaxPacketSize));
>> + struct usb_request *req;
>> +
>> + length = usb_ep_align_maybe(midi->gadget, midi->out_ep,
>> + midi->buflen);
On Fri, Jul 08 2016, Felipe Balbi wrote:
> after calling usb_ep_align_maybe()...
>
>> + req = midi_alloc_ep_req(midi->out_ep,
>> + max_t(unsigned, length, bulk_out_desc.wMaxPacketSize));
>
> ... max_t() is pointless. length will *always* >= wMaxPacketSize.
That is only true for gadgets with the quirk. usb_ep_align_maybe is
a noöp for gadgets without the quirk.
--
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»
next prev parent reply other threads:[~2016-07-08 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 9:11 [PATCH] usb: gadget: f_midi: Add checking if it need align buffer's size to an ep's maxpacketsize Baolin Wang
2016-07-07 12:51 ` Michal Nazarewicz
2016-07-08 2:25 ` Baolin Wang
2016-07-08 13:04 ` Michal Nazarewicz
2016-07-08 13:25 ` Felipe Balbi
2016-07-08 13:27 ` Felipe Balbi
2016-07-11 2:25 ` Baolin Wang
2016-07-08 14:05 ` Michal Nazarewicz
2016-07-11 2:26 ` Baolin Wang
2016-07-08 13:21 ` Felipe Balbi
2016-07-08 14:04 ` Michal Nazarewicz [this message]
2016-07-11 2:22 ` Baolin Wang
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=xa1t4m80teds.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=balbi@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=eu@felipetonello.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=r.baldyga@samsung.com \
/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