All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
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, 20 Nov 2012 08:27:05 -0500	[thread overview]
Message-ID: <878v9wflqu.fsf@octavius.laptop.org> (raw)
In-Reply-To: <50AB81C8.4090300@samsung.com> (Marek Szyprowski's message of "Tue, 20 Nov 2012 14:12:40 +0100")

Hi,

On Tue, Nov 20 2012, Marek Szyprowski wrote:
>> >> >> Subject: [PATCH v5 03/13] mmc: sdhci: use regulator min/max voltage
>> >> >> range according to spec
>> >> >>
>> >> >> From: Kevin Liu <kliu5@marvell.com>
>> >> >>
>> >> >> For regulator vmmc/vmmcq, use voltage range as below
>> >> >> 3.3v/3.0v: (2.7v, 3.6v)
>> >> >> 1.8v: (1.7v, 1.95v)
>> >> >> Original code use the specific value which may fail in regulator
>> >> >> driver if it does NOT support the specific voltage.
>> >> >>
>> >> >> Signed-off-by: Jialing Fu <jlfu@marvell.com>
>> >> >> Signed-off-by: Kevin Liu <kliu5@marvell.com>
>> >> >
>> >> >
>> >> > Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> >> >
>> >> > This patch restores sdhci devices to working state on Samsung boards
>> >> > (tested on GONI and UniversalC210) after merging "regulator: fix voltage
>> >> > check in regulator_is_supported_voltage()" patch to v3.7-rc6 (commit
>> >> > f0f98b19e23d4426ca185e3d4ca80e6aff5ef51b). Would be great to have it
>> >> > merged before the final v3.7 is out.
>> >> >
>> >> Marek,
>> >>
>> >> thanks a lot for the verification!
>> >> And your patch "mmc: sdhci: apply voltage range check only for
>> >> non-fixed regulators" (commit
>> >> d5b5205f2d480a47863dda0772d2d9dc47c2b51b, which has been merged in
>> >> mmc-next) can be reverted if this patch merged?
>> >
>> >
>> > Yes, it can be replaced with it, although there is still an issue that need
>> > to be resolved somehow. Right now SDHCI driver fails to initialize if
>> > support
>> > for dummy regulator is enabled.
>> >
>> Then I think the dummy issue can be resolved with your patch merged
>> and if you can just update your patch from
>>       "regulator_count_voltages(host->vmmc) > 1"
>> to
>>       "regulator_count_voltages(host->vmmc) > 0"
>> to let fix regulator work.
>
> regulator_count_voltages() returns 1 for both fixed regulators and for
> virtual dummy regulator, so the above change makes no sense.
>
> However I was so focused on fixing the 2.8V supply case that I missed the
> fact that my "mmc: sdhci: apply voltage range check only for non-fixed
> regulators" patch also fixed the dummy regulator case.
>
> The conclusion is that applying both patches should finally fix the
> regulator issues with for the Samsung boards (2.8V supply for eMMC) and
> 'dummy-regulators' cases.

Thanks, I've pushed v5 of "mmc: sdhci: use regulator min/max voltage
range according to spec" to mmc-next for 3.7 with Marek's Tested-by now.

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2012-11-20 13:27 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 [this message]
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

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=878v9wflqu.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --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=m.szyprowski@samsung.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 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.