From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] mmc: sdhci: Defer probe if regulator_get fails
Date: Tue, 23 Oct 2012 18:07:39 +0100 [thread overview]
Message-ID: <20121023170723.GD4477@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5086C5F5.4070801@wwwdotorg.org>
On Tue, Oct 23, 2012 at 10:29:41AM -0600, Stephen Warren wrote:
> On 10/23/2012 01:57 AM, Lucas Stach wrote:
> > Does this work with boards where we don't have any MMC supplies? Or are
> > we just deferring the probe indefinitely there?
> > For boards that power MMC unconditionally, are we supposed to add dummy
> > regulators to make them work with this patchset?
> I believe that dummy (fixed) regulators are supposed to be provided in
> all cases where the platform doesn't actually have one. The fact that
> everything worked OK without them before this patch was most likely a
> mistake/accident.
That's the general idea; clearly there *are* supplies here, they're just
not software controlled supplies.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121023/e239279e/attachment.sig>
next prev parent reply other threads:[~2012-10-23 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 7:18 [PATCH 0/2] mmc: sdhci: Defer probe if regulators are not registered Pavan Kunapuli
2012-10-23 7:18 ` [PATCH 1/2] ARM: dt: tegra: Add sdhci regulators Pavan Kunapuli
2012-10-23 18:07 ` Marc Dietrich
2012-10-23 18:42 ` Stephen Warren
2012-10-23 19:41 ` Marc Dietrich
2012-10-23 7:19 ` [PATCH 2/2] mmc: sdhci: Defer probe if regulator_get fails Pavan Kunapuli
2012-10-23 7:57 ` Lucas Stach
2012-10-23 8:16 ` Pavan Kunapuli
2012-10-23 16:29 ` Stephen Warren
2012-10-23 17:07 ` Mark Brown [this message]
2012-10-23 13:21 ` Philip Rakity
2012-10-23 13:36 ` Russell King - ARM Linux
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=20121023170723.GD4477@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).