From: 함명주 <myungjoo.ham@samsung.com>
To: "Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
최찬우 <cw00.choi@samsung.com>
Cc: 박경민 <kyungmin.park@samsung.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"Tomasz Figa" <t.figa@samsung.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] devfreq: exynos: generalize PPMU code
Date: Thu, 27 Mar 2014 10:08:09 +0000 (GMT) [thread overview]
Message-ID: <14716616.146541395914888684.JavaMail.weblogic@epml10> (raw)
On Sat, Mar 22, 2014 at 2:31 AM, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> wrote:
> Hi,
>
> This patch series generalizes PPMU support for Exynos devfreq
> drivers.
>
> It is based on top of "devfreq: exynos: Fix minor issue and code
> clean to remove legacy method" patch series from Chanwoo Choi
> (https://lkml.org/lkml/2014/3/19/713).
>
> Please note that the patches were only compile tested because
> Exynos devfreq drivers don't work yet in the upstream kernels
> (FWIW these changes were briefly tested with the internal tree
> which has working devfreq drivers).
Hi Blartlomiej,
Thank you.
I'll merge this into devfreq's for-next.
Anyway, days ago, I had a short discussion with Chanwoo about
providing some common interface for PPMU-like devices
(sort of sub device of devfreq device) that provide usage statistics.
At this stage, I roughly guess that such a device driver (or whatever
entity it is) may be simply a helper for filling out the "get_dev_status" callback.
It is because devfreq's PPMU usage is limited to getting get_dev_status().
As you had done something on PPMU, I guess you may have some
idea on this.
Cheers,
MyungJoo.
>
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
>
>
> Bartlomiej Zolnierkiewicz (3):
> devfreq: exynos4: introduce struct busfreq_ppmu_data
> devfreq: exynos5: introduce struct busfreq_ppmu_data
> devfreq: exynos: make more PPMU code common
>
> Chanwoo Choi (1):
> devfreq: exynos4: use common PPMU code
>
> drivers/devfreq/exynos/Makefile | 2 +-
> drivers/devfreq/exynos/exynos4_bus.c | 176 +++++++++--------------------------
> drivers/devfreq/exynos/exynos5_bus.c | 94 +++++--------------
> drivers/devfreq/exynos/exynos_ppmu.c | 60 ++++++++++++
> drivers/devfreq/exynos/exynos_ppmu.h | 8 ++
> 5 files changed, 135 insertions(+), 205 deletions(-)
>
> --
> 1.8.2.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
MyungJoo Ham, Ph.D.
System S/W Lab, S/W Center, Samsung Electronics
next reply other threads:[~2014-03-27 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 10:08 함명주 [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-21 17:31 [PATCH 0/4] devfreq: exynos: generalize PPMU code Bartlomiej Zolnierkiewicz
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=14716616.146541395914888684.JavaMail.weblogic@epml10 \
--to=myungjoo.ham@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=t.figa@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;
as well as URLs for NNTP newsgroup(s).