From: "Timo Sigurdsson" <public_timo.s@silentcreek.de>
To: maxime.ripard@free-electrons.com
Cc: wens@csie.org, julian.calaby@gmail.com, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
monnier@iro.umontreal.ca
Subject: Re: [linux-sunxi] [PATCH] ARM: dts: sunxi: Raise minimum CPU voltage for sun7i-a20 to a level all boards can supply
Date: Tue, 4 Aug 2015 10:51:30 +0200 (CEST) [thread overview]
Message-ID: <20150804085130.602FA6C83EF9@dd34104.kasserver.com> (raw)
In-Reply-To: <20150803093420.GC2564@lukather>
Hi Maxime,
Maxime Ripard schrieb am 03.08.2015 11:34:
> On Mon, Aug 03, 2015 at 11:03:52AM +0200, Timo Sigurdsson wrote:
>> Julian Calaby schrieb am 03.08.2015 06:22:
>> > My only real objection here is are there boards that can go down to
>> > 0.9v and if so, won't this change make them less power efficient in
>> > the almost-idle case? And are those power savings enough to justify
>> > not accepting this patch?
>>
>> It will probably make those boards less power efficient, yes. On the
>> other hand, boards that have their CPU regulator set to min. 1.0V might
>> also draw more power because the lowest frequency is not available,
>> even though the savings due to frequency are likely to be lower than
>> the savings due to voltage.
>
> Guys, isn't this whole discussion a bit moot? We're not doing any kind
> of power management but cpufreq, so maybe there's a lot more to do
> before we actually can have these kind of arguments?
>
> Plus this OPP has never been used anyway, so this patch is not going
> to increase the power consumption either.
You are right. When I wrote that, I was under the impression that the
Olinuxino Lime 2 board at least used this setting since it has has a cpu
regulator defined to go as low as 0.7V. But now I checked again and see
the regulator is not referenced in the cpu node, so I guess cpufreq
doesn't use it. So, this discussion was really hypothetical and more
importantly, as you mentioned, it's an out-of-spec opp that shouldn't
be supported anyway.
Thanks,
Timo
next prev parent reply other threads:[~2015-08-04 8:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 19:23 Timo Sigurdsson
2015-08-02 23:35 ` [linux-sunxi] " Julian Calaby
2015-08-03 2:37 ` Chen-Yu Tsai
2015-08-03 4:22 ` Julian Calaby
2015-08-03 4:26 ` Chen-Yu Tsai
2015-08-03 9:03 ` Timo Sigurdsson
2015-08-03 9:34 ` Maxime Ripard
2015-08-03 9:36 ` Julian Calaby
2015-08-04 8:51 ` Timo Sigurdsson [this message]
2015-08-03 9:28 ` Maxime Ripard
2015-08-03 8:37 ` Timo Sigurdsson
2015-08-03 9:23 ` Maxime Ripard
2015-08-03 9:16 ` Maxime Ripard
2015-08-03 9:13 ` Maxime Ripard
2015-08-04 8:38 ` Timo Sigurdsson
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=20150804085130.602FA6C83EF9@dd34104.kasserver.com \
--to=public_timo.s@silentcreek.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=julian.calaby@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=monnier@iro.umontreal.ca \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.org \
/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
all inboxes | Powered by JetHome®