From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
sre@debian.org, sre@ring0.de,
"kernel list" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com
Subject: Re: n900 in 4.2-rc0: repeating oopses
Date: Wed, 1 Jul 2015 23:16:21 -0700 [thread overview]
Message-ID: <20150702061620.GY4156@atomide.com> (raw)
In-Reply-To: <20150701130903.GG7969@amd>
* Pavel Machek <pavel@ucw.cz> [150701 06:11]:
> On Wed 2015-07-01 03:34:22, Tony Lindgren wrote:
> >
> > Works for me after enabling the idle timeouts with the following
> > script and blanking the screen and disconnecting USB:
>
> Um. I'm forcing suspend with "echo mem > /sys/power/state" . (It
> worked in 4.1). That should just make it sleep, no autosuspend-related
> trickery... (But yes, I guess I should set up the leds and try
> autosuspend, too.)
That too works just fine for me with omap2plus_defconfig after
echo enabled > /sys/class/tty/ttyO2/power/wakeup as I have n900
in my test rack.
You probably have some additional drivers enabled?
Regards,
Tony
next prev parent reply other threads:[~2015-07-02 6:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 9:32 n900 in 4.1-rc0 Pavel Machek
2015-04-16 9:37 ` Marc Zyngier
2015-04-16 16:35 ` Tony Lindgren
2015-04-26 10:15 ` Pavel Machek
2015-04-16 16:45 ` Tyler Baker
2015-04-26 10:20 ` Pavel Machek
2015-04-27 18:58 ` Tyler Baker
2015-06-29 9:11 ` n900 in 4.2-rc0: repeating oopses Pavel Machek
2015-06-29 10:45 ` Pali Rohár
2015-06-30 9:24 ` Pavel Machek
2015-06-30 9:53 ` Pali Rohár
2015-07-01 6:59 ` Tony Lindgren
2015-07-01 7:22 ` Pali Rohár
2015-07-01 9:59 ` Pavel Machek
2015-07-01 10:34 ` Tony Lindgren
2015-07-01 13:09 ` Pavel Machek
2015-07-02 6:16 ` Tony Lindgren [this message]
2015-07-26 22:31 ` Pavel Machek
2015-07-27 7:12 ` Pali Rohár
2015-07-02 20:25 ` Pavel Machek
2015-07-26 9:26 ` Pavel Machek
2015-07-28 6:01 ` Tony Lindgren
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=20150702061620.GY4156@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@debian.org \
--cc=sre@ring0.de \
/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).