From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Ben Dooks <ben-linux@fluff.org>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-kernel@vger.kernel.org, sdhci-devel@list.drzeus.cx
Subject: Re: [patch 5/7] SDHCI: Samsung SDHCI (HSMMC) driver
Date: Wed, 19 Nov 2008 19:38:36 +0100 [thread overview]
Message-ID: <20081119193836.74cc2ee8@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20081116000302.GD9161@fluff.org.uk>
On Sun, 16 Nov 2008 00:03:02 +0000
Ben Dooks <ben-linux@fluff.org> wrote:
> On Fri, Nov 14, 2008 at 10:48:13PM +0100, Pierre Ossman wrote:
> > On Mon, 03 Nov 2008 20:09:49 +0000
> > Ben Dooks <ben-linux@fluff.org> wrote:
> > > + if (pdata->cfg_card)
> > > + pdata->cfg_card(ourhost->pdev, host->ioaddr,
> > > + ios, host->mmc->card);
> >
> > What's the deal here? Hosts shouldn't know more about the card than the
> > MMC core tells them.
>
> Depending on exactly which version, there's a number of configurations
> in the extra configuration registers that get changed, such as delays
> used for clock feedback which are meant to be chnaged when the speed
> of the card is changed. Unfortunately this changes depending on the
> chip model and possibly also on the board it is on.
>
> The other is that it is possible that depending on the chip and board
> combination things like the GPIO driver-strength controls will need to
> be changed.
I don't see where knowledge about the card gets into the picture here.
All of this sounds like information that is gathered from platform data
and/or ios information.
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
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.
next prev parent reply other threads:[~2008-11-19 18:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 20:09 [patch 0/7] SDHCI support for Samsung SoC Ben Dooks
2008-11-03 20:09 ` [patch 1/7] SDHCI: Add timeout hooks Ben Dooks
2008-11-14 21:29 ` Pierre Ossman
2008-11-03 20:09 ` [patch 2/7] SDHCI: Print ADMA status and pointer on debug Ben Dooks
2008-11-14 21:29 ` Pierre Ossman
2008-11-03 20:09 ` [patch 3/7] SDHCI: Add set_ios hook Ben Dooks
2008-11-14 21:32 ` Pierre Ossman
2008-11-03 20:09 ` [patch 4/7] SDHCI: Add quirk for controller with no end-of-busy IRQ Ben Dooks
2008-11-14 21:41 ` Pierre Ossman
2008-11-15 23:58 ` Ben Dooks
2008-11-03 20:09 ` [patch 5/7] SDHCI: Samsung SDHCI (HSMMC) driver Ben Dooks
2008-11-14 21:48 ` Pierre Ossman
2008-11-16 0:03 ` Ben Dooks
2008-11-19 18:38 ` Pierre Ossman [this message]
2008-11-03 20:09 ` [patch 6/7] SDHCI: Check DMA for overruns at end of transfer Ben Dooks
2008-11-03 21:12 ` Henrique de Moraes Holschuh
2008-11-03 21:16 ` Ben Dooks
2008-11-04 1:28 ` Henrique de Moraes Holschuh
2008-11-10 9:58 ` Ben Dooks
2008-11-14 22:00 ` Pierre Ossman
2008-11-16 0:05 ` Ben Dooks
2008-11-19 18:41 ` Pierre Ossman
2008-11-03 20:09 ` [patch 7/7] SDHCI: Add change_clock callback for glue drivers Ben Dooks
2008-11-14 22:20 ` Pierre Ossman
2008-11-15 23:57 ` Ben Dooks
2008-11-19 18:43 ` Pierre Ossman
2008-11-10 10:57 ` [patch 0/7] SDHCI support for Samsung SoC Ben Dooks
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=20081119193836.74cc2ee8@mjolnir.drzeus.cx \
--to=drzeus-mmc@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
Powered by JetHome