From: Chris Ball <cjb@laptop.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
will.newton@imgtec.com, Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH 2/3] dw_mmc: support mmc power control with regulator
Date: Thu, 17 Mar 2011 15:01:39 -0400 [thread overview]
Message-ID: <m3mxkto9kc.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <m3ei65pqcp.fsf@pullcord.laptop.org> (Chris Ball's message of "Thu, 17 Mar 2011 14:13:42 -0400")
Hi,
On Thu, Mar 17 2011, Chris Ball wrote:
>> @@ -1438,6 +1439,13 @@ static int __init dw_mci_init_slot(struct dw_mci *host, unsigned int id)
>> }
>> #endif /* CONFIG_MMC_DW_IDMAC */
>>
>> + host->vmmc = regulator_get(mmc_dev(mmc), "vmmc");
>> + if (IS_ERR(host->vmmc)) {
>> + printk(KERN_INFO "%s: no vmmc regulator found\n", mmc_hostname(mmc));
>> + host->vmmc = NULL;
>> + } else
>> + regulator_enable(host->vmmc);
>> +
>> if (dw_mci_get_cd(mmc))
>> set_bit(DW_MMC_CARD_PRESENT, &slot->flags);
>> else
>
> I think you want an "#ifdef CONFIG_REGULATOR" around this hunk.
> Please try building the driver with CONFIG_REGULATOR=n.
>
> The other hunks in the patch shouldn't need it, because they test
> "host->vcc" before making any regulator calls.
Actually, <linux/regulator/consumer.h> provides no-op versions of all
these functions if CONFIG_REGULATOR is unset, so I guess this doesn't
matter; the driver builds without CONFIG_REGULATOR as-is.
Will merge for .39 with Will's ACK, thanks.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2011-03-17 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 2:08 [PATCH 2/3] dw_mmc: support mmc power control with regulator Jaehoon Chung
2011-02-25 17:57 ` Will Newton
2011-03-17 10:23 ` Jaehoon Chung
2011-03-17 18:13 ` Chris Ball
2011-03-17 19:01 ` Chris Ball [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=m3mxkto9kc.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=jh80.chung@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=will.newton@imgtec.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.