From: shawn.lin@rock-chips•com (Shawn Lin)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH v3 1/3] mmc: sprd: Add MMC host driver for Spreadtrum SoC
Date: Mon, 28 Sep 2015 15:37:43 +0800 [thread overview]
Message-ID: <5608EE47.1020402@rock-chips.com> (raw)
In-Reply-To: <CAG_R4_VTXCV4NVMOwv-9F56-_pVsK0hU4go79ZhV3OFxwcF0mA@mail.gmail.com>
On 2015/9/28 15:18, Hongtao Wu wrote:
> >>
>
> On Thu, Sep 10, 2015 at 9:28 PM, Ulf Hansson <ulf.hansson@linaro•org
> <mailto:ulf.hansson@linaro•org>> wrote:
> >
> > On 14 August 2015 at 18:55, Hongtao Wu <wuht06@gmail•com
> <mailto:wuht06@gmail•com>> wrote:
[...]
>
> Yes, most of this data can be removed, such as caps, caps2, base_clk.
> However ocr_avail and signal_default_voltage are useful for us.
> We can't fetch ocr_avail from external regulator via
> mmc_regulator_get_supply,
> because our regulator driver can't supply mmc_regulator_get_ocrmask()
> interface for MMC driver.
Sorry for the noise but... IMO, your need to quirk your regulator driver
stuffs rather than mmc.
> And sometimes our external regulator can not supply 3.0v or 1.8v default
> signal voltage that we expect. So this 3.0v or 1.8v default signal
> voltage are
> mandatory.
>
--
Best Regards
Shawn Lin
next prev parent reply other threads:[~2015-09-28 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1439571353-30165-1-git-send-email-wuht06@gmail.com>
2015-09-10 11:23 ` [RFC PATCH v3 0/3] Add MMC host driver for Spreadtrum SoC Ulf Hansson
[not found] ` <1439571353-30165-2-git-send-email-wuht06@gmail.com>
2015-09-10 13:28 ` [RFC PATCH v3 1/3] mmc: sprd: " Ulf Hansson
[not found] ` <CAG_R4_VTXCV4NVMOwv-9F56-_pVsK0hU4go79ZhV3OFxwcF0mA@mail.gmail.com>
2015-09-28 7:37 ` Shawn Lin [this message]
2015-10-06 9:18 ` Ulf Hansson
2015-10-08 13:37 ` Hongtao Wu
2015-10-08 13:54 ` Ulf Hansson
2015-10-09 13:23 ` Hongtao Wu
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=5608EE47.1020402@rock-chips.com \
--to=shawn.lin@rock-chips$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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