From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Chris Ball <cjb@laptop.org>
Cc: Kevin Liu <keyuan.liu@gmail.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
kyungmin.park@samsung.com,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
lrg@ti.com, Philip Rakity <prakity@nvidia.com>
Subject: Re: FW: [PATCH v2] mmc: sdhci: apply voltage range check only for non-fixed regulators
Date: Tue, 04 Dec 2012 15:07:34 +0100 [thread overview]
Message-ID: <50BE03A6.6010504@samsung.com> (raw)
In-Reply-To: <87hao7f344.fsf@octavius.laptop.org>
Hello,
On 11/30/2012 5:48 PM, Chris Ball wrote:
> On Tue, Nov 20 2012, Marek Szyprowski wrote:
> > The problem with dummy regulator is the fact that it can be enabled only
> > globally for all devices in the system. I think that the best solution
> > would be to introduce regulator_can_change_voltage() as Mark suggested.
> > I will post patches soon.
>
> Does this mean that I shouldn't merge either yours or Kevin's patch for
> 3.8, while we wait for this? Any ETA on it?
I've just posted an updated patches to solve those issues. I'm sorry for the
delay as I was terribly busy with other stuff. Kevin's patch is still
required and it should stay in the tree because it indeed fixes other, in
some cases related issues.
However my earlier patch "mmc: sdhci: apply voltage range check only for
non-fixed regulators" can be replaced with the new patches from the
"[PATCH v2 0/3] Fix fixed regulators support" thread posted a few minutes
ago (those patches are based on mmc-next branch).
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
prev parent reply other threads:[~2012-12-04 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25B60CDC2F704E4E9D88FFD52780CB4C060FBEA29A@SC-VEXCH1.marvell.com>
2012-11-14 7:11 ` FW: [PATCH v2] mmc: sdhci: apply voltage range check only for non-fixed regulators Kevin Liu
2012-11-14 7:28 ` Mark Brown
2012-11-14 8:36 ` Kevin Liu
2012-11-14 8:41 ` Mark Brown
2012-11-14 8:57 ` Kevin Liu
2012-11-14 9:08 ` Philip Rakity
2012-11-14 12:05 ` Kevin Liu
2012-11-20 7:44 ` FW: " Marek Szyprowski
2012-11-20 8:59 ` Kevin Liu
2012-11-20 10:16 ` Marek Szyprowski
2012-11-20 11:36 ` Kevin Liu
2012-11-20 13:12 ` Marek Szyprowski
2012-11-20 13:27 ` Chris Ball
2012-11-20 14:14 ` Kevin Liu
2012-11-20 15:02 ` Marek Szyprowski
2012-11-20 15:24 ` Kevin Liu
2012-11-30 16:48 ` Chris Ball
2012-12-04 14:07 ` Marek Szyprowski [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=50BE03A6.6010504@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=keyuan.liu@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lrg@ti.com \
--cc=prakity@nvidia.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).