From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Yen.Lin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org
Cc: olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org,
mike-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org,
lrg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org,
swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
xxie-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
Yen Lin <yelin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] ARM: regulator: tps6586x: add PFM/PWM options on SMs
Date: Fri, 15 Apr 2011 10:30:53 +0100 [thread overview]
Message-ID: <20110415093052.GC23466@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1302818393-19067-1-git-send-email-yelin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Thu, Apr 14, 2011 at 02:59:53PM -0700, Yen.Lin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org wrote:
> TPS6586x SM0, SM1 and SM2 port have 2 power switching modes:
> - PWM only, or
> - PMW-PFM auto mode
> Some of TPS6586x have voltage spike in PFM-to-FWM transition which
> can lockup the CPU if choose PWM-PFM auto mode.
> This patch enables such mode selection on SMs ports from the
> board level power configuration file.
This is just the regular regulator mode API - forced PWM mode would map
onto _FAST.
next prev parent reply other threads:[~2011-04-15 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 21:59 [PATCH] ARM: regulator: tps6586x: add PFM/PWM options on SMs Yen.Lin-DDmLM1+adcrQT0dZR+AlfA
[not found] ` <1302818393-19067-1-git-send-email-yelin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-04-14 22:58 ` Mayuresh Janorkar
[not found] ` <BANLkTi=McsPozAGVCf9TBNuxZvtTPw79yA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-15 23:41 ` Yen Lin
2011-04-15 9:30 ` Mark Brown [this message]
[not found] ` <20110415093052.GC23466-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2011-04-16 1:13 ` Yen Lin
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=20110415093052.GC23466@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=Yen.Lin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lrg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org \
--cc=mike-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=xxie-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=yelin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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