LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: dbrownell@users.sourceforge.net, mikael.starvik@axis.com,
	spi-devel-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 4/5: Updates to SPI and mmc_spi: mmc_spi updated, kernel 2.6.19
Date: Fri, 26 Jan 2007 17:49:22 +0100	[thread overview]
Message-ID: <45BA3112.503@drzeus.cx> (raw)
In-Reply-To: <200701250453.l0P4rjHN017189@ignucius.se.axis.com>

Hans-Peter Nilsson wrote:
> 
> Future improvements:
> A rewrite.  Not only for the new MMC framework (I haven't looked
> at it so I don't know what's involved) but also because this
> code seems a little too, um, experimental to fit my taste.
> Functions go behind each other's back and look at and change
> data; they seem to "fix up" the result of each others work.
> It doesn't help maintenance.
> 

Right, this isn't getting merged anywhere near its current state. It
should be implemented as a host driver and we'll modify the mmc core
where needed to cover the differences when doing spi.

As for my "new framework", it's mostly reorganising the stuff already
there. But any patches will have to be reworked after that change. So
I'd suggest holding off on this for a while.

> Support SDIO and SDHC.  SDIO fails over already when mmc_spi
> sees CMD5 and reports that it's invalid.  This is mostly about
> mapping commands and reply-types, but also support for the SDIO
> interrupt line.  Ok, I guess this can't be properly defined
> before the SDIO and SDHC support at the MMC layer is clear. :)
> 

The response type problem is exactly the kind of problem that should be
solved by moving spi support into the mmc core.

> Better API.  The card-detect API should *at least optionally* be
> like the get_ro function.

I think this is so uncommon and involves so little code that it just
adds complexity to abstract it up to the core. Most hw get interrupts
for insertion/removal.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

  parent reply	other threads:[~2007-01-26 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25  4:53 Hans-Peter Nilsson
2007-01-25 13:02 ` David Brownell
2007-01-26 15:45   ` Hans-Peter Nilsson
2007-01-26 16:49 ` Pierre Ossman [this message]
2007-01-26 23:38   ` 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:
  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=45BA3112.503@drzeus.cx \
    --to=drzeus-mmc@drzeus.cx \
    --cc=dbrownell@users.sourceforge.net \
    --cc=hans-peter.nilsson@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikael.starvik@axis.com \
    --cc=spi-devel-general@lists.sourceforge.net \
    --subject='Re: [PATCH] 4/5: Updates to SPI and mmc_spi: mmc_spi updated, kernel 2.6.19' \
    /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

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