linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP4: add support for TPS62361 PMIC
Date: Wed, 30 May 2012 11:12:23 +0300	[thread overview]
Message-ID: <1338365543.8834.111.camel@sokoban> (raw)
In-Reply-To: <87ehq2ekwk.fsf@ti.com>

On Tue, 2012-05-29 at 14:29 -0700, Kevin Hilman wrote:
> Tero Kristo <t-kristo@ti.com> writes:
> 
> > Hi,
> >
> > This set adds support for TPS62361 PMIC, which is used to power
> > MPU voltagedomain on OMAP4460 boards. These patches apply on top
> > of 3.4 + my voltagedomain fixes set to avoid adding redundant code.
> 
> Hmm... do you have an updated version of your voltagedomain fixes?  Or
> are you waiting for me to review something?  I thought I had been
> through them already, but if I have not, they slipped throught the
> cracks.  I'm sorry.  Can you please update/repost?

There have been some updates to the patches as per Nishanth's comments,
but I need to double check those before re-posting here. I can re-post
this series also once that is done.

-Tero

> 
> Thanks.
> 
> Kevin
> 
> > Working tree available here for interested parties:
> >
> > git://gitorious.org/~kristo/omap-pm/omap-pm-work.git
> > branch: mainline-3.4-voltdm-tps-v1
> >
> > Tree has been tested with:
> > - omap3beagle board
> > - omap4panda es board (OMAP4460)
> > - omap4blaze board (OMAP4430)
> >
> > Tested modifying the voltage levels on all core regulators (vdd1...vdd3)
> > and measuring that the voltages do actually change.
> >
> > Patch #1 was needed before the voltages could be modified on a panda
> > board es device, otherwise the timing for the I2C channel was so bogus
> > it usually failed. The values used were taken from an android tree and
> > are based on TI analysis.
> >
> > -Tero
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> > the body of a message to majordomo at vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2012-05-30  8:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 13:57 [PATCH 0/3] ARM: OMAP4: add support for TPS62361 PMIC Tero Kristo
2012-05-04 13:57 ` [PATCH 1/3] ARM: OMAP4: VC: fix I2C timing Tero Kristo
2012-05-29 21:30   ` Kevin Hilman
2012-05-30  8:50     ` Tero Kristo
2012-05-04 13:57 ` [PATCH 2/3] ARM: OMAP3+: PM: introduce a central pmic control Tero Kristo
2012-05-07 12:00   ` Vishwanath Sripathy
2012-05-07 13:24     ` Tero Kristo
2012-05-04 13:57 ` [PATCH 3/3] ARM: OMAP2+ PM: Add support for TPS62361 Tero Kristo
2012-05-04 22:00   ` Nishanth Menon
2012-05-07  7:38     ` Tero Kristo
2012-05-07 14:32       ` Menon, Nishanth
2012-05-29 21:29 ` [PATCH 0/3] ARM: OMAP4: add support for TPS62361 PMIC Kevin Hilman
2012-05-30  8:12   ` Tero Kristo [this message]

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=1338365543.8834.111.camel@sokoban \
    --to=t-kristo@ti.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).