From: Daniel Mack <zonque@gmail.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Felipe Balbi <balbi@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: v3.11-rc1 USB regressions
Date: Tue, 16 Jul 2013 20:30:21 +0200 [thread overview]
Message-ID: <51E5913D.3080205@gmail.com> (raw)
In-Reply-To: <20130716182601.GB14385@blackmetal.musicnaut.iki.fi>
On 16.07.2013 20:26, Aaro Koskinen wrote:
> Hi,
>
> On Tue, Jul 16, 2013 at 11:22:47AM +0300, Felipe Balbi wrote:
>>> On Tue, Jul 16, 2013 at 12:30:00PM +0530, Kishon Vijay Abraham I wrote:
>>>> On Tuesday 16 July 2013 12:03 PM, Daniel Mack wrote:
>>>>> Hi Aaro,
>>>>>
>>>>> On 16.07.2013 00:56, Aaro Koskinen wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I think USB tree introduced regressions in v3.11-rc1, at least for some
>>>>>> OMAP devices using legacy boot.
>>>>>
>>>>> Thanks for checking the tree so early.
>>>>>
>>>>>> I have only bisected these; I have no
>>>>>> idea what the real fixes are but the following reverts make Nokia OMAP2+
>>>>>> boards again usable for kernel development work (they need working USB
>>>>>> connection for interacting with the device):
>>>>>>
>>>>>> 1) USB peripheral mode (g_ether) is broken on Nokia N900, N950 and N9
>>>>>> (USB_MUSB_OMAP2PLUS). To make it it work, I need to revert three
>>>>>> commits:
>>>>>>
>>>>>> 09fc7d22b024692b2fe8a943b246de1af307132b
>>>>>> usb: musb: fix incorrect usage of resource pointer
>>>>>> (Reverting this fixes the g_ether probe failure "couldn't find
>>>>>> an available UDC")
>>>>
>>>> I've posted a patch fixing the issue
>>>> http://comments.gmane.org/gmane.linux.usb.general/89541
>>>> There were some comments on it. I'll be posting a new version for it.
>>>
>>> hmm, n8x0 used tusb6010, so perhaps a similar patch needs to be cooked
>>> for that too. Right now, let's to the minimum fix, which is just to
>>> increment the array size to 3 and for v3.12 we do the changes that I
>>> suggested.
>>
>> this should solve the problem on n900 and n8x0, it's pretty much
>> kishon's original patch, so I guess it deserves his authorship:
>
> Thanks, and yes it fixes this issue. I tested both N900 and N800, so
> feel free to add my Tested-by.
Together with my patch I take it? Does your Tested-by apply to this one
as well?
Thanks,
Daniel
next prev parent reply other threads:[~2013-07-16 18:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 22:56 v3.11-rc1 USB regressions Aaro Koskinen
2013-07-16 6:33 ` Daniel Mack
2013-07-16 7:00 ` Kishon Vijay Abraham I
2013-07-16 8:08 ` Felipe Balbi
2013-07-16 8:22 ` Felipe Balbi
2013-07-16 18:26 ` Aaro Koskinen
2013-07-16 18:30 ` Daniel Mack [this message]
2013-07-16 18:34 ` Aaro Koskinen
[not found] ` <51E4E922.2040707-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-07-16 17:30 ` Aaro Koskinen
2013-07-16 17:57 ` Aaro Koskinen
2013-07-24 18:51 ` Aaro Koskinen
2013-07-24 19:04 ` Daniel Mack
2013-07-25 0:30 ` Aaro Koskinen
[not found] ` <20130725003029.GD26943-R3WNPi76c83LsdW6vOPryG4HOFkwEHDbMR2xtNvyitY@public.gmane.org>
2013-07-25 9:08 ` Daniel Mack
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=51E5913D.3080205@gmail.com \
--to=zonque@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).