From: "M. Warner Losh" <imp@bsdimp.com>
To: matt@genesi-usa.com
Cc: sdhci-devel@list.drzeus.cx, arnd@arndb.de, DaveLiu@freescale.com,
Joe.D'abbraccio@freescale.com, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, Konjin.Lai@freescale.com,
ben-linux@fluff.org, drzeus-sdhci@drzeus.cx, X.Xie@freescale.com
Subject: Re: [PATCH 10/10] mmc: Add OpenFirmware bindings for SDHCI driver
Date: Mon, 26 Jan 2009 15:26:20 -0700 (MST) [thread overview]
Message-ID: <20090126.152620.1498421823.imp@bsdimp.com> (raw)
In-Reply-To: <497C09D9.50004@genesi-usa.com>
In message: <497C09D9.50004@genesi-usa.com>
Matt Sealey <matt@genesi-usa.com> writes:
: Anton Vorontsov wrote:
: >
: > If unsure, say Y.
: >
: > +config MMC_SDHCI_OF
: > + tristate "SDHCI support on OpenFirmware platforms"
: > + depends on MMC_SDHCI && PPC_OF
: > + help
: > + This selects the OF Secure Digital Host Controller Interface.
: > + So far there is only Freescale eSDHC controller known to exists
: > + on OF platforms.
:
: Nit; would probably be better English as
:
: This selects the OF support for Secure Digital Host Controller
: Interfaces. So far, only the Freescale eSDHC controller is known
: to exist on OF platforms.
Is this the SD Association standard host controller interface, or a
custom one by Freescale? If the former, then I'd suggest:
This selects OF support for the SD Association standard Secure
Digital Host Controller Interface (version x.xx). So far,
only the Freescale eSDHC controller is the only example on OF
platforms.
if the latter:
This selects OF support for Freescale's custom Secure Digital
Host Controller Interface. So far, only the Freescale eSDHC
controller is the only example on OF platforms.
Warner
prev parent reply other threads:[~2009-01-26 22:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 1:56 [PATCH RFC 0/10] Freescale "eSDHC" SDHCI support (was [PATCH] mmc: Add driver for Freescale eSDHC controllers) Anton Vorontsov
2009-01-22 1:59 ` [PATCH 01/10] sdhci: Add quirk for controllers with no end-of-busy IRQ Anton Vorontsov
2009-01-22 2:00 ` [PATCH 02/10] sdhci: Add support for bus-specific IO memory accessors Anton Vorontsov
2009-01-22 11:55 ` Arnd Bergmann
2009-01-22 18:31 ` Anton Vorontsov
2009-01-22 2:00 ` [PATCH 03/10] sdhci: Add support for card-detection polling Anton Vorontsov
2009-01-22 2:00 ` [PATCH 04/10] sdhci: Add support for hosts reporting inverted write-protect state Anton Vorontsov
2009-01-22 2:00 ` [PATCH 05/10] sdhci: Add support for hosts with strict 32 bit addressing Anton Vorontsov
2009-01-22 2:00 ` [PATCH 06/10] sdhci: Add quirk to suppress PIO interrupts during DMA transfers Anton Vorontsov
2009-01-22 2:00 ` [PATCH 07/10] sdhci: Add support for hosts that don't specify clocks in the cap. register Anton Vorontsov
2009-01-22 2:00 ` [PATCH 08/10] sdhci: Add set_clock callback Anton Vorontsov
2009-01-22 2:00 ` [PATCH 09/10] sdhci: Add quirk for Freescale eSDHC controllers Anton Vorontsov
2009-01-22 2:00 ` [PATCH 10/10] mmc: Add OpenFirmware bindings for SDHCI driver Anton Vorontsov
2009-01-22 12:05 ` Arnd Bergmann
2009-01-22 19:15 ` Kumar Gala
2009-01-25 6:42 ` Matt Sealey
2009-01-26 22:26 ` M. Warner Losh [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=20090126.152620.1498421823.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=DaveLiu@freescale.com \
--cc=Joe.D'abbraccio@freescale.com \
--cc=Konjin.Lai@freescale.com \
--cc=X.Xie@freescale.com \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=drzeus-sdhci@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.com \
--cc=sdhci-devel@list.drzeus.cx \
/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).