linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/12] ARM: OMAP2+: Add minimal clockdomains for dm814x
Date: Wed,  3 Jun 2015 09:23:12 -0700	[thread overview]
Message-ID: <1433348601-8966-4-git-send-email-tony@atomide.com> (raw)
In-Reply-To: <1433348601-8966-1-git-send-email-tony@atomide.com>

For now, let's just add the ones shared with dm816x.
The dm814x specific ones can be added as they are tested.

Cc: Matthijs van Duin <matthijsvanduin@gmail.com>
Cc: Paul Walmsley <paul@pwsan.com>
Cc: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
 arch/arm/mach-omap2/clockdomain.h           |  3 ++-
 arch/arm/mach-omap2/clockdomains81xx_data.c | 23 ++++++++++++++++++++---
 arch/arm/mach-omap2/io.c                    |  4 ++--
 3 files changed, 24 insertions(+), 6 deletions(-)

diff --git a/arch/arm/mach-omap2/clockdomain.h b/arch/arm/mach-omap2/clockdomain.h
index 77bab5f..2c398ce 100644
--- a/arch/arm/mach-omap2/clockdomain.h
+++ b/arch/arm/mach-omap2/clockdomain.h
@@ -216,7 +216,8 @@ extern void __init omap242x_clockdomains_init(void);
 extern void __init omap243x_clockdomains_init(void);
 extern void __init omap3xxx_clockdomains_init(void);
 extern void __init am33xx_clockdomains_init(void);
-extern void __init ti81xx_clockdomains_init(void);
+extern void __init ti814x_clockdomains_init(void);
+extern void __init ti816x_clockdomains_init(void);
 extern void __init omap44xx_clockdomains_init(void);
 extern void __init omap54xx_clockdomains_init(void);
 extern void __init dra7xx_clockdomains_init(void);
diff --git a/arch/arm/mach-omap2/clockdomains81xx_data.c b/arch/arm/mach-omap2/clockdomains81xx_data.c
index ce2a820..53442c8 100644
--- a/arch/arm/mach-omap2/clockdomains81xx_data.c
+++ b/arch/arm/mach-omap2/clockdomains81xx_data.c
@@ -165,7 +165,24 @@ static struct clockdomain default_l3_slow_816x_clkdm = {
 	.flags		= CLKDM_CAN_SWSUP,
 };
 
-static struct clockdomain *clockdomains_ti81xx[] __initdata = {
+static struct clockdomain *clockdomains_ti814x[] __initdata = {
+	&alwon_l3_slow_81xx_clkdm,
+	&alwon_l3_med_81xx_clkdm,
+	&alwon_l3_fast_81xx_clkdm,
+	&alwon_ethernet_81xx_clkdm,
+	&mmu_81xx_clkdm,
+	&mmu_cfg_81xx_clkdm,
+	NULL,
+};
+
+void __init ti814x_clockdomains_init(void)
+{
+	clkdm_register_platform_funcs(&am33xx_clkdm_operations);
+	clkdm_register_clkdms(clockdomains_ti814x);
+	clkdm_complete_init();
+}
+
+static struct clockdomain *clockdomains_ti816x[] __initdata = {
 	&alwon_mpu_816x_clkdm,
 	&alwon_l3_slow_81xx_clkdm,
 	&alwon_l3_med_81xx_clkdm,
@@ -185,10 +202,10 @@ static struct clockdomain *clockdomains_ti81xx[] __initdata = {
 	NULL,
 };
 
-void __init ti81xx_clockdomains_init(void)
+void __init ti816x_clockdomains_init(void)
 {
 	clkdm_register_platform_funcs(&am33xx_clkdm_operations);
-	clkdm_register_clkdms(clockdomains_ti81xx);
+	clkdm_register_clkdms(clockdomains_ti816x);
 	clkdm_complete_init();
 }
 #endif
diff --git a/arch/arm/mach-omap2/io.c b/arch/arm/mach-omap2/io.c
index 820dde8..6779a9f 100644
--- a/arch/arm/mach-omap2/io.c
+++ b/arch/arm/mach-omap2/io.c
@@ -554,7 +554,7 @@ void __init ti814x_init_early(void)
 	omap2_prcm_base_init();
 	omap3xxx_voltagedomains_init();
 	omap3xxx_powerdomains_init();
-	ti81xx_clockdomains_init();
+	ti814x_clockdomains_init();
 	ti81xx_hwmod_init();
 	omap_hwmod_init_postsetup();
 	if (of_have_populated_dt())
@@ -571,7 +571,7 @@ void __init ti816x_init_early(void)
 	omap2_prcm_base_init();
 	omap3xxx_voltagedomains_init();
 	omap3xxx_powerdomains_init();
-	ti81xx_clockdomains_init();
+	ti816x_clockdomains_init();
 	ti81xx_hwmod_init();
 	omap_hwmod_init_postsetup();
 	if (of_have_populated_dt())
-- 
2.1.4

  parent reply	other threads:[~2015-06-03 16:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 16:23 [PATCH 00/12] Minimal support for dm814x-evm and hp t410 thin client Tony Lindgren
2015-06-03 16:23 ` [PATCH 01/12] ARM: OMAP2+: Fix dm814x DT_MACHINE_START Tony Lindgren
2015-06-03 16:23 ` [PATCH 02/12] ARM: OMAP2+: Fix scrm compatible for dm814x Tony Lindgren
2015-06-03 19:08   ` Sergei Shtylyov
2015-06-03 19:38     ` Tony Lindgren
2015-07-16  9:11       ` Tony Lindgren
2015-06-03 16:23 ` Tony Lindgren [this message]
2015-06-03 16:23 ` [PATCH 04/12] ARM: OMAP2+: Add custom prwdm_operations for 81xx to support dm814x Tony Lindgren
2015-06-03 16:23 ` [PATCH 05/12] ARM: OMAP2+: Add support for initializing dm814x clocks Tony Lindgren
2015-06-04 18:42   ` Stephen Boyd
2015-06-04 22:28     ` Tony Lindgren
2015-07-16  9:37       ` Tony Lindgren
2015-07-16 18:25         ` Stephen Boyd
2015-07-17  5:06           ` Tony Lindgren
2015-06-03 16:23 ` [PATCH 06/12] ARM: OMAP2+: Prepare dm81xx hwmod code for adding minimal dm814x support Tony Lindgren
2015-06-03 16:23 ` [PATCH 07/12] ARM: OMAP2: Add minimal dm814x hwmod support Tony Lindgren
2015-06-03 16:23 ` [PATCH 08/12] ARM: dts: Add minimal dm814x support Tony Lindgren
2015-06-03 16:23 ` [PATCH 09/12] ARM: dts: Add minimal clocks for dm814x Tony Lindgren
2015-06-03 16:23 ` [PATCH 10/12] ARM: dts: Add minimal dts support for dm8148-evm Tony Lindgren
2015-06-03 16:23 ` [PATCH 11/12] ARM: dts: Add minimal support for HP T410 Tony Lindgren
2015-06-03 16:23 ` [PATCH 12/12] ARM: OMAP2+: Add custom abort handler for t410 Tony Lindgren

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=1433348601-8966-4-git-send-email-tony@atomide.com \
    --to=tony@atomide.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).