From: Pierre Ossman <drzeus@drzeus.cx>
To: Ben Dooks <ben-linux@fluff.org>
Cc: sdhci-devel@list.drzeus.cx, linux-kernel@vger.kernel.org,
Ben Dooks <ben-linux@fluff.org>
Subject: Re: [patch 5/8] SDHCI: Samsung SDHCI (HSMMC) driver
Date: Sun, 21 Dec 2008 14:32:29 +0100 [thread overview]
Message-ID: <20081221143229.54a7d5ff@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20081202154112.640260459@fluff.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1814 bytes --]
On Tue, 02 Dec 2008 15:40:23 +0000
Ben Dooks <ben-linux@fluff.org> wrote:
> Index: linux.git/drivers/mmc/host/Kconfig
> ===================================================================
> --- linux.git.orig/drivers/mmc/host/Kconfig 2008-12-01 23:18:20.000000000 +0000
> +++ linux.git/drivers/mmc/host/Kconfig 2008-12-01 23:25:18.000000000 +0000
> @@ -48,6 +48,18 @@ config MMC_SDHCI_PCI
>
> If unsure, say N.
>
> +config MMC_SDHCI_S3C
> + tristate "SDHCI support on Samsung S3C SoC"
> + depends on MMC_SDHCI && (PLAT_S3C24XX || PLAT_S3C64XX)
> + help
> + This selects the Secure Digital Host Controller Interface (SDHCI)
> + often referrered to as the HSMMC block in some of the Samsung S3C
> + range of SoC.
> +
> + If you have a controller with this interface, say Y or M here.
> +
> + If unsure, say N.
> +
> config MMC_RICOH_MMC
> tristate "Ricoh MMC Controller Disabler (EXPERIMENTAL)"
> depends on MMC_SDHCI_PCI
You should probably put it under MMC_RICOH_MMC as that will become a
subentry under MMC_SDHCI_PCI.
> +static void sdhci_s3c_set_ios(struct sdhci_host *host,
> + struct mmc_ios *ios)
> +{
> + struct sdhci_s3c *ourhost = to_s3c(host);
> + struct s3c_sdhci_platdata *pdata = ourhost->pdata;
> +
> + if (pdata->cfg_card)
> + pdata->cfg_card(ourhost->pdev, host->ioaddr, ios);
> +}
I'm still waiting for a proper reason to allow this hook. Since you've
added this, I assume you have at least one implementation of cfg_card.
Care to include that so that I can see what it is you're trying to do?
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-21 13:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 15:40 [patch 0/8] Update Samsung SDHCI Ben Dooks
2008-12-02 15:40 ` [patch 1/8] SDHCI: Add timeout hooks Ben Dooks
2008-12-02 16:46 ` smohideen
2008-12-21 13:16 ` Pierre Ossman
2008-12-02 15:40 ` [patch 2/8] SDHCI: Print ADMA status and pointer on debug Ben Dooks
2008-12-02 15:40 ` [patch 3/8] SDHCI: Add set_ios hook Ben Dooks
2008-12-21 13:22 ` Pierre Ossman
2008-12-02 15:40 ` [patch 4/8] SDHCI: Add quirk for controller with no end-of-busy IRQ Ben Dooks
2008-12-02 15:40 ` [patch 5/8] SDHCI: Samsung SDHCI (HSMMC) driver Ben Dooks
2008-12-21 13:32 ` Pierre Ossman [this message]
2008-12-02 15:40 ` [patch 6/8] SDHCI: Check DMA for overruns at end of transfer Ben Dooks
2008-12-21 13:49 ` Pierre Ossman
2008-12-02 15:40 ` [patch 7/8] SDHCI: Add change_clock callback for glue drivers Ben Dooks
2008-12-21 14:07 ` Pierre Ossman
2008-12-02 15:40 ` [patch 8/8] SDHCI: Add maintainers entry for Samsung SoC Ben Dooks
2008-12-21 14:09 ` Pierre Ossman
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=20081221143229.54a7d5ff@mjolnir.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=ben-linux@fluff.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®