From: Pankaj Dubey <pankaj.dubey@samsung.com>
To: linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: kgene.kim@samsung.com, k.kozlowski@samsung.com,
thomas.ab@samsung.com, p.fedin@samsung.com,
andi.shyti@samsung.com, Pankaj Dubey <pankaj.dubey@samsung.com>,
Kukjin Kim <kgene@kernel.org>
Subject: [RESEND PATCH v5 1/8] ARM: EXYNOS: remove unused static mapping of CMU for exynos5
Date: Sat, 12 Dec 2015 13:13:55 +0530 [thread overview]
Message-ID: <1449906242-20843-2-git-send-email-pankaj.dubey@samsung.com> (raw)
In-Reply-To: <1449906242-20843-1-git-send-email-pankaj.dubey@samsung.com>
Remove unused static mapping of exynos5 CMU and related code.
Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Signed-off-by: Kukjin Kim <kgene@kernel.org>
---
arch/arm/mach-exynos/exynos.c | 5 -----
arch/arm/mach-exynos/include/mach/map.h | 1 -
2 files changed, 6 deletions(-)
diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
index 1c47aee..524aa6f 100644
--- a/arch/arm/mach-exynos/exynos.c
+++ b/arch/arm/mach-exynos/exynos.c
@@ -70,11 +70,6 @@ static struct map_desc exynos5_iodesc[] __initdata = {
.pfn = __phys_to_pfn(EXYNOS5_PA_SROMC),
.length = SZ_4K,
.type = MT_DEVICE,
- }, {
- .virtual = (unsigned long)S5P_VA_CMU,
- .pfn = __phys_to_pfn(EXYNOS5_PA_CMU),
- .length = 144 * SZ_1K,
- .type = MT_DEVICE,
},
};
diff --git a/arch/arm/mach-exynos/include/mach/map.h b/arch/arm/mach-exynos/include/mach/map.h
index de3ae59..a2acba3 100644
--- a/arch/arm/mach-exynos/include/mach/map.h
+++ b/arch/arm/mach-exynos/include/mach/map.h
@@ -25,7 +25,6 @@
#define EXYNOS_PA_CHIPID 0x10000000
#define EXYNOS4_PA_CMU 0x10030000
-#define EXYNOS5_PA_CMU 0x10010000
#define EXYNOS4_PA_DMC0 0x10400000
#define EXYNOS4_PA_DMC1 0x10410000
--
1.9.1
next prev parent reply other threads:[~2015-12-12 7:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 7:43 [RESEND PATCH v5 0/8] Add support for Exynos SROM Controller driver Pankaj Dubey
2015-12-12 7:43 ` Pankaj Dubey [this message]
2015-12-12 7:43 ` [RESEND PATCH v5 2/8] ARM: EXYNOS: code cleanup in map.h Pankaj Dubey
2015-12-12 7:43 ` [RESEND PATCH v5 3/8] dt-bindings: add exynos-srom device tree binding Pankaj Dubey
2015-12-12 7:43 ` [RESEND PATCH v5 4/8] ARM: dts: add SROM device node for exynos4 Pankaj Dubey
2015-12-12 7:43 ` [RESEND PATCH v5 5/8] ARM: dts: add SROM device node for exynos5 Pankaj Dubey
2015-12-12 7:44 ` [RESEND PATCH v5 6/8] drivers: soc: add support for exynos SROM driver Pankaj Dubey
2015-12-12 7:44 ` [RESEND PATCH v5 7/8] MAINTAINERS: add maintainers entry for drivers/soc/samsung Pankaj Dubey
2015-12-12 7:44 ` [RESEND PATCH v5 8/8] ARM: EXYNOS: Remove SROM related register settings from mach-exynos Pankaj Dubey
2015-12-14 7:39 ` [RESEND PATCH v5 0/8] Add support for Exynos SROM Controller driver Pavel Fedin
2015-12-17 5:14 ` Krzysztof Kozlowski
2015-12-18 3:39 ` pankaj.dubey
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=1449906242-20843-2-git-send-email-pankaj.dubey@samsung.com \
--to=pankaj.dubey@samsung.com \
--cc=andi.shyti@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=p.fedin@samsung.com \
--cc=thomas.ab@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).