From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
s.nawrocki@samsung.com
Subject: Re: Question about Odroid XU4 cpuidle
Date: Wed, 10 Jun 2020 16:02:38 +0200 [thread overview]
Message-ID: <20200610140238.GA31473@kozik-lap> (raw)
In-Reply-To: <570c73f2-d9d8-4ae1-3caf-829547232e48@arm.com>
On Wed, Jun 10, 2020 at 02:18:12PM +0100, Lukasz Luba wrote:
> Hi Krzysztof, Bartek,
>
> I recall that you have been working on some cpuidle code for Exynos(4?).
>
> I have a question regarding CPUIdle driver for Odroid XU4.
> I use the board with LISA tests for EAS, but missing at
> least idle state 0 cause errors (please see the log below).
>
> Currently the system does not report any idle driver and the state 0
> is missing in: /sys/devices/system/cpu/cpu0/cpuidle/state0/
The state 0 long time ago was WFI. It was kind of meaningless so it it
was dropped.
>
> I am using driver CONFIG_ARM_BIG_LITTLE_CPUIDLE but the
> boot stops silently while trying to init the cpu idle devices in there.
> I carry on with a workaround that just removes idle state[1] and set
> state_count=1 in the big and little structures.
Try earlyprintk.
In general, the big-little cpuidle driver should work... or rather: long
time ago it was working. It requires proper support from early stages
(BL1, secure monitor) but this should be already in standard Odroid.
I just saw there:
/* Start at index 1, index 0 standard WFI */
so maybe it was not updated properly to removal of WFI?
I think no one uses this driver so it might be not well tested and not
that useful.
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-06-10 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 13:18 Question about Odroid XU4 cpuidle Lukasz Luba
2020-06-10 14:02 ` Krzysztof Kozlowski [this message]
2020-06-10 14:09 ` Marek Szyprowski
2020-06-10 14:30 ` Lukasz Luba
2020-06-15 12:45 ` Marek Szyprowski
2020-06-15 15:39 ` Lukasz Luba
2020-06-10 14:27 ` Lukasz Luba
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=20200610140238.GA31473@kozik-lap \
--to=krzk@kernel.org \
--cc=a.hajda@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=m.szyprowski@samsung.com \
--cc=s.nawrocki@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox