[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170321153851.GA10760@atomide.com>
Date: Tue, 21 Mar 2017 08:38:52 -0700
From: Tony Lindgren <tony@...mide.com>
To: Pavel Machek <pavel@....cz>
Cc: pali.rohar@...il.com, sre@...nel.org,
kernel list <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-omap@...r.kernel.org, khilman@...nel.org,
aaro.koskinen@....fi, ivo.g.dimitrov.75@...il.com,
patrikbachan@...il.com, serge@...lyn.com, abcloriens@...il.com
Subject: Re: N900 failure in next-20170321
* Pavel Machek <pavel@....cz> [170321 06:59]:
> Hi!
>
> Tony asked me to test linux-next from time to time. I did... today I
> moved from next-20170309 to next-20170321. Kernel boots and seems to
> work fine (including audio and X startup), but if I leave it sitting
> for a while RGB LED reverts from "system alive" to charging indication
> that was disabled before and system does not react to any input.
>
> Any ideas?
Not much there I could see affecting this.. Try reverting commit
179125085bd4 ("ARM: OMAP3: Fix smartreflex platform data regression")?
Maybe smartreflex now attempts to do something but we're missing
or have wrong dts configuration for n900?
Regards,
Tony
Powered by blists - more mailing lists