From: Wolfram Sang <w.sang@pengutronix.de>
To: Peppe CAVALLARO <peppe.cavallaro@st.com>
Cc: Chris Ball <cjb@laptop.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH (mmc-next) 1/3] mmc: add suspend/resume in the sdhci-pltfm driver (V3)
Date: Mon, 4 Oct 2010 10:57:31 +0200 [thread overview]
Message-ID: <20101004085731.GA10746@pengutronix.de> (raw)
In-Reply-To: <4CA967F8.9030005@st.com>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
> In the near future I'll have to start using SDIO and eMMC devices.
> I wonder if I'll be able to continue to use the platform driver or if
> I'll need to actually have own driver (to solve specific limits/features
> .... due to our Hw) or if we'll extend the sdhci-pltfm d.d.
>
> What do you think?
First rule should be trying to extend pltfm. If all of the drafts we come up
with don't seem reasonable, the "own driver" solution is the fallback.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2010-10-04 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 8:41 [PATCH (mmc-next) 1/3] mmc: add suspend/resume in the sdhci-pltfm driver (V3) Giuseppe CAVALLARO
2010-09-28 8:41 ` [PATCH (mmc-next) 2/3] mmc: fix a warning when compile the sdhci d.d. (V2) Giuseppe CAVALLARO
2010-09-28 8:41 ` [PATCH (mmc-next) 3/3] mmc: split the sdhci.h to help platforms that uses shdci-pltfm " Giuseppe CAVALLARO
2010-09-28 11:14 ` Wolfram Sang
2010-09-28 11:09 ` [PATCH (mmc-next) 2/3] mmc: fix a warning when compile the sdhci " Wolfram Sang
2010-09-28 11:08 ` [PATCH (mmc-next) 1/3] mmc: add suspend/resume in the sdhci-pltfm driver (V3) Wolfram Sang
2010-09-30 23:25 ` Chris Ball
2010-10-01 7:07 ` Wolfram Sang
2010-10-04 5:36 ` Peppe CAVALLARO
2010-10-04 8:57 ` Wolfram Sang [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=20101004085731.GA10746@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=peppe.cavallaro@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox