From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: EXYNOS4: Add DMC1, allow PPMU access for DMC.
Date: Mon, 19 Dec 2011 00:58:15 +0900 [thread overview]
Message-ID: <4EEE0D97.9060001@samsung.com> (raw)
In-Reply-To: <CAH9JG2VS3_dBar-wMAA=9wn_+hT0FgFHDsnBsOWTDGJE_v_qKA@mail.gmail.com>
On 12/16/11 17:24, Kyungmin Park wrote:
> Hi Mr. Kim,
>
> It's maybe missing for v3.3 merge at samsung soc.
> Please give your opinion, how to handle it?
Looks ok to me at the moment, and as a note, I'm sorting it out now.
>
> If you don't mind it, it can merge it by devfreq.
Hmm, I think, it should be handled in samsung tree to avoid useless
conflicts with others. And if you need this in the devfreq tree now,
please let me know so that I can create topic branch for it.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
> On 12/1/11, MyungJoo Ham<myungjoo.ham@samsung.com> wrote:
>> - Add DMC1
>> - Enlarge address space for DMC from 4k to 64k so that PPMU registers
>> may be accessed.
>>
>> Signed-off-by: MyungJoo Ham<myungjoo.ham@samsung.com>
>> Signed-off-by: Kyungmin Park<kyungmin.park@samsung.com>
>> ---
>> arch/arm/mach-exynos/cpu.c | 7 ++++++-
>> arch/arm/mach-exynos/include/mach/map.h | 1 +
>> 2 files changed, 7 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/arm/mach-exynos/cpu.c b/arch/arm/mach-exynos/cpu.c
>> index 90ec247..8bdcba9 100644
>> --- a/arch/arm/mach-exynos/cpu.c
>> +++ b/arch/arm/mach-exynos/cpu.c
>> @@ -108,7 +108,12 @@ static struct map_desc exynos4_iodesc[] __initdata = {
>> }, {
>> .virtual = (unsigned long)S5P_VA_DMC0,
>> .pfn = __phys_to_pfn(EXYNOS4_PA_DMC0),
>> - .length = SZ_4K,
>> + .length = SZ_64K,
>> + .type = MT_DEVICE,
>> + }, {
>> + .virtual = (unsigned long)S5P_VA_DMC1,
>> + .pfn = __phys_to_pfn(EXYNOS4_PA_DMC1),
>> + .length = SZ_64K,
>> .type = MT_DEVICE,
>> }, {
>> .virtual = (unsigned long)S5P_VA_SROMC,
>> diff --git a/arch/arm/mach-exynos/include/mach/map.h
>> b/arch/arm/mach-exynos/include/mach/map.h
>> index 058541d..870a980 100644
>> --- a/arch/arm/mach-exynos/include/mach/map.h
>> +++ b/arch/arm/mach-exynos/include/mach/map.h
>> @@ -57,6 +57,7 @@
>> #define EXYNOS4_PA_KEYPAD 0x100A0000
>>
>> #define EXYNOS4_PA_DMC0 0x10400000
>> +#define EXYNOS4_PA_DMC1 0x10410000
>>
>> #define EXYNOS4_PA_COMBINER 0x10440000
>>
>> --
>> 1.7.4.1
next prev parent reply other threads:[~2011-12-18 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 9:05 [PATCH 0/4] PM/Devfreq: Exynos4210 Bus/VDD_int MyungJoo Ham
2011-12-01 9:05 ` [PATCH 1/4] ARM: EXYNOS4: Add DMC1, allow PPMU access for DMC MyungJoo Ham
2011-12-02 9:01 ` Kukjin Kim
2011-12-02 9:13 ` Kyungmin Park
2011-12-03 9:27 ` Kukjin Kim
2011-12-16 8:24 ` Kyungmin Park
2011-12-18 15:58 ` Kukjin Kim [this message]
2011-12-01 9:05 ` [PATCH 2/4] PM/Devfreq: Add Exynos4210-bus device DVFS driver MyungJoo Ham
2011-12-01 9:05 ` [PATCH 3/4] ARM Exynos4210-Nuri: remove compiler errors MyungJoo Ham
2011-12-02 8:59 ` Kukjin Kim
2011-12-02 9:23 ` MyungJoo Ham
2011-12-03 9:26 ` Kukjin Kim
2011-12-05 4:55 ` MyungJoo Ham
2011-12-01 9:05 ` [PATCH 4/4] ARM Exynos4210-Nuri: support Exynos4210-bus Devfreq driver MyungJoo Ham
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=4EEE0D97.9060001@samsung.com \
--to=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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).