From: Chanwoo Choi <cw00.choi@samsung.com>
To: Jonghwa Lee <jonghwa3.lee@samsung.com>
Cc: linux-pm@vger.kernel.org, myungjoo.ham@samsung.com,
kyungmin.park@samsung.com
Subject: Re: [PATCH 0/3] devfreq: exynos4_bus: Update Exynos4 busfreq driver
Date: Wed, 11 Jun 2014 12:27:13 +0900 [thread overview]
Message-ID: <5397CC91.4050903@samsung.com> (raw)
In-Reply-To: <1402449476-6782-1-git-send-email-jonghwa3.lee@samsung.com>
Hi Jonghwa,
I sent already this patchset to support dt for exynos4-busfreq[1].
You can check history of exynos4-busfreq on following patchset[1].
[1] https://lkml.org/lkml/2014/3/13/58
So, I'm preparing to implement common driver to support dt of PPMU.
Thanks,
Chanwoo Choi
On 06/11/2014 10:17 AM, Jonghwa Lee wrote:
> Driver updates including devicetree supporting and some fixes.
>
> Jonghwa Lee (3):
> devfreq: exynos4_bus: Enable PPMU's source clock before use.
> devfreq: exynos4_bus: Access memory mapped I/O region via dynamic
> allocation.
> devfreq: exynos4_bus: Support DT in exynos4 busfreq driver.
>
> .../devicetree/bindings/devfreq/exynos4_bus.txt | 19 +++++
> drivers/devfreq/exynos/exynos4_bus.c | 77 +++++++++++++++++---
> 2 files changed, 87 insertions(+), 9 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/devfreq/exynos4_bus.txt
>
prev parent reply other threads:[~2014-06-11 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 1:17 [PATCH 0/3] devfreq: exynos4_bus: Update Exynos4 busfreq driver Jonghwa Lee
2014-06-11 1:17 ` [PATCH 1/3] devfreq: exynos4_bus: Enable PPMU's source clock before use Jonghwa Lee
2014-06-11 1:17 ` [PATCH 2/3] devfreq: exynos4_bus: Access memory mapped I/O region via dynamic allocation Jonghwa Lee
2014-06-11 1:17 ` [PATCH 3/3] devfreq: exynos4_bus: Support DT in exynos4 busfreq driver Jonghwa Lee
2014-06-11 3:27 ` Chanwoo Choi [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=5397CC91.4050903@samsung.com \
--to=cw00.choi@samsung.com \
--cc=jonghwa3.lee@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.