From: Nishanth Menon <menon.nishanth@gmail.com>
To: Sanjeev Premi <premi@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Question on OPP table handling
Date: Sat, 03 Oct 2009 10:04:48 -0500 [thread overview]
Message-ID: <4AC76810.1040206@gmail.com> (raw)
In-Reply-To: <1254420194-4757-1-git-send-email-premi@ti.com>
Sanjeev Premi said the following on 10/01/2009 01:03 PM:
> +struct omap_opp omap3_mpu_rate_table[] = {
> + {0, 0, 0},
> + /*OPP1*/
> + {S125M, VDD1_OPP1, 0x1E},
> + /*OPP2*/
> + {S250M, VDD1_OPP2, 0x26},
> + /*OPP3*/
> + {S500M, VDD1_OPP3, 0x30},
> + /*OPP4*/
> + {S550M, VDD1_OPP4, 0x36},
> + /*OPP5*/
> + {S600M, VDD1_OPP5, 0x3C},
> +};
>
For those involved,
if we wanted to convert omap3_mpu_table[] into *omap3_mpu_table so that
we dynamically initialize it based on cpu type - what would be the
recommendations?
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-10-03 15:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 18:03 [PATCHv2 1/1] OMAP3: PM: Functions to get freq from opp and vice-versa Sanjeev Premi
2009-10-03 15:04 ` Nishanth Menon [this message]
2009-10-05 13:09 ` Question on OPP table handling Premi, Sanjeev
2009-10-05 16:56 ` Kevin Hilman
2009-10-05 17:19 ` Nishanth Menon
2009-10-06 8:06 ` Shilimkar, Santosh
2009-10-06 8:44 ` Premi, Sanjeev
2009-10-06 9:19 ` Shilimkar, Santosh
2009-10-06 8:42 ` Cousson, Benoit
2009-10-06 8:52 ` Premi, Sanjeev
2009-10-06 11:44 ` Nishanth Menon
2009-10-06 12:00 ` Dasgupta, Romit
2009-10-06 12:04 ` Nishanth Menon
2009-10-06 12:10 ` Cousson, Benoit
2009-10-06 12:14 ` Dasgupta, Romit
2009-10-06 12:52 ` Cousson, Benoit
2009-10-09 0:41 ` Nishanth Menon
2009-10-06 12:21 ` Dasgupta, Romit
2009-10-06 12:43 ` Shilimkar, Santosh
2009-10-06 13:29 ` Kevin Hilman
2009-10-09 15:19 ` [PATCHv2 1/1] OMAP3: PM: Functions to get freq from opp and vice-versa 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=4AC76810.1040206@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.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.