LKML Archive on
help / color / mirror / Atom feed
From: David Brownell <>
To: "Hans-Peter Nilsson" <>
Subject: Re: 5 patches: updates to SPI and mmc_spi, kernel 2.6.19
Date: Thu, 25 Jan 2007 04:59:37 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wednesday 24 January 2007 8:47 pm, Hans-Peter Nilsson wrote:
> (Please CC me on replies, I'm not subscribed to LKML.  Thanks.)
> Five SPI-related patches follow.
> 1: bugfix for spi_bitbang: always call the setup_transfer
> function via the overridable pointer.
> 2: Allow clocking SPI with chip-select inactive.
> 3: Define the bit-value transmitted for SPI transfers with no tx_buf.
> 4: Update of David B.'s (et al) kind-of-proof-of-concept
> MMC <-> SPI glue driver mmc_spi posted on Aug 1, found at e.g.
> <URL:>.
> 5: SPI cleanup should not have const on its argument.

Cool ... two of those (#1, #5) seem ok to merge right now, and
I expect that #2 can go in with only minor tweaks.

#3 needs more attention (see my response) and I'll have to look
at #4 soon.

Thanks for looking at this.  I know various folk have needed to
have MMC/SD working over SPI for some time, and was hoping that
someone else would make time to take that code the next few steps
on the way.  Just like you did!

So to summarize ... you now have MMC-over-SPI working on CRIS
hardware, with these patches?   Can you yet run filesystem
stress tests with ext3 on such an MMC card, or is this more at
the level of everything working with light/early test loads,
so it's time to see if other folk can reproduce your results?

- Dve

  reply	other threads:[~2007-01-25 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25  4:47 Hans-Peter Nilsson
2007-01-25 12:59 ` David Brownell [this message]
2007-01-26 14:31   ` Hans-Peter Nilsson
2007-01-26 23:23     ` David Brownell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: 5 patches: updates to SPI and mmc_spi, kernel 2.6.19' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).