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 15:45:09 +0200 [thread overview]
Message-ID: <4CAC7D65.8010705@compulab.co.il> (raw)
In-Reply-To: <AANLkTi=kmLuUyD-9k-Xa5vfgvjx2nNUGfyADhoY0HC1i@mail.gmail.com>
Hi Steve,
Steve Sakoman wrote:
> On Tue, Oct 5, 2010 at 11:17 PM, Mike Rapoport <mike@compulab.co.il> wrote:
>
>> 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 :-(
>
> I tried my hand at making the patch apply on 2.6.35:
>
> http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=commitdiff;h=51b802d73191c306618cddefbd63379c839589f5
This one fails to build:
CC drivers/mmc/host/omap_hsmmc.o
drivers/mmc/host/omap_hsmmc.c: In function 'omap_hsmmc_start_command':
drivers/mmc/host/omap_hsmmc.c:791: warning: unused variable 'int_en_mask'
drivers/mmc/host/omap_hsmmc.c: In function 'omap_hsmmc_do_irq':
drivers/mmc/host/omap_hsmmc.c:1023: error: label 'out' used but not defined
drivers/mmc/host/omap_hsmmc.c: In function 'omap_hsmmc_irq':
drivers/mmc/host/omap_hsmmc.c:1101: warning: label 'out' defined but not used
drivers/mmc/host/omap_hsmmc.c: In function 'omap_hsmmc_suspend':
drivers/mmc/host/omap_hsmmc.c:2346: warning: unused variable 'state'
make[4]: *** [drivers/mmc/host/omap_hsmmc.o] Error 1
Moving the 'out' label where I believe it should live I get:
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas: command 0x0003 timed out
libertas: Timeout submitting command 0x0003
libertas: PREP_CMD: command 0x0003 failed: -110
libertas_sdio: probe of mmc1:0001:1 failed with error -110
>
> It seems to work, but I'm pretty sure I must have messed something up
> because I get error messages every once in a while:
>
> libertas: tx watch dog timeout
>
> I don't recall seeing these with the original version of the patch :-(
>
> Suggestions as to where I went wrong are welcome!
I've "applied" the patch almost the same way you did and I was not able to get
any further than the point above (command 0x0003 timed out). As far as I
understand, what we have now is that omap_hsmmc_request_done() calls
omap_hsmmc_disable_irq() and the interrupts that come from the 8686 _between_
requests are simply missed. Whatever I've tried to keep the SDIO interrupts on
didn't help... :(
> Steve
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2010-10-06 13:45 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
2010-10-06 12:55 ` Steve Sakoman
2010-10-06 13:45 ` Mike Rapoport [this message]
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=4CAC7D65.8010705@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.