linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Mike Turquette <mturquette@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 3/4] OMAP: Voltage: add ABB structures and data
Date: Tue, 01 Mar 2011 14:05:56 -0800	[thread overview]
Message-ID: <87mxleh4xn.fsf@ti.com> (raw)
In-Reply-To: <1298020853-13761-3-git-send-email-mturquette@ti.com> (Mike Turquette's message of "Fri, 18 Feb 2011 03:20:52 -0600")

Hi Mike,

Mike Turquette <mturquette@ti.com> writes:

> OMAP3630 and OMAP4 support an Adaptive Body-Bias LDO on some voltage domains
> which effects voltage supplied to PMOS back-gates.  These LDOs have
> different operating modes which correspond to the voltage of each VDD.
>
> This patch introduces the data structures needed to represent the ABB LDOs
> in the voltage layer, and populates the appropriate data for 3630 and OMAP4.
> Note that OMAP34XX does not have this LDO, so any data for that chip has
> been initialized as zero.
>
> Signed-off-by: Mike Turquette <mturquette@ti.com>

This patch (and this series) should be updated based on Paul's split-up
of the voltage code & data series:

   http://marc.info/?l=linux-arm-kernel&m=129825439819340&w=2

> ---
>  arch/arm/mach-omap2/voltage.c             |  137 ++++++++++++++++++++++-------
>  arch/arm/plat-omap/include/plat/voltage.h |   28 ++++++
>  2 files changed, 133 insertions(+), 32 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/voltage.c b/arch/arm/mach-omap2/voltage.c
> index 0cbc58a..6ede092 100644
> --- a/arch/arm/mach-omap2/voltage.c
> +++ b/arch/arm/mach-omap2/voltage.c
> @@ -39,6 +39,10 @@
>  #define VP_TRANXDONE_TIMEOUT	300
>  #define VOLTAGE_DIR_SIZE	16
>  
> +#define ABB_TRANXDONE_TIMEOUT	30
> +#define FAST_OPP		0x1
> +#define NOMINAL_OPP		0x0
> +
>  static struct omap_vdd_info *vdd_info;
>  /*
>   * Number of scalable voltage domains.
> @@ -59,6 +63,17 @@ static struct omap_vdd_info omap3_vdd_info[] = {
>  		.voltdm = {
>  			.name = "mpu",
>  		},
> +		.abb = {
> +			.setup_offs	= OMAP3_PRM_LDO_ABB_SETUP_OFFSET,
> +			.ctrl_offs	= OMAP3_PRM_LDO_ABB_CTRL_OFFSET,
> +			.irqstatus_mpu_offs
> +					= OMAP3_PRM_IRQSTATUS_MPU_OFFSET,
> +			.done_st_shift	= OMAP3630_ABB_LDO_TRANXDONE_ST_SHIFT,
> +			.done_st_mask	= OMAP3630_ABB_LDO_TRANXDONE_ST_MASK,
> +			.configure	= NULL,
> +			.nb_handler	= NULL,
> +			.set_opp	= NULL,

NULL assignments are redundant.

[...]

Kevin

  reply	other threads:[~2011-03-01 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18  9:20 [PATCH 1/4] OMAP: voltage: pre- and post-transition notifiers Mike Turquette
2011-02-18  9:20 ` [PATCH 2/4] OMAP3630: add missing ABB PRM register definitions Mike Turquette
2011-02-18  9:20 ` [PATCH 3/4] OMAP: Voltage: add ABB structures and data Mike Turquette
2011-03-01 22:05   ` Kevin Hilman [this message]
2011-02-18  9:20 ` [PATCH 4/4] OMAP: Voltage: Adaptive Body-Bias handlers Mike Turquette
2011-02-19  0:29   ` David Cohen
2011-02-21 10:31   ` Gulati, Shweta
2011-02-21 19:47     ` Turquette, Mike
2011-02-21 23:01       ` Cousson, Benoit
2011-02-28  9:35       ` Gulati, Shweta
2011-03-01 17:30         ` Turquette, Mike
2011-03-04  4:53           ` Gulati, Shweta
2011-03-01 22:06 ` [PATCH 1/4] OMAP: voltage: pre- and post-transition notifiers 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=87mxleh4xn.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@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 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).