From: Marek Szyprowski <m.szyprowski@samsung.com>
To: 'Chris Ball' <cjb@laptop.org>, 'Jaehoon Chung' <jh80.chung@samsung.com>
Cc: 'linux-mmc' <linux-mmc@vger.kernel.org>,
'Kyungmin Park' <kyungmin.park@samsung.com>,
'Adrian Hunter' <adrian.hunter@intel.com>
Subject: RE: [RFC] mmc: core: add the capability for broken voltage
Date: Mon, 06 Feb 2012 11:24:52 +0100 [thread overview]
Message-ID: <000001cce4b9$906c6f90$b1454eb0$%szyprowski@samsung.com> (raw)
In-Reply-To: <m2aa4y9o7k.fsf@bob.laptop.org>
Hello,
On Sunday, February 05, 2012 12:25 AM Chris Ball wrote:
> On Mon, Jan 16 2012, Jaehoon Chung wrote:
> > This patch is added the MMC_CAP2_BROKEN_VOLTAGE.
> >
> > if the voltage didn't satisfy between min_uV and max_uV,
> > try to change the voltage in core.c.
> > When change the voltage, maybe use the regulator_set_voltage().
>
> Thanks, pushed to mmc-next for 3.3 with Adrian's ACK. Marek, does this
> work for you?
Yes, it works fine together with a patch from
http://thread.gmane.org/gmane.linux.kernel.mmc/12658
I also had to set this new capability in device's platform data.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
prev parent reply other threads:[~2012-02-06 10:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 8:49 [RFC] mmc: core: add the capability for broken voltage Jaehoon Chung
2012-01-17 8:00 ` Adrian Hunter
2012-01-17 9:05 ` Kyungmin Park
2012-01-17 9:37 ` Adrian Hunter
2012-01-17 9:53 ` Kyungmin Park
2012-01-17 11:47 ` Adrian Hunter
2012-01-17 23:58 ` Kyungmin Park
2012-01-18 8:01 ` Adrian Hunter
2012-01-18 8:13 ` Kyungmin Park
2012-01-18 8:56 ` Adrian Hunter
2012-01-18 13:03 ` Kyungmin Park
2012-01-19 10:14 ` Adrian Hunter
2012-01-19 10:40 ` Kyungmin Park
2012-01-19 14:08 ` Adrian Hunter
2012-02-04 23:24 ` Chris Ball
2012-02-06 10:24 ` 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='000001cce4b9$906c6f90$b1454eb0$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung.com \
--cc=adrian.hunter@intel.com \
--cc=cjb@laptop.org \
--cc=jh80.chung@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.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).