From: Kalle Valo <kvalo@adurom.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] sdio: add new function for RAW (Read after Write) operation
Date: Mon, 17 May 2010 09:43:36 +0300 [thread overview]
Message-ID: <AANLkTil49xWUSeUCGk_EQgdfOUSnFyKv6xf-RW7RX661@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinEGhNI_n25FVZ4NrLr6ClNw3JVusnJVDZdQchn@mail.gmail.com>
On 14 May 2010 14:04, Grazvydas Ignotas <notasas@gmail.com> wrote:
> Hi Kalle,
Hi Grazvydas,
> On Wed, Apr 28, 2010 at 12:18 AM, Grazvydas Ignotas <notasas@gmail.com> wrote:
>> SDIO specification allows RAW (Read after Write) operation using
>> IO_RW_DIRECT command (CMD52) by setting the RAW bit. This operation is
>> similar to ordinary read/write commands, except that both write and read
>> are performed using single command/response pair. The Linux SDIO layer
>> already supports this internaly, only external function is missing for
>> drivers to make use, which is added by this patch.
>>
>> This type of command is required to implement proper power save mode
>> support in wl1251 wifi driver.
>
> As wl1251 maintainer, can you confirm this is needed for wl1251 driver
> to function in SDIO mode? Perhaps this could help convince Andrew to
> merge this patch. Without this the chip is having problems leaving ELP
> mode.
Yes, this is needed for wl1251 (and I would assume also for wl1271) to
wake up firmware from it's sleep state, also called as the ELP mode. A
TI engineer has confirmed this for me.
Kalle
prev parent reply other threads:[~2010-05-17 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 21:18 [PATCH] sdio: add new function for RAW (Read after Write) operation Grazvydas Ignotas
2010-05-14 11:04 ` Grazvydas Ignotas
2010-05-14 22:06 ` Andrew Morton
2010-05-15 0:02 ` Dmitry Shmidt
2010-05-15 12:16 ` Grazvydas Ignotas
2010-05-15 16:25 ` Dmitry Shmidt
2010-05-15 20:46 ` Grazvydas Ignotas
2010-05-17 6:43 ` Kalle Valo [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=AANLkTil49xWUSeUCGk_EQgdfOUSnFyKv6xf-RW7RX661@mail.gmail.com \
--to=kvalo@adurom.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mmc@vger.kernel.org \
--cc=notasas@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;
as well as URLs for NNTP newsgroup(s).