From: Kevin Hilman <khilman@ti.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] ARM: OMAP4: add support for TPS62361 PMIC
Date: Tue, 29 May 2012 14:29:15 -0700 [thread overview]
Message-ID: <87ehq2ekwk.fsf@ti.com> (raw)
In-Reply-To: <1336139842-845-1-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Fri, 4 May 2012 16:57:19 +0300")
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?
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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP4: add support for TPS62361 PMIC
Date: Tue, 29 May 2012 14:29:15 -0700 [thread overview]
Message-ID: <87ehq2ekwk.fsf@ti.com> (raw)
In-Reply-To: <1336139842-845-1-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Fri, 4 May 2012 16:57:19 +0300")
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?
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
next prev parent reply other threads:[~2012-05-29 21:29 UTC|newest]
Thread overview: 26+ 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 ` Tero Kristo
2012-05-04 13:57 ` [PATCH 1/3] ARM: OMAP4: VC: fix I2C timing Tero Kristo
2012-05-04 13:57 ` Tero Kristo
2012-05-29 21:30 ` Kevin Hilman
2012-05-29 21:30 ` Kevin Hilman
2012-05-30 8:50 ` Tero Kristo
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-04 13:57 ` Tero Kristo
2012-05-07 12:00 ` Vishwanath Sripathy
2012-05-07 12:00 ` Vishwanath Sripathy
2012-05-07 13:24 ` Tero Kristo
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 13:57 ` Tero Kristo
2012-05-04 22:00 ` Nishanth Menon
2012-05-04 22:00 ` Nishanth Menon
2012-05-07 7:38 ` Tero Kristo
2012-05-07 7:38 ` Tero Kristo
2012-05-07 14:32 ` Menon, Nishanth
2012-05-07 14:32 ` Menon, Nishanth
2012-05-29 21:29 ` Kevin Hilman [this message]
2012-05-29 21:29 ` [PATCH 0/3] ARM: OMAP4: add support for TPS62361 PMIC Kevin Hilman
2012-05-30 8:12 ` Tero Kristo
2012-05-30 8:12 ` Tero Kristo
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=87ehq2ekwk.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=t-kristo@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.