From: Pierre Ossman <drzeus-list@drzeus.cx>
To: pierre Tardy <tardyp@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] New MMC driver model
Date: Wed, 10 Jan 2007 21:34:15 +0100 [thread overview]
Message-ID: <45A54DC7.4060403@drzeus.cx> (raw)
In-Reply-To: <loom.20070109T150821-717@post.gmane.org>
(Please keep me as cc as I will almost always overlook you replies
otherwise)
pierre Tardy wrote:
> Pierre Ossman <drzeus-list <at> drzeus.cx> writes:
>
>> Register functions
>> ==================
>>
>> I also intend to write a couple of register functions (sdio_read[bwl])
>> so that card drivers doesn't have to deal with MMC requests more than
>> necessary.
>
> Good idea. Another need may be a sdio_read[bwl]_sync, which will poll for the
> end of the cmd52s, instead of waiting for the irq. This polling is faster than
> wait_for_completion/irq/tasklet/complete mechanism, which involve several
> context switches.
>
Hadn't thought of that. I will have to do some tests once I have
something functional.
>> Endianness can also be handled there (SDIO are always LE).
> I dont remember sdio spec forcing HW registers to be LE. Function 0 registers
> are (BLKSZ for ex), but Function 1-7 register may be BE if the designers found
> an advantage to it..
>
Hmm... It's been a while since I read the spec, but perhaps the LE
requirement was only for the base registers.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
prev parent reply other threads:[~2007-01-10 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 13:23 [RFC] New MMC driver model Pierre Ossman
2006-06-20 9:35 ` Marcel Holtmann
2006-06-20 12:46 ` Pierre Ossman
2006-06-20 17:46 ` Marcel Holtmann
2007-01-09 14:25 ` pierre Tardy
2007-01-10 20:34 ` Pierre Ossman [this message]
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=45A54DC7.4060403@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=tardyp@gmail.com \
/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