From: Andreas Kemnade <andreas@kemnade.info>
To: Merlijn Wajer <merlijn@wizzup.org>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>, Adam Ford <aford173@gmail.com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dev Null <devnull@uvos.xyz>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: Nokia N900 OFF mode regression between v5.10 and v5.11
Date: Sat, 11 Dec 2021 08:54:03 +0100 [thread overview]
Message-ID: <20211211085403.3c1fcb0d@aktux> (raw)
In-Reply-To: <43cac03a-53c2-83dd-e1b0-4d25920d9095@wizzup.org>
Hi,
On Sat, 11 Dec 2021 00:20:24 +0100
Merlijn Wajer <merlijn@wizzup.org> wrote:
> Hi Tony, Adam,
>
> I noticed that after I fixed the OFF mode regression between v5.9 and
> v5.10 that there are another one between v5.10 and v5.11. Fortunately,
> much like the other change it can be worked around with a config change,
> and in fact it looks like the commit identified by git bisect is indeed
> just a commit to change omap2plus_defconfig.
>
> a82820fcd079e38309403f595f005a8cc318a13c ("ARM: omap2plus_defconfig:
> Enable OMAP3_THERMAL") prevents the N900 from entering OFF mode pretty
> much all the time (I've seen scenarios with OFF:2,RET:500), but with the
> config change reverted, stuff like this is more common: OFF:13,RET:2
>
> We will probably to keep the thermal features enabled, but maybe we can
> figure out why it causes the SoC to not enter sleep modes?
well, it was enabled after people agreed that is fixed... including me.
It was wrongly enabled some time before, then disabled again, fixed and
reenabled.
The mentioned commit was just after the fix. So what is different now?
Regards,
Andreas
next prev parent reply other threads:[~2021-12-11 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 23:20 Nokia N900 OFF mode regression between v5.10 and v5.11 Merlijn Wajer
2021-12-11 7:54 ` Andreas Kemnade [this message]
2021-12-11 10:23 ` Merlijn Wajer
2021-12-11 10:43 ` Andreas Kemnade
2021-12-13 5:54 ` Tony Lindgren
2021-12-11 10:43 ` Merlijn Wajer
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=20211211085403.3c1fcb0d@aktux \
--to=andreas@kemnade.info \
--cc=aaro.koskinen@iki.fi \
--cc=aford173@gmail.com \
--cc=devnull@uvos.xyz \
--cc=hns@goldelico.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=pavel@ucw.cz \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.