From: Felipe Balbi <balbi@ti.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Felipe Balbi <balbi@ti.com>,
Alexander Holler <holler@ahsoftware.de>,
Michael Jones <michael.jones@matrix-vision.de>,
Greg KH <gregkh@suse.de>,
Kernel development list <linux-kernel@vger.kernel.org>,
stable@kernel.org, stable-review@kernel.org,
torvalds@linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
USB list <linux-usb@vger.kernel.org>,
linux-omap@vger.kernel.org
Subject: Re: [024/115] USB: prevent buggy hubs from crashing the USB stack
Date: Thu, 24 Feb 2011 10:57:39 +0200 [thread overview]
Message-ID: <20110224085735.GD3528@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1102231021210.2233-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
Hi,
On Wed, Feb 23, 2011 at 10:26:20AM -0500, Alan Stern wrote:
> In both cases, it appears that the problem is caused by the fact that
> the musb host-controller driver doesn't set the hcd->has_tt flag.
>
> Felipe, you should know where it belongs. It should be easy enough to
> add.
Sure Alan, it's attached to this mail. Compile tested only though.
Michael, would you care to give your tested-by ?
--
balbi
[-- Attachment #2: 0001-usb-musb-core-set-has_tt-flag.diff --]
[-- Type: text/x-diff, Size: 1060 bytes --]
>From 65315c60a17f83e69d01888babe4445097c8ead0 Mon Sep 17 00:00:00 2001
From: Felipe Balbi <balbi@ti.com>
Date: Thu, 24 Feb 2011 10:36:53 +0200
Subject: [PATCH] usb: musb: core: set has_tt flag
Organization: Texas Instruments\n
MUSB is a non-standard host implementation which
can handle all speeds with the same core. We need
to set has_tt flag after commit
d199c96d41d80a567493e12b8e96ea056a1350c1 (USB: prevent
buggy hubs from crashing the USB stack) in order for
MUSB HCD to continue working.
Signed-off-by: Felipe Balbi <balbi@ti.com>
---
drivers/usb/musb/musb_core.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
index 54a8bd1..c292d5c 100644
--- a/drivers/usb/musb/musb_core.c
+++ b/drivers/usb/musb/musb_core.c
@@ -1864,6 +1864,7 @@ allocate_instance(struct device *dev,
INIT_LIST_HEAD(&musb->out_bulk);
hcd->uses_new_polling = 1;
+ hcd->has_tt = 1;
musb->vbuserr_retry = VBUSERR_RETRY_COUNT;
musb->a_wait_bcon = OTG_TIME_A_WAIT_BCON;
--
1.7.4.rc2
next prev parent reply other threads:[~2011-02-24 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D64C81B.5060807@ahsoftware.de>
2011-02-23 15:26 ` [024/115] USB: prevent buggy hubs from crashing the USB stack Alan Stern
2011-02-24 8:57 ` Felipe Balbi [this message]
2011-02-24 9:15 ` Alexander Holler
[not found] ` <4D6621AB.10205-SXC+2es9fhnfWeYVQQPykw@public.gmane.org>
2011-02-24 9:16 ` Felipe Balbi
2011-02-24 17:18 ` Greg KH
2011-02-24 17:23 ` Felipe Balbi
2011-02-24 17:57 ` Alan Stern
2011-02-24 18:11 ` Alexander Holler
2011-02-24 18:24 ` Greg KH
2011-02-24 18:12 ` Greg KH
2011-02-24 18:16 ` Greg KH
2011-02-24 9:53 ` Michael Jones
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=20110224085735.GD3528@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jones@matrix-vision.de \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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