From: David Cohen <david.a.cohen@linux.intel.com>
To: David Cohen <david.a.cohen@linux.intel.com>
Cc: balbi@ti.com, gregkh@linuxfoundation.org,
stern@rowland.harvard.edu, mina86@mina86.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/5] usb: gadget: f_fs: remove loop from I/O function
Date: Mon, 11 Nov 2013 15:21:58 -0800 [thread overview]
Message-ID: <52816696.1000806@linux.intel.com> (raw)
In-Reply-To: <1384201011-11114-4-git-send-email-david.a.cohen@linux.intel.com>
On 11/11/2013 12:16 PM, David Cohen wrote:
> From: Michal Nazarewicz <mina86@mina86.com>
>
> When endpoint changes (due to it being disabled or alt setting changed),
> mimic the action as if the change happened after the request has been
> queued, instead of retrying with the new endpoint.
>
> Signed-off-by: Michal Nazarewicz <mina86@mina86.com>
> Cc: David Cohen <david.a.cohen@linux.intel.com>
> ---
> drivers/usb/gadget/f_fs.c | 94 +++++++++++++++++++++--------------------------
> 1 file changed, 41 insertions(+), 53 deletions(-)
>
> diff --git a/drivers/usb/gadget/f_fs.c b/drivers/usb/gadget/f_fs.c
> index 75e4b7846a8d..f1563c47e0c2 100644
> --- a/drivers/usb/gadget/f_fs.c
> +++ b/drivers/usb/gadget/f_fs.c
> @@ -756,74 +756,61 @@ static ssize_t ffs_epfile_io(struct file *file,
> {
> struct ffs_epfile *epfile = file->private_data;
> struct ffs_ep *ep;
> - char *data = NULL;
> ssize_t ret;
> + char *data;
> int halt;
>
> - goto first_try;
> - do {
> - spin_unlock_irq(&epfile->ffs->eps_lock);
> - mutex_unlock(&epfile->mutex);
> + /* Are we still active? */
> + if (WARN_ON(epfile->ffs->state != FFS_ACTIVE)) {
> + ret = -ENODEV;
> + goto error;
> + }
>
> -first_try:
> - /* Are we still active? */
> - if (WARN_ON(epfile->ffs->state != FFS_ACTIVE)) {
> - ret = -ENODEV;
> + /* Wait for endpoint to be enabled */
> + ep = epfile->ep;
> + if (!ep) {
> + if (file->f_flags & O_NONBLOCK) {
> + ret = -EAGAIN;
> goto error;
> }
>
> - /* Wait for endpoint to be enabled */
> - ep = epfile->ep;
> - if (!ep) {
> - if (file->f_flags & O_NONBLOCK) {
> - ret = -EAGAIN;
> - goto error;
> - }
> -
> - if (wait_event_interruptible(epfile->wait,
> - (ep = epfile->ep))) {
> - ret = -EINTR;
> - goto error;
> - }
> - }
> -
> - /* Do we halt? */
> - halt = !read == !epfile->in;
> - if (halt && epfile->isoc) {
> - ret = -EINVAL;
> + if (wait_event_interruptible(epfile->wait, (ep = epfile->ep))) {
> + ret = -EINTR;
> goto error;
> }
> + }
>
> - /* Allocate & copy */
> - if (!halt && !data) {
> - data = kzalloc(len, GFP_KERNEL);
> - if (unlikely(!data))
> - return -ENOMEM;
> + /* Do we halt? */
> + halt = !read == !epfile->in;
One curiosity here. This patch prints the following warning:
In file included from (...)/drivers/usb/gadget/g_ffs.c:55:0:
(...)/drivers/usb/gadget/f_fs.c: In function 'ffs_epfile_io.isra.18':
(...)/drivers/usb/gadget/f_fs.c:837:15: warning: 'data_len' may be used
uninitialized in this function [-Wmaybe-uninitialized]
But if we do this dummy change on it:
@@ -782,7 +782,10 @@ static ssize_t ffs_epfile_io(struct file *file,
}
/* Do we halt? */
- halt = !read == !epfile->in;
+ if (!read == !epfile->in)
+ halt = 1;
+ else
+ halt = 0;
if (halt && epfile->isoc) {
ret = -EINVAL;
goto error;
The warning goes away. This false-positive warning comes out of this
gcc version:
$ i686-linux-android-gcc --version
i686-linux-android-gcc (GCC) 4.7
Br, David Cohen
> + if (halt && epfile->isoc) {
> + ret = -EINVAL;
> + goto error;
> + }
>
> - if (!read &&
> - unlikely(__copy_from_user(data, buf, len))) {
> - ret = -EFAULT;
> - goto error;
> - }
> - }
> + /* Allocate & copy */
> + if (!halt) {
> + data = kmalloc(len, GFP_KERNEL);
> + if (unlikely(!data))
> + return -ENOMEM;
>
> - /* We will be using request */
> - ret = ffs_mutex_lock(&epfile->mutex,
> - file->f_flags & O_NONBLOCK);
> - if (unlikely(ret))
> + if (!read && unlikely(copy_from_user(data, buf, len))) {
> + ret = -EFAULT;
> goto error;
> + }
> + }
>
> - /*
> - * We're called from user space, we can use _irq rather then
> - * _irqsave
> - */
> - spin_lock_irq(&epfile->ffs->eps_lock);
> + /* We will be using request */
> + ret = ffs_mutex_lock(&epfile->mutex, file->f_flags & O_NONBLOCK);
> + if (unlikely(ret))
> + goto error;
> + spin_lock_irq(&epfile->ffs->eps_lock);
>
> - /*
> - * While we were acquiring mutex endpoint got disabled
> - * or changed?
> - */
> - } while (unlikely(epfile->ep != ep));
> + /* While we were acquiring mutex endpoint got disabled or changed. */
> + if (epfile->ep != ep) {
> + ret = -ESHUTDOWN;
> + spin_unlock_irq(&epfile->ffs->eps_lock);
> + goto error_unlock;
> + }
>
> /* Halt */
> if (unlikely(halt)) {
> @@ -858,6 +845,7 @@ first_try:
> }
> }
>
> +error_unlock:
> mutex_unlock(&epfile->mutex);
> error:
> kfree(data);
>
next prev parent reply other threads:[~2013-11-11 23:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 20:16 [PATCH v5 0/5] add gadget quirk to adapt f_fs for DWC3 David Cohen
2013-11-11 20:16 ` [PATCH v5 1/5] usb: gadget: move bitflags to the end of usb_gadget struct David Cohen
2013-11-11 23:52 ` Michal Nazarewicz
2013-11-11 20:16 ` [PATCH v5 2/5] usb: gadget: add quirk_ep_out_aligned_size field to struct usb_gadget David Cohen
2013-11-11 23:55 ` Michal Nazarewicz
2013-11-12 0:03 ` David Cohen
2013-11-12 12:54 ` Michal Nazarewicz
2013-12-06 20:13 ` Felipe Balbi
2013-12-06 20:14 ` David Cohen
2013-11-11 20:16 ` [PATCH v5 3/5] usb: gadget: f_fs: remove loop from I/O function David Cohen
2013-11-11 23:21 ` David Cohen [this message]
2013-11-11 23:57 ` [PATCHv5.1 " Michal Nazarewicz
2013-12-06 20:18 ` Felipe Balbi
2013-11-11 20:16 ` [PATCH v5 4/5] usb: f_fs: check quirk to pad epout buf size when not aligned to maxpacketsize David Cohen
2013-11-11 23:58 ` [PATCHv5.1 4/5] " Michal Nazarewicz
2013-11-12 0:12 ` David Cohen
2013-11-12 12:59 ` Michal Nazarewicz
2013-11-12 18:26 ` David Cohen
2013-12-06 20:19 ` Felipe Balbi
2013-11-11 20:16 ` [PATCH v5 5/5] usb: dwc3: set gadget's quirk ep_out_align_size David Cohen
2013-12-06 20:19 ` Felipe Balbi
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=52816696.1000806@linux.intel.com \
--to=david.a.cohen@linux.intel.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mina86@mina86.com \
--cc=stern@rowland.harvard.edu \
/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).