Hi Jiri, On Tue, 16 Jun 2015 10:51:55 +0200 Jiří Prchal <jiri.prchal@xxxxxxxxxxx> wrote: > > > On 13.6.2015 13:13, Boris Brezillon wrote: > > On Sat, 13 Jun 2015 13:09:56 +0200 > > Boris Brezillon <boris.brezillon@xxxxxxxxxxxxxxxxxx> wrote: > > > >> Hi Jiri, > >> > >> On Fri, 12 Jun 2015 11:30:20 +0200 > >> Jiří Prchal <jiri.prchal@xxxxxxxxxxx> wrote: > >> > >>> > >>> > >>> On 11.6.2015 15:53, Alan Stern wrote: > >>>> On Thu, 11 Jun 2015, Jiří Prchal wrote: > >>>> > >>>>> Hi all, > >>>>> I discovered some bug when I change kernel from 3.18.13 to 3.18.14. I have board with usb hub CY7C65632 on it. > >>>>> In .13 it works fine but in .14 it repeats this message: > >>>>> [ 19.170000] usb 2-3: new full-speed USB device number 56 using at91_ohci > >>>>> and devices connected to usb through hub doesn't appear at all. > >>>> > >>>>> Any idea? > >>>> > >>>> Try using git bisect to find the commit which caused this problem to > >>>> start. > >>> > >>> This is result: > >>> Bisecting: 0 revisions left to test after this (roughly 0 steps) > >>> [ae74ea64ccdb8b99ee2618b58020263d5b1d9b22] clk: at91: usb: propagate rate modification to the parent clk > >> > >> > >> Actually when bisecting you found a bug that has been fixed before > >> 3.18.14 was released (see this commit [1]). > >> This being said, the prototype mismatch fix does not seem to fix all > >> the mismatches (seems the ->determine_rate() has been changed in 3.19 > >> too, and the prototype mismatch patch was a backport of a 3.19 fix). > >> > >> Anyway, you'll find below a patch supposed to fix the remaining bug. > > > > I forgot to disable the line wrapper in my email client, here is the > > same patch without the wrapped lines: > > Aplied to 3.18.14 and it helped! Thanks for testing, I'll send this patch to Sacha and the stable ML. Best Regards, Boris -- Boris Brezillon, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
