Re: What's in mmc.git for 2.6.24

Previous thread: "cat /proc/20502/wchan" vs strace vs man page by Johan Walles on Monday, September 24, 2007 - 3:54 am. (1 message)

Next thread: [RFC][PATCH] mm: couple rcu and memory reclaim by Peter Zijlstra on Monday, September 24, 2007 - 4:45 am. (8 messages)
To: LAK <linux-arm-kernel@...>, LKML <linux-kernel@...>
Date: Monday, September 24, 2007 - 4:28 am

The merge window for 2.6.24 should open up any day now, so it's
probably time for me to detail what I intend to cram in there.

This release will probably be one of the biggest ones for the MMC layer
so far. The major pieces are SDIO and SPI support, but there are
several small nuggets as well.

SDIO
----

Gone are the days of having to rely on proprietary stacks for SDIO
support in Linux. So no more spotty support for hosts and possible GPL
problems. SDIO will now be a standard feature of Linux.

The model is largely based on PCI. All the memory operations they have
(readX/writeX and friends) exist in an equivalent manner for SDIO. We
also have the readsb() and writesb() functions which exist only on some
platforms for "normal" I/O. (For those not familiar with these
functions, they write every byte of a block of data into a single
byte in the address space.)

The big difference from other buses is that you have to hold the host
lock (which has gotten SDIO wrappers for ease of use), and that all I/O
operations may sleep.

There has been some talk about asynchronous requests, but that doesn't
really make much sense for a bus like SDIO where you don't interleave
transfers.

Interrupt support is also there and uses an interface similar to other
buses. It is called from process context though (currently a dedicated
kernel thread handles interrupts). Your ISR will also be called with
the host lock held, so keep the ISR short and try delegate what you
can. The only MUST is that you must remove the interrupt source before
you exit.

There are currently three working drivers for this new stack:

- sdio_uart: A driver for the standardised GPS and UART interfaces.
Currently we only know how the GPS system works, so UART is only a
future possibility.

- libertas_sdio: Support for Marvell's 8686 Libertas wifi chip. Will
be merged late in the merge window as there are some interdependencies
between my tree and the libertas tree.

- hci_sdio: A driver for the standardised bluet...

To: Pierre Ossman <drzeus-list@...>
Cc: LAK <linux-arm-kernel@...>, LKML <linux-kernel@...>
Date: Monday, September 24, 2007 - 5:47 am

where can I get this driver? I have a bunch of SDIO WiFi cards that

The driver name will be btsdio and I will merge the initial version
within the 2.4.24 merge window. However this driver will go in via the
Bluetooth subsystem. My only request is that we can do the MMC merge
really early in the merge window.

Regards

Marcel

-

To: Marcel Holtmann <marcel@...>
Cc: LAK <linux-arm-kernel@...>, LKML <linux-kernel@...>
Date: Monday, September 24, 2007 - 12:50 pm

On Mon, 24 Sep 2007 11:47:59 +0200

If you just want to determine if they have the chip or not, then just
examine the debug output my current sdio tree spews out. Libertas chips

My plan is to do it immediately when Linus says go.

Rgds
--
-- Pierre Ossman

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

Previous thread: "cat /proc/20502/wchan" vs strace vs man page by Johan Walles on Monday, September 24, 2007 - 3:54 am. (1 message)

Next thread: [RFC][PATCH] mm: couple rcu and memory reclaim by Peter Zijlstra on Monday, September 24, 2007 - 4:45 am. (8 messages)