From: Keerthy <a0393675@ti.com>
To: Mark Brown <broonie@kernel.org>, Keerthy <j-keerthy@ti.com>
Cc: <lee.jones@linaro.org>, <tony@atomide.com>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<t-kristo@ti.com>, <russ.dill@ti.com>,
Dave Gerlach <d-gerlach@ti.com>
Subject: Re: [PATCH v2 5/5] regulator: tps65218: do not disable DCDC3 during poweroff on broken PMICs
Date: Tue, 28 Jun 2016 14:58:18 +0530 [thread overview]
Message-ID: <57724332.1090704@ti.com> (raw)
In-Reply-To: <20160627165930.GC17217@sirena.org.uk>
On Monday 27 June 2016 10:29 PM, Mark Brown wrote:
> On Fri, Jun 24, 2016 at 01:58:11PM +0530, Keerthy wrote:
>> From: Tero Kristo <t-kristo@ti.com>
>>
>> Some versions of tps65218 do not seem to support poweroff modes properly
>> if DCDC3 regulator is shut-down. Thus, keep it enabled even during
>> poweroff if the version info matches the broken silicon revision.
>
> This is fine but depends on the MFD bit so needs to wait for that to be
> reviewed.
Yes. I will wait for Lee Jones to review Patch 4/5 of this series.
Thanks,
Keerthy
>
next prev parent reply other threads:[~2016-06-28 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 8:28 [PATCH v2 1/5] regulator: tps65217: Enable suspend configuration Keerthy
2016-06-24 8:28 ` [PATCH v2 2/5] regulator: tps65218: " Keerthy
2016-06-24 8:28 ` [PATCH v2 3/5] regulator: tps65218: force set power-up/down strobe to 3 for dcdc3 Keerthy
2016-06-24 8:28 ` [PATCH v2 4/5] mfd: tps65218: add version check to the PMIC probe Keerthy
2016-06-28 11:14 ` Lee Jones
2016-06-24 8:28 ` [PATCH v2 5/5] regulator: tps65218: do not disable DCDC3 during poweroff on broken PMICs Keerthy
2016-06-27 16:59 ` Mark Brown
2016-06-28 9:28 ` Keerthy [this message]
2016-06-28 11:12 ` Lee Jones
2016-06-28 11:13 ` Lee Jones
2016-06-28 11:24 ` Keerthy
2016-06-28 11:45 ` Lee Jones
2016-06-24 8:28 ` [PATCH v2 0/5] regulator: Enable suspend configuration Keerthy
2016-06-27 17:00 ` Applied "regulator: tps65217: Enable suspend configuration" to the regulator tree Mark Brown
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=57724332.1090704@ti.com \
--to=a0393675@ti.com \
--cc=broonie@kernel.org \
--cc=d-gerlach@ti.com \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=russ.dill@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).