From: David Vrabel <david.vrabel@csr.com>
To: linux-kernel@vger.kernel.org, Pierre Ossman <drzeus-list@drzeus.cx>
Cc: David Vrabel <david.vrabel@csr.com>
Subject: [patch 0/5] sdio: various bug fixes and CSR specific support
Date: Fri, 10 Aug 2007 13:24:08 +0100 [thread overview]
Message-ID: <46BC58E8.50300@csr.com> (raw)
This set of 5 patches fixes a few bugs in the SDIO support and adds
stuff required for CSR chips.
1. SHDC PCI cards produced by Arasan (for prototyping their SHDC IP)
report an invalid maximum block size. These cards don't have a valid
vendor or device ID so we can't blacklist them. Instead, just assume we
can always support a block size of 512 (which is the minimum possible).
2. Ensure we set the bus width the host uses if we set the card's bus
width to 4 bit mode. Needless to say a host sending 1 bit mode data to
a card in 4 bit mode doesn't work.
3. Add defines for CSR specific CCCR vendor registers.
4. Add vendor and device IDs for CSR chips.
5. Add sdio_f0_readb() and sdio_f0_writeb() so drivers can read/write F0
registers.
David
--
David Vrabel, Software Engineer, Drivers group Tel: +44 (0)1223 692562
CSR plc, Churchill House, Cambridge Business Park, Cowley Road, CB4 0WZ
.
next reply other threads:[~2007-08-10 12:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 12:24 David Vrabel [this message]
2007-08-10 12:25 ` mmc: ignore bad max block size in sdhci David Vrabel
2007-08-10 13:34 ` Pierre Ossman
2007-08-10 12:27 ` sdio: set host bus width David Vrabel
2007-08-10 13:35 ` Pierre Ossman
2007-08-10 13:46 ` David Vrabel
2007-08-10 12:28 ` sdio: add <linux/mmc/sdio_csr.h> for CSR specific CCCR registers David Vrabel
2007-08-10 12:59 ` Marcel Holtmann
2007-08-10 13:00 ` David Vrabel
2007-08-10 13:37 ` Pierre Ossman
2007-08-10 12:28 ` sdio: add CSR vendor/device IDs David Vrabel
2007-08-10 13:37 ` Pierre Ossman
2007-08-10 12:29 ` [patch 5/5] sdio: add sdio_f0_readb() and sdio_f0_writeb() David Vrabel
2007-08-10 13:38 ` 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=46BC58E8.50300@csr.com \
--to=david.vrabel@csr.com \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
/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