public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Anand Moon <linux.amoon@gmail.com>,
	Daniel Lezcano <daniel.lezcano@free.fr>,
	Kukjin Kim <kgene@kernel.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	Przemyslaw Marczak <p.marczak@samsung.com>,
	Kevin Hilman <khilman@linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: CPUIdle for Exynos5422 Odroid-XU3/XU4 boards.
Date: Fri, 28 Aug 2015 21:42:35 +0900	[thread overview]
Message-ID: <55E0573B.4060604@samsung.com> (raw)
In-Reply-To: <55E01D61.8020706@osg.samsung.com>

W dniu 28.08.2015 o 17:35, Javier Martinez Canillas pisze:
> Hello Bartlomiej and Lorenzo,
> 
> Thanks a lot for your explanations.
> 
> On 08/27/2015 06:58 PM, Bartlomiej Zolnierkiewicz wrote:
>
>> If somebody wants to implement a separate Exynos542x/Exynos5800
>> big.LITTLE cpuidle driver for them I see no problem with it and I'm
>> willing to help in maintaining it.
>>
> 
> Ok, I'll see if I can take a look what is needed to implement a Exynos542x CPUidle
> driver. I'm quite busy with other stuff right now but I should be less busy in a
> couple of weeks.

The only useful users of Exynos542x cpuidle would be Chromebooks.
Probably the same goes with suspend to RAM. Non-mobile devices could
leave without it.

In the same time cpuidle and S2R would require a significant amount of
work. Testing would have to be performed on Chromebooks. I have doubts
it would work on Odroid XU3.

I dug into S2R issues on Odroid XU3 and after fixing trivial imprecise
abort I don't have clue. It just dies somewhere in firmware/bootloader.
Vendor code has a lot more stuff related to suspend and testing it
one-by-one whether it fixes the issue is frustrating.

Do we really need cpuidle or S2R on Exynos542x/5800?

> 
> Maybe is a little bit out of topic but since Anand also asked about CPUFreq support,
> are you planning on re-posting your "cpufreq: add generic cpufreq driver support
> for Exynos5250/5800 platforms" [0] series?

That would be useful. Bartlomiej, do you have plans for continuing the work?

Best regards,
Krzysztof


  reply	other threads:[~2015-08-28 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANAwSgTWZ1a+j8RTiamsKaALKf+ekLVqtO6RFTLXkG=bJN4BPQ@mail.gmail.com>
     [not found] ` <CAJKOXPeFVwmRzP3YPSaJ_PtNf3L3pzXSXVqHwyYfWDYwhTmsBQ@mail.gmail.com>
     [not found]   ` <55DC38CA.9090202@osg.samsung.com>
2015-08-25 14:35     ` CPUIdle for Exynos5422 Odroid-XU3/XU4 boards Bartlomiej Zolnierkiewicz
2015-08-25 16:09       ` Lorenzo Pieralisi
2015-08-27 16:58         ` Bartlomiej Zolnierkiewicz
2015-08-28  8:35           ` Javier Martinez Canillas
2015-08-28 12:42             ` Krzysztof Kozlowski [this message]
2015-08-28 12:50               ` Bartlomiej Zolnierkiewicz
2015-10-12 19:06               ` Amit Kucheria

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=55E0573B.4060604@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=daniel.lezcano@free.fr \
    --cc=javier@osg.samsung.com \
    --cc=kgene@kernel.org \
    --cc=khilman@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux.amoon@gmail.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=p.marczak@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