From: Tomeu Vizoso <tomeu@tomeuvizoso.net>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Chris Ball <chris@printf.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org, Kukjin Kim <kgene@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-samsung-soc@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [RFC 0/3] mmc: Add dynamic frequency scaling
Date: Thu, 15 Jan 2015 16:25:19 +0100 [thread overview]
Message-ID: <CAAObsKCUed_-XndZC_-mn_MWt5f2h0OUff_FHC30W4+2VQxsQg@mail.gmail.com> (raw)
In-Reply-To: <1421054585-9032-1-git-send-email-k.kozlowski@samsung.com>
On 12 January 2015 at 10:23, Krzysztof Kozlowski
<k.kozlowski@samsung.com> wrote:
> Hi,
>
>
> I would like to hear some comments about idea of scaling MMC clock
> frequency. The basic idea is to lower the clock when device is
> completely idle or not busy enough.
>
> The patchset adds MMC card as a devfreq device and uses simple_ondemand
> as governor. In idle this gave benefits (less energy consumed during
> idle):
> 1. Trats2 (Exynos4412): 2.6%
> 2. Rinato (Exynos3250): 1%
>
> but (especially on Rinato) it had impact on performance (probably
> because ondemand triggering a little to late). What is interesting
> manually changing the clock (without this patchset) gave slightly
> bigger benefits. Maybe the devfreq introduces noticeable overhead?
Could it be because of the polling interval being too long thus it
being too slow to ramp up?
That's a problem with all polling devfreq drivers, it has been
proposed before using pm_qos to to reduce the polling interval when
some event indicates that the utilization may grow abruptly in the
near future.
I don't think pm_qos is the best mechanism for that, maybe something
new needs to be devised.
Regards,
Tomeu
>
> Comments are welcomed. Maybe on other platforms this has bigger impact?
>
> Best regards,
> Krzysztof
>
>
> Krzysztof Kozlowski (3):
> mmc: Add dynamic frequency scaling
> ARM: dts: Specify MSHC realistic clocks and use frequency scaling
> ARM: dts: Use frequency scaling for MSHC
>
> Documentation/devicetree/bindings/mmc/mmc.txt | 2 +
> arch/arm/boot/dts/exynos3250-rinato.dts | 1 +
> arch/arm/boot/dts/exynos4412-trats2.dts | 4 +-
> drivers/mmc/card/block.c | 247 ++++++++++++++++++++++++++
> drivers/mmc/core/Kconfig | 16 ++
> drivers/mmc/core/core.h | 1 -
> drivers/mmc/core/host.c | 2 +
> include/linux/mmc/card.h | 8 +
> include/linux/mmc/host.h | 3 +
> 9 files changed, 282 insertions(+), 2 deletions(-)
>
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2015-01-15 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 9:23 [RFC 0/3] mmc: Add dynamic frequency scaling Krzysztof Kozlowski
2015-01-12 9:23 ` [RFC 1/3] " Krzysztof Kozlowski
2015-01-12 9:23 ` [RFC 2/3] ARM: dts: Specify MSHC realistic clocks and use " Krzysztof Kozlowski
2015-01-12 9:23 ` [RFC 3/3] ARM: dts: Use frequency scaling for MSHC Krzysztof Kozlowski
2015-01-15 8:20 ` [RFC 0/3] mmc: Add dynamic frequency scaling Ulf Hansson
2015-01-15 9:20 ` Krzysztof Kozlowski
2015-01-15 10:04 ` Ulf Hansson
2015-01-17 23:52 ` Mike Turquette
2015-01-15 15:25 ` Tomeu Vizoso [this message]
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=CAAObsKCUed_-XndZC_-mn_MWt5f2h0OUff_FHC30W4+2VQxsQg@mail.gmail.com \
--to=tomeu@tomeuvizoso.net \
--cc=b.zolnierkie@samsung.com \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).