From: Oliver Neukum <oneukum@suse.de>
To: Naveen Kumar Parna <pnaveenkos@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: btusb_intr_complete returns -EPIPE
Date: Mon, 06 Oct 2014 14:24:28 +0200 [thread overview]
Message-ID: <1412598268.1132.15.camel@linux-0dmf.site> (raw)
In-Reply-To: <CAG0bkvK4-gfeYXXsdNg4BKdjxmo1e5d8rKuABohtYNNBHKJwDA@mail.gmail.com>
On Mon, 2014-10-06 at 17:05 +0530, Naveen Kumar Parna wrote:
> These errors will repeat until sending a proper HCI command on the USB
> bus. Again after some time duration same error will repeats.
>
> The error -32(-EPIPE) says , Endpoint stalled. For non-control
> endpoints, reset this status with usb_clear_halt().
>
> But I don’t see the error(-EPIPE) handling code in btusb module. Does
> anyone has the patch for this scenario?
It really shouldn't stall without reason. We need to know which
transfers stall. A usbmon trace would show you.
Regards
Oliver
next prev parent reply other threads:[~2014-10-06 12:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 11:35 btusb_intr_complete returns -EPIPE Naveen Kumar Parna
2014-10-06 12:24 ` Oliver Neukum [this message]
[not found] ` <CAG0bkv+nKt-TgONDLENNUncz9NScdJGcYR+J2Z6b=wg2grvqhg@mail.gmail.com>
2014-10-06 12:55 ` Oliver Neukum
2014-10-06 13:03 ` Naveen Kumar Parna
2014-10-06 13:29 ` Oliver Neukum
2014-10-06 14:38 ` Naveen Kumar Parna
2014-10-06 14:50 ` Oliver Neukum
[not found] ` <CAG0bkvKJZMhurNNpc_2wgaACRzhyEikb0G0YSY7QnxqBe1rnjw@mail.gmail.com>
2014-10-07 6:44 ` Naveen Kumar Parna
2014-10-07 10:01 ` Oliver Neukum
2014-10-07 13:34 ` Naveen Kumar Parna
2014-10-07 14:31 ` Naveen Kumar Parna
2014-10-08 9:09 ` Oliver Neukum
2014-10-08 10:21 ` Naveen Kumar Parna
2014-10-08 10:44 ` Oliver Neukum
2014-10-08 13:01 ` Naveen Kumar Parna
2014-10-08 13:17 ` Oliver Neukum
2014-10-08 14:10 ` Naveen Kumar Parna
2014-10-08 14:46 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2014-10-06 12:23 Naveen Kumar Parna
[not found] <CAG0bkvJDLP2tgnzu7H_ZCRCnZwkw1zUd1uqWwoDkmrU_FLts7w@mail.gmail.com>
2014-10-09 14:31 ` Alan Stern
2014-10-15 10:11 ` Oliver Neukum
2014-10-15 13:09 ` Naveen Kumar Parna
2014-10-15 13:46 ` Naveen Kumar Parna
2014-10-15 16:11 ` Alan Stern
2014-10-16 7:13 ` Naveen Kumar Parna
2014-10-16 14:16 ` Alan Stern
2014-10-16 15:32 ` Naveen Kumar Parna
2014-10-28 12:40 ` Naveen Kumar Parna
2014-10-28 17:27 ` Alan Stern
[not found] ` <CAG0bkvL-qy+Wvp7q39TOaQ1dZDd0PKyoXHjO=5TrJvdC8byr8A@mail.gmail.com>
2014-10-31 11:27 ` Naveen Kumar Parna
2014-10-31 20:51 ` Alan Stern
2014-10-16 9:15 ` Oliver Neukum
2014-10-16 10:54 ` Naveen Kumar Parna
2014-10-16 14:09 ` Alan Stern
2014-10-16 15:05 ` Naveen Kumar Parna
2014-10-27 9:19 ` Naveen Kumar Parna
[not found] <CAG0bkv+YY90Tq1aTw1Dbg-RSVadoP2U6tyVpW1bZSxBfQ=3Y4g@mail.gmail.com>
2014-11-03 16:19 ` Alan Stern
2014-11-05 6:58 ` Naveen Kumar Parna
2014-11-05 21:09 ` Alan Stern
[not found] <CAG0bkv+DL0bVs9irE7eUB3rC-J16Ue=b9+_TqeuTHJYMJDkC0g@mail.gmail.com>
2014-11-06 16:44 ` Alan Stern
2014-11-10 6:38 ` Naveen Kumar Parna
2014-11-10 16:56 ` Alan Stern
2014-11-11 9:53 ` Naveen Kumar Parna
2014-11-11 15:56 ` Alan Stern
2014-11-10 9:29 ` Naveen Kumar Parna
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=1412598268.1132.15.camel@linux-0dmf.site \
--to=oneukum@suse.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pnaveenkos@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 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).