public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Sanjeev Premi <premi@ti.com>
To: linux-omap@vger.kernel.org
Cc: Sanjeev Premi <premi@ti.com>
Subject: [RFC 2/3] am35xx: voltage: Add basic initialization
Date: Wed, 23 Feb 2011 23:28:32 +0530	[thread overview]
Message-ID: <1298483913-20344-3-git-send-email-premi@ti.com> (raw)
In-Reply-To: <1298483913-20344-1-git-send-email-premi@ti.com>

This patch adds basic initialization in
the voltage layer for AM35xx processors.

In absence of AVS, functions vp_init() and
vc_init() are empty.

Signed-off-by: Sanjeev Premi <premi@ti.com>
---
 arch/arm/mach-omap2/voltage.c |   45 ++++++++++++++++++++++++++++++++++++++++-
 1 files changed, 44 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-omap2/voltage.c b/arch/arm/mach-omap2/voltage.c
index bbc36e7..63dac11 100644
--- a/arch/arm/mach-omap2/voltage.c
+++ b/arch/arm/mach-omap2/voltage.c
@@ -194,6 +194,30 @@ static struct omap_vdd_info omap3_vdd_info[] = {
 
 #define OMAP3_NR_SCALABLE_VDD ARRAY_SIZE(omap3_vdd_info)
 
+/*
+ * AM3517 VDD structures
+ * TODO: The values in vp_offs are just a copy of OMAP3 for now.
+ *       Assignments need to be looked again; but appears that
+ *       they won't ever be used.
+ */
+static struct omap_vdd_info am3517_vdd_info[] = {
+        {
+                .vp_offs = {
+                        .vpconfig       = OMAP3_PRM_VP1_CONFIG_OFFSET,
+                        .vstepmin       = OMAP3_PRM_VP1_VSTEPMIN_OFFSET,
+                        .vstepmax       = OMAP3_PRM_VP1_VSTEPMAX_OFFSET,
+                        .vlimitto       = OMAP3_PRM_VP1_VLIMITTO_OFFSET,
+                        .vstatus        = OMAP3_PRM_VP1_STATUS_OFFSET,
+                        .voltage        = OMAP3_PRM_VP1_VOLTAGE_OFFSET,
+                },
+                .voltdm = {
+                        .name = "mpu",
+                },
+        },
+};
+
+#define AM3517_NR_SCALABLE_VDD 0
+
 /* OMAP4 VDD sturctures */
 static struct omap_vdd_info omap4_vdd_info[] = {
 	{
@@ -1551,11 +1575,30 @@ int __init omap_voltage_late_init(void)
 }
 
 /**
+ * AM35xx - dummy initialization of voltage controller
+ */
+static void __init am3517_vc_init(struct omap_vdd_info *vdd)
+{
+}
+/**
+ * AM35xx - dummy initialization of voltage processor
+ */
+static void __init am3517_vp_init(struct omap_vdd_info *vdd)
+{
+}
+
+/**
  * omap_voltage_early_init()- Volatage driver early init
  */
 static int __init omap_voltage_early_init(void)
 {
-	if (cpu_is_omap34xx()) {
+	if (cpu_is_omap3505() || cpu_is_omap3517()) {
+		vdd_info	= am3517_vdd_info;
+		nr_scalable_vdd	= AM3517_NR_SCALABLE_VDD;
+		vc_init		= am3517_vc_init;
+		vp_init		= am3517_vp_init;
+		vdd_data_configure = omap3_vdd_data_configure;
+	} else if (cpu_is_omap34xx()) {
 		vdd_info = omap3_vdd_info;
 		nr_scalable_vdd = OMAP3_NR_SCALABLE_VDD;
 		vc_init = omap3_vc_init;
-- 
1.7.2.2


  parent reply	other threads:[~2011-02-23 17:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 17:58 [RFC 0/3] Support TPS65023 with AM35xx Sanjeev Premi
2011-02-23 17:58 ` [RFC 1/3] omap: voltage: Allow custom vp_init() implementation Sanjeev Premi
2011-02-23 18:36   ` Menon, Nishanth
2011-02-23 20:45     ` Premi, Sanjeev
2011-02-24  1:11       ` Nishanth Menon
2011-02-23 17:58 ` Sanjeev Premi [this message]
2011-02-23 18:40   ` [RFC 2/3] am35xx: voltage: Add basic initialization Menon, Nishanth
2011-02-23 17:58 ` [RFC 3/3] am35xx: pm: Hook-up with TPS65023 Sanjeev Premi
2011-02-23 18:43   ` Menon, Nishanth
2011-02-24 13:20     ` Premi, Sanjeev
2011-02-24 10:04   ` Vishwanath Sripathy
2011-03-07 15:20     ` Premi, Sanjeev
2011-03-07 16:31       ` Vishwanath Sripathy
2011-03-08 12:26         ` Premi, Sanjeev
2011-03-08 12:45           ` Vishwanath Sripathy
2011-03-08 13:25             ` Premi, Sanjeev
2011-03-08 12:46           ` Nishanth Menon
2011-03-08 13:18             ` Premi, Sanjeev
2011-03-08 13:27               ` Menon, Nishanth
2011-03-08 13:37                 ` Premi, Sanjeev
2011-03-08 16:08                 ` Kevin Hilman

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=1298483913-20344-3-git-send-email-premi@ti.com \
    --to=premi@ti.com \
    --cc=linux-omap@vger.kernel.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