From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Abhilash Kesavan <a.kesavan@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Jonghwan Choi <jhbird.choi@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: [PATCH v5 4/4] PM: Devfreq: Add Exynos5-bus devfreq driver for Exynos5250
Date: Tue, 5 Feb 2013 18:56:31 +0900 [thread overview]
Message-ID: <CAJ0PZbT5csFuLpxTTTXqCOApYsOKM4z8r-cTAL3w3vLmA8mKvw@mail.gmail.com> (raw)
In-Reply-To: <1359980088-20799-1-git-send-email-a.kesavan@samsung.com>
On Mon, Feb 4, 2013 at 9:14 PM, Abhilash Kesavan <a.kesavan@samsung.com> wrote:
> Exynos5-bus device devfreq driver monitors PPMU counters and
> adjusts operating frequencies and voltages with OPP. ASV should
> be used to provide appropriate voltages as per the speed group
> of the SoC rather than using a constant 1.025V.
applied. thanks.
ps. Devfreq patches are stacking up at devfreq's for-rafael branch and
will be pull-requested for 3.9 soon.
>
> Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
> Cc: Jonghwan Choi <jhbird.choi@samsung.com>
> Cc: Kukjin Kim <kgene.kim@samsung.com>
> ---
> Changes since RFC v1:
> * Moved the Exynos5 PPMU driver to machine specific directory
> * Migrated to the PM QOS framework
> Changes since v2:
> * Moved the PPMU driver to drivers/devfreq/exynos
> * Fixed whitespace, commenting, empty lines in PPMU driver
> Changes since v3:
> * Removed the custom devfreq monitor and PPMU polling function
> * Moved exynos5 PPMU access functions to the devfreq driver
> Changes since v4:
> * Fixed compilation errors due to presence of devinit/devexit
> * Moved exynos ppmu header to the drivers/devfreq/exynos directory
>
--
MyungJoo Ham, Ph.D.
Mobile Software Platform Lab, DMC Business, Samsung Electronics
next prev parent reply other threads:[~2013-02-05 9:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 12:06 [PATCH 1/4] ARM: EXYNOS5: Add PPMU device tree support Abhilash Kesavan
2013-01-09 12:06 ` [PATCH 2/4] ARM: EXYNOS5: Support Exynos5-bus devfreq driver Abhilash Kesavan
2013-01-14 14:29 ` MyungJoo Ham
2013-01-18 13:23 ` [PATCH v4 " Abhilash Kesavan
2013-01-09 12:06 ` [PATCH 3/4] PM: DEVFREQ: Move exynos4 devfreq driver into a new sub-directory Abhilash Kesavan
2013-01-14 14:30 ` MyungJoo Ham
2013-01-18 13:24 ` [PATCH v4 " Abhilash Kesavan
2013-01-09 12:06 ` [PATCH 4/4] PM/Devfreq: Add Exynos5-bus devfreq driver for Exynos5250 Abhilash Kesavan
2013-01-09 14:14 ` Rajagopal Venkat
2013-01-18 13:22 ` Abhilash Kesavan
2013-01-18 13:24 ` [PATCH v4 4/4] PM: Devfreq: " Abhilash Kesavan
2013-02-03 15:47 ` Abhilash Kesavan
2013-02-04 6:41 ` myungjoo.ham
2013-02-04 8:03 ` Abhilash Kesavan
2013-02-04 12:14 ` [PATCH v5 " Abhilash Kesavan
2013-02-05 9:56 ` MyungJoo Ham [this message]
2013-01-14 14:26 ` [PATCH 1/4] ARM: EXYNOS5: Add PPMU device tree support MyungJoo Ham
2013-01-18 13:23 ` [PATCH v4 " Abhilash Kesavan
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=CAJ0PZbT5csFuLpxTTTXqCOApYsOKM4z8r-cTAL3w3vLmA8mKvw@mail.gmail.com \
--to=myungjoo.ham@samsung.com \
--cc=a.kesavan@samsung.com \
--cc=jhbird.choi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@gmail.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;
as well as URLs for NNTP newsgroup(s).