From: Mike Rapoport <mike@compulab.co.il>
To: Steve Sakoman <sakoman@gmail.com>
Cc: Madhusudhan <madhu.cr@ti.com>,
David Vrabel <david.vrabel@csr.com>, Chris Ball <cjb@laptop.org>,
linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org,
Adrian Hunter <adrian.hunter@nokia.com>,
Mike Rapoport <mike@compulab.co.il>
Subject: Re: [PATCH 0/2] mmc: omap_hsmmc: support SDIO cards (#2)
Date: Wed, 06 Oct 2010 08:17:17 +0200 [thread overview]
Message-ID: <4CAC146D.3040001@compulab.co.il> (raw)
In-Reply-To: <AANLkTin-r5Svg1+YrdYq95WA6=sh7+X0Bwogk=h0V6pP@mail.gmail.com>
Steve Sakoman wrote:
> On Mon, Oct 4, 2010 at 10:33 AM, Madhusudhan <madhu.cr@ti.com> wrote:
>>
>>> -----Original Message-----
>>> From: Steve Sakoman [mailto:sakoman@gmail.com]
>>> Sent: Monday, October 04, 2010 11:57 AM
>>> To: Madhusudhan
>>> Cc: Mike Rapoport; David Vrabel; Chris Ball; linux-mmc@vger.kernel.org;
>>> linux-omap@vger.kernel.org
>>> Subject: Re: [PATCH 0/2] mmc: omap_hsmmc: support SDIO cards (#2)
>>>
>>> On Mon, Oct 4, 2010 at 9:45 AM, Madhusudhan <madhu.cr@ti.com> wrote:
>>>>
>>>>> -----Original Message-----
>>>>> From: Steve Sakoman [mailto:sakoman@gmail.com]
>>>>> Sent: Monday, October 04, 2010 11:32 AM
>>>>> To: Mike Rapoport
>>>>> Cc: David Vrabel; Chris Ball; linux-mmc@vger.kernel.org; linux-
>>>>> omap@vger.kernel.org; madhu.cr@ti.com
>>>>> Subject: Re: [PATCH 0/2] mmc: omap_hsmmc: support SDIO cards (#2)
>>>>>
>>>>> On Wed, Sep 1, 2010 at 11:02 PM, Mike Rapoport <mike@compulab.co.il>
>>>>> wrote:
>>>>>> David Vrabel wrote:
>>>>>>> On 27/08/2010 20:22, Chris Ball wrote:
>>>>>>>> Hi David,
>>>>>>>>
>>>>>>>> On Mon, Feb 22, 2010 at 02:24:17PM +0000, David Vrabel wrote:
>>>>>>>>> These patches add support for SDIO cards to the omap_hsmmc driver.
>>>>>>>>> Power management changes to prevent SDIO cards from being turned
>>> off
>>>>>>>>> and losing all state, and card interrupts.
>>>>>>>>>
>>>>>>>>> I've been unable to test these exact patches as I only have an
>>> N900
>>>>> for
>>>>>>>>> testing and the N900 support in mainline is incomplete.
>>>>>>>>>
>>>>>>>>> Changes since v1:
>>>>>>>>> - (hopefully) get all cards working again by removing a second
>>> call
>>>>> to
>>>>>>>>> read MMCi_STAT in the interrupt handler.
>>>>>>>>> - flush posted writes after enabling/disabling SDIO interrupts.
>>>>>>>>> - tweak the FIXME commit on disabling FCLK to better match what
>>>>> really
>>>>>>>>> going on (at least I think so anyway).
>>>>>>>>>
>>>>>>>>> David Vrabel (2):
>>>>>>>>> mmc: omap_hsmmc: don't turn SDIO cards off when idle
>>>>>>>>> mmc: omap_hsmmc: enable SDIO card interrupts
>>>>>>>> Looks like this patchset wasn't merged. Mike Rapoport replied with
>>> a
>>>>> fix
>>>>>>>> for libertas. Would you like to resubmit it?
>>>>>>> I thought Madhu had picked this up and was going to submit it.
>>>>>>>
>>>>>>> Regardless of whether that is the case, I think it needs to be
>>>>> submitted
>>>>>>> by someone who can run mainline kernels (I can't) and ideally
>>> someone
>>>>>>> who can test it with SDIO cards.
>>>>>> I'll try to update the patches in the next few days.
>>>>> Any update on the status of these patches? I'm happy to help test!
>>>>>
>>>> Steve,
>>>>
>>>> I have not been able to test SDIO card interrupts. If you could help
>>> test
>>>> that it's great.
>>> Where can I grab the most recent patches? The original set don't apply
>>> cleanly.
>>>
>> Yes. They may not apply. I can rebase them and send it to you for testing.
>> Are you using the two patches posted by David Vrabel?
>
> Yes, I've been using the original patches on 2.6.33 and 2.6.34. The
> SDIO interrupt patch doesn't apply on 2.6.35 or 36.
>
> If you send a revised patch for either I would be happy to test as
> soon as I get it.
I've tried to update the patches on top of 2.6.36-rc3 and I've got stuck.
The changes Adrian has made to the interrupt synchronization affect the way the
SDIO irq should be implemented and I haven't found a way to resolve it :-(
> Steve
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2010-10-06 6:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 14:24 [PATCH 0/2] mmc: omap_hsmmc: support SDIO cards (#2) David Vrabel
2010-02-22 14:24 ` [PATCH 1/2] mmc: omap_hsmmc: don't turn SDIO cards off when idle David Vrabel
2010-02-22 14:24 ` [PATCH 2/2] mmc: omap_hsmmc: enable SDIO card interrupts David Vrabel
2010-02-22 14:55 ` [PATCH 0/2] mmc: omap_hsmmc: support SDIO cards (#2) Felipe Contreras
2010-02-22 15:11 ` David Vrabel
2010-02-22 15:50 ` Felipe Contreras
2010-02-24 10:07 ` Mike Rapoport
2010-08-27 19:22 ` Chris Ball
2010-08-31 8:59 ` David Vrabel
2010-09-01 18:07 ` mike
2010-09-02 6:02 ` Mike Rapoport
2010-10-04 16:32 ` Steve Sakoman
2010-10-04 16:45 ` Madhusudhan
2010-10-04 16:57 ` Steve Sakoman
2010-10-04 17:33 ` Madhusudhan
2010-10-04 18:09 ` Steve Sakoman
2010-10-06 6:17 ` Mike Rapoport [this message]
2010-10-06 12:55 ` Steve Sakoman
2010-10-06 13:45 ` Mike Rapoport
2010-10-06 15:22 ` Steve Sakoman
2010-10-06 18:28 ` Madhusudhan Chikkature
2010-10-06 19:02 ` David Vrabel
2010-10-06 19:21 ` Madhusudhan
2010-10-07 7:15 ` Mike Rapoport
2010-10-07 13:56 ` Steve Sakoman
2010-10-07 16:52 ` Madhusudhan
2010-10-07 17:56 ` Steve Sakoman
2010-10-10 6:50 ` Mike Rapoport
2010-10-29 11:33 ` Enric Balletbò i Serra
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=4CAC146D.3040001@compulab.co.il \
--to=mike@compulab.co.il \
--cc=adrian.hunter@nokia.com \
--cc=cjb@laptop.org \
--cc=david.vrabel@csr.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=sakoman@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.