From: Pierre Ossman <drzeus@drzeus.cx>
To: "Wolfgang Mües" <wolfgang.mues@auerswald.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Matt Fleming" <matt@console-pimps.org>,
"David Brownell" <dbrownell@users.sourceforge.net>,
linux-kernel@vger.kernel.org,
"Mike Frysinger" <vapier.adi@gmail.com>
Subject: Re: [PATCH] Fixes and enhancements for the MMC SPI driver - revised
Date: Sun, 8 Feb 2009 20:44:52 +0100 [thread overview]
Message-ID: <20090208204452.0ecdb18e@mjolnir.drzeus.cx> (raw)
In-Reply-To: <200901261418.19681.wolfgang.mues@auerswald.de>
[-- Attachment #1: Type: text/plain, Size: 2493 bytes --]
On Mon, 26 Jan 2009 14:18:19 +0100
Wolfgang Mües <wolfgang.mues@auerswald.de> wrote:
> Hi,
>
> thanks to all contributors who have reviewed my patch, especial to
> Andrew Morton for pointing out some problems.
>
> Here is a revised patch incl. changelog. I have though about putting
> some warnings in the message log with printk, Pierre. But this is low-level
> stuff and will likely flood the logfile.
>
There are some helpers to avoid flooding dmesg, but its a wish a not a
requirement so don't sweat it.
> changelog:
Please split these things up into one patch for each item. It keeps the
logs sensible and makes bisecting work better in case of problems.
> @@ -609,6 +616,18 @@ mmc_spi_writeblock(struct mmc_spi_host *
> struct spi_device *spi = host->spi;
> int status, i;
> struct scratch *scratch = host->data;
> + u32 pattern;
> + struct timeval tv;
> +
> + /*
> + * The MMC framework does a good job of computing timeouts
> + * according to the mmc/sd standard. However, we found that in
> + * SPI mode, there are many cards which need a longer timeout
> + * of 1s after receiving a long stream of write data.
> + */
> + tv = ktime_to_timeval(timeout);
> + if (tv.tv_sec == 0)
> + timeout = ktime_set(1, 0);
>
> if (host->mmc->use_spi_crc)
> scratch->crc_val = cpu_to_be16(
This might as well be handled when we compute the timeout in the core.
Having things spread out is just confusing.
> @@ -743,7 +777,12 @@ mmc_spi_readblock(struct mmc_spi_host *h
> return -EIO;
> }
>
> - if (host->mmc->use_spi_crc) {
> + /*
> + * Omit the CRC check for CID and CSD reads. There are some SDHC
> + * cards which don't supply a valid CRC after CID reads.
> + * Note that the CID has it's own CRC7 value inside the data block.
> + */
> + if (host->mmc->use_spi_crc && (t->len == MMC_SPI_BLOCKSIZE)) {
> u16 crc = crc_itu_t(0, t->rx_buf, t->len);
>
> be16_to_cpus(&scratch->crc_val);
Hmmm... I think this also better handled in the core. Reorder things in
the init to not turn CRC checks on until after those registers have
been read.
Other than that, the changes look fine. So split them up and I can
queue them up for the next merge window.
Rgds
--
-- 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:[~2009-02-08 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090113015904.606e3548.akpm@linux-foundation.org>
2009-01-26 13:18 ` Wolfgang Mües
2009-02-08 19:44 ` Pierre Ossman [this message]
2009-02-09 11:53 ` Wolfgang Mües
2009-02-21 14:16 ` 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=20090208204452.0ecdb18e@mjolnir.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=vapier.adi@gmail.com \
--cc=wolfgang.mues@auerswald.de \
/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®