Re: Tiny BL switcher compatibility issue with PMU on non-BL SoC

2013-05-29 Thread Amit Kucheria
On Thu, May 30, 2013 at 7:36 AM, Andy Green wrote: > Hi - > > We're using one kernel binary with BL Switcher enabled in config, but able > to work on SoC without Big Little. > > This is OK except where the BL patches touch the PMU driver. It makes an > assumption about BL configured == in use whi

Re: [PATCH V8 0/3] USB: OHCI: Start splitting up the driver

2013-05-29 Thread Manjunath Goudar
On 30 May 2013 03:32, Arnd Bergmann wrote: > On Wednesday 29 May 2013, Alan Stern wrote: > > > > On Wed, 29 May 2013, Arnd Bergmann wrote: > > > > > On Wednesday 29 May 2013 12:21:02 Alan Stern wrote: > > > > > > > > Those error messages are annoying; they don't use dev_err(), so they > > > > don

Tiny BL switcher compatibility issue with PMU on non-BL SoC

2013-05-29 Thread Andy Green
Hi - We're using one kernel binary with BL Switcher enabled in config, but able to work on SoC without Big Little. This is OK except where the BL patches touch the PMU driver. It makes an assumption about BL configured == in use which is not true. PMU init fails and when you try to use per

Re: [PATCH V8 0/3] USB: OHCI: Start splitting up the driver

2013-05-29 Thread Arnd Bergmann
On Wednesday 29 May 2013, Alan Stern wrote: > > On Wed, 29 May 2013, Arnd Bergmann wrote: > > > On Wednesday 29 May 2013 12:21:02 Alan Stern wrote: > > > > > > Those error messages are annoying; they don't use dev_err(), so they > > > don't include the device and driver names. There's no way to

Re: [PATCH V8 0/3] USB: OHCI: Start splitting up the driver

2013-05-29 Thread Alan Stern
On Wed, 29 May 2013, Arnd Bergmann wrote: > On Wednesday 29 May 2013 12:21:02 Alan Stern wrote: > > > > Those error messages are annoying; they don't use dev_err(), so they > > don't include the device and driver names. There's no way to know what > > they refer to. I rather suspect they come f

Re: [PATCH V8 0/3] USB: OHCI: Start splitting up the driver

2013-05-29 Thread Arnd Bergmann
On Wednesday 29 May 2013 12:21:02 Alan Stern wrote: > > Those error messages are annoying; they don't use dev_err(), so they > don't include the device and driver names. There's no way to know what > they refer to. I rather suspect they come from the usbaudio driver. That makes sense. I have a

Re: [PATCH V8 0/3] USB: OHCI: Start splitting up the driver

2013-05-29 Thread Alan Stern
On Tue, 28 May 2013, Arnd Bergmann wrote: > Seems to basically work now, but I'm getting run-time errors after > loading the driver, with patch 1/3 applied: > > [15916.438452] input: Logitech USB-PS/2 Optical Mouse as > /devices/pci:00/:00:12.0/usb3/3-1/3-1:1.0/input/input26 > [15916.438

Re: [PATCH] cpuidle: arm_big_little: pass target residency to mcpm

2013-05-29 Thread Sebastian Capella
Hi Guys, Sorry, I think the conversation went pretty far from my patch. Concerning my original patch, do you have any more ideas or concerns? I'm not sure I have a clear idea what, if anything, needs to be changed. I was able to verify it on the TC2 platform without issue. Thanks again for all