* Tony Lindgren [150831 14:02]:
>
> And I must have tested next-20150827 instead of next-20150828. Or
> else it does not happen on every boot. In any case, I'm now getting
> the following on next-20150831 most of the time:
>
> [9.493133] omap_hsmmc 4809c000.mmc: using
hsmmc driver instead for
now or revert some patches to remove the dependency and get things working.
And I must have tested next-20150827 instead of next-20150828. Or
else it does not happen on every boot. In any case, I'm now getting
the following on next-20150831 most of the time:
[9.493133]
while booting AM437x device, the following splat
triggered:
[ 12.005238] ===
[ 12.009749] [ INFO: suspicious RCU usage. ]
[ 12.014116] 4.2.0-next-20150831 #1154 Not tainted
[ 12.019050] ---
[ 12.023408] security/device_cgroup.c:405
Hi,
On Mon, Aug 31, 2015 at 11:41:59AM -0500, Felipe Balbi wrote:
> On Mon, Aug 31, 2015 at 03:11:58PM +0200, Yegor Yefremov wrote:
> > Hi Felipe,
> >
> > On Fri, Aug 7, 2015 at 12:57 PM, Yegor Yefremov
> > wrote:
> > > On Fri, Aug 7, 2015 at 12:16 PM, Yegor Yefremov
> > > wrote:
> > >> On Thu,
On 10/08/15 17:56, Adam Lee wrote:
> Yes I will do a better job in following the patch submission conventions.
> Thanks for your comment Jonathan.
>
> @Sebastian, let me know if you have any concerns with the patch.
This has been sat around for long enough that I suspect Sebastian isn't
going to r
Hello.
On 08/31/2015 05:03 PM, Grygorii Strashko wrote:
The interrupt handler may not be available when smsc911x probes if the
interrupt handler is a GPIO controller for example. Let's fix that
by adding handling for -EPROBE_DEFER.
Cc: Steve Glendinning
Signed-off-by: Tony Lindgren
---
On Mon, Aug 31, 2015 at 03:11:58PM +0200, Yegor Yefremov wrote:
> Hi Felipe,
>
> On Fri, Aug 7, 2015 at 12:57 PM, Yegor Yefremov
> wrote:
> > On Fri, Aug 7, 2015 at 12:16 PM, Yegor Yefremov
> > wrote:
> >> On Thu, Aug 6, 2015 at 4:21 PM, Felipe Balbi wrote:
> >>> HI,
> >>>
> >>> On Thu, Aug 06,
Hi
On Thu, 16 Jul 2015, R, Vignesh wrote:
> On 07/16/2015 03:24 AM, Paul Walmsley wrote:
> >
> > On Wed, 3 Jun 2015, Vignesh R wrote:
> >
> >> Add hwmod entries for the PWMSS on DRA7.
> >>
> >> Set l4_root_clk_div as the main_clk of PWMSS. It is fixed-factored clock
> >> equal to L4PER2_L3_GICL
Hi,
This series add support to DWC3 core to conserve
power during system sleep by setting the USB
DRVVBUS line to a lower power consuming state.
Tested to make sure USB host and device works on
AM437x with v4.2. Tested for power savings on v4.1
kernel where there is an implementation of suspend-
Add support for USB DRVVBUS pinctrl state change during
suspend/resume. This helps is conserving power during
system sleep.
Signed-off-by: Sekhar Nori
---
drivers/usb/dwc3/core.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index ff577
From: Dave Gerlach
Add pinctrl default and sleep states for each usb device.
The only pin that can be controlled is USB_DRVVBUS, this
must be set to MUX_MODE7 (gpio) during sleep to conserve
power.
Signed-off-by: Dave Gerlach
[nsek...@ti.com: move pins to core dwc3]
Signed-off-by: Sekhar Nori
On Mon, Aug 31, 2015 at 04:14:07PM +0530, Kishon Vijay Abraham I wrote:
> On Tuesday 25 August 2015 07:20 PM, Mark Brown wrote:
> > On Tue, Aug 25, 2015 at 01:03:04PM +0300, Grygorii Strashko wrote:
> >> On 08/19/2015 09:11 PM, Mark Brown wrote:
> >>> So substract this address from the start of th
On 08/31/2015 05:11 PM, Tony Lindgren wrote:
> * Grygorii Strashko [150831 02:07]:
>> Hi Tony,
>>
>> On 08/28/2015 09:44 PM, Tony Lindgren wrote:
>>> Currently we gpio-omap breaks if gpiochip_add() returns -EPROBE_DEFER:
>>>
>>> [0.57] gpiochip_add: GPIOs 0..31 (gpio) failed to register
>>
On Mon, Aug 31, 2015 at 08:46:46AM -0500, Michael Welling wrote:
> On Mon, Aug 31, 2015 at 09:53:55AM +0100, Mark Brown wrote:
> > On Sun, Aug 30, 2015 at 11:44:45AM -0500, Michael Welling wrote:
> > > The patch is currently sitting in linux-next.
> > > Not sure why it wasn't merged with 4.2.0-rc
* Grygorii Strashko [150831 02:07]:
> Hi Tony,
>
> On 08/28/2015 09:44 PM, Tony Lindgren wrote:
> >Currently we gpio-omap breaks if gpiochip_add() returns -EPROBE_DEFER:
> >
> >[0.57] gpiochip_add: GPIOs 0..31 (gpio) failed to register
> >[0.57] omap_gpio 4831.gpio: Could not
On 08/30/2015 12:33 AM, Sergei Shtylyov wrote:
> Hello.
>
> On 8/28/2015 9:50 PM, Tony Lindgren wrote:
>
>> The interrupt handler may not be available when smsc911x probes if the
>> interrupt handler is a GPIO controller for example. Let's fix that
>> by adding handling for -EPROBE_DEFER.
>
>> C
On Mon, Aug 31, 2015 at 09:53:55AM +0100, Mark Brown wrote:
> On Sun, Aug 30, 2015 at 11:44:45AM -0500, Michael Welling wrote:
>
> > The patch is currently sitting in linux-next.
>
> > Not sure why it wasn't merged with 4.2.0-rc8.
>
> You didn't indicate that it was a bug fix for Linus rather th
Hi Felipe,
On Fri, Aug 7, 2015 at 12:57 PM, Yegor Yefremov
wrote:
> On Fri, Aug 7, 2015 at 12:16 PM, Yegor Yefremov
> wrote:
>> On Thu, Aug 6, 2015 at 4:21 PM, Felipe Balbi wrote:
>>> HI,
>>>
>>> On Thu, Aug 06, 2015 at 09:40:26AM +0200, Yegor Yefremov wrote:
I performed a stress test with
Hi Mark,
On Tuesday 25 August 2015 07:20 PM, Mark Brown wrote:
> On Tue, Aug 25, 2015 at 01:03:04PM +0300, Grygorii Strashko wrote:
>> On 08/19/2015 09:11 PM, Mark Brown wrote:
>
>>> So substract this address from the start of the resource to get the
>>> offset? Or provide a wrapper function in
Hi Tony,
On 08/28/2015 09:44 PM, Tony Lindgren wrote:
Currently we gpio-omap breaks if gpiochip_add() returns -EPROBE_DEFER:
[0.57] gpiochip_add: GPIOs 0..31 (gpio) failed to register
[0.57] omap_gpio 4831.gpio: Could not register gpio chip -517
...
[3.67] omap_gpio
On Sun, Aug 30, 2015 at 11:44:45AM -0500, Michael Welling wrote:
> The patch is currently sitting in linux-next.
> Not sure why it wasn't merged with 4.2.0-rc8.
You didn't indicate that it was a bug fix for Linus rather than a fix
for recent development :(
signature.asc
Description: Digital si
21 matches
Mail list logo
