From: Daniel Mack <daniel@zonque.org>
To: Peter Chen <peter.chen@freescale.com>, balbi@ti.com
Cc: linux-usb@vger.kernel.org, andrzej.p@samsung.com,
Daniel Mack <zonque@gmail.com>,
tiwai@suse.de, stable@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH v4 1/1] usb: gadget: f_uac2: finalize wMaxPacketSize according to bandwidth
Date: Tue, 28 Jul 2015 11:37:44 +0200 [thread overview]
Message-ID: <55B74D68.8060506@zonque.org> (raw)
In-Reply-To: <55B74BCD.3030401@zonque.org>
On 07/28/2015 11:30 AM, Daniel Mack wrote:
> On 07/28/2015 03:38 AM, Peter Chen wrote:
>> +static void set_ep_max_packet_size (struct f_uac2_opts *uac2_opts,
>> + struct usb_endpoint_descriptor *ep_desc, unsigned int factor)
>> +{
>> + int chmask;
>> + int srate;
>> + int ssize;
>> + u16 max_packet_size;
>> +
>> + if (ep_desc == &fs_epin_desc || ep_desc == &hs_epin_desc) {
>> + chmask = uac2_opts->p_chmask;
>> + srate = uac2_opts->p_srate;
>> + ssize = uac2_opts->p_ssize;
>> + } else {
>> + WARN_ON (ep_desc != &fs_epout_desc && ep_desc != &hs_epout_desc);
>> + chmask = uac2_opts->c_chmask;
>> + srate = uac2_opts->c_srate;
>> + ssize = uac2_opts->c_ssize;
>> + }
>> +
>> + max_packet_size = num_channels(chmask) * ssize *
>> + DIV_ROUND_UP(srate, factor / (1 << (ep_desc->bInterval - 1)));
>> + ep_desc->wMaxPacketSize = min(cpu_to_le16(max_packet_size),
>> + ep_desc->wMaxPacketSize);
>> +}
>
> Thinking about it again, it would probably be nicer to make this
> function return wMaxPacketSize directly:
Ah, no, that doesn't make sense, sorry. We need bInterval and the
current value of wMaxPacketSize as well. Just stick with your current
approach then :)
prev parent reply other threads:[~2015-07-28 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 1:38 [PATCH v4 1/1] usb: gadget: f_uac2: finalize wMaxPacketSize according to bandwidth Peter Chen
2015-07-28 8:13 ` Daniel Mack
2015-07-28 8:20 ` Peter Chen
2015-07-28 9:30 ` Daniel Mack
2015-07-28 9:37 ` Daniel Mack [this message]
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=55B74D68.8060506@zonque.org \
--to=daniel@zonque.org \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@freescale.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tiwai@suse.de \
--cc=zonque@gmail.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 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.