From: "Madhusudhan" <madhu.cr@ti.com>
To: 'John Rigby' <jcrigby@gmail.com>
Cc: 'Mike Rapoport' <mike@compulab.co.il>,
'Dirk Behme' <dirk.behme@googlemail.com>,
'Phaneendra Kumar Alapati' <phani@embwise.com>,
linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org,
'Adrian Hunter' <adrian.hunter@nokia.com>,
"'Paasikivi Teemu.3 (EXT-Ixonos/Tampere)'"
<ext-teemu.3.paasikivi@nokia.com>,
"'Gabay, Benzy'" <benzyg@ti.com>
Subject: RE: sdio irq hack for omap_hsmmc.c (was: Re: [PATCH] OMAP35xx:SDIO IRQ Support for OMAP35xx)
Date: Thu, 28 Jan 2010 17:52:44 -0600 [thread overview]
Message-ID: <000801caa074$fca47fd0$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <4b73d43f1001271556m5945d358v2ca5bea5862b0080@mail.gmail.com>
Hi,
I am not an SDIO expert. But what I understand from this is that we are
missing the wakeup capability on an SDIO interrupt.
Regards,
Madhu
> -----Original Message-----
> From: John Rigby [mailto:jcrigby@gmail.com]
> Sent: Wednesday, January 27, 2010 5:56 PM
> To: Madhusudhan
> Cc: Mike Rapoport; Dirk Behme; Phaneendra Kumar Alapati; linux-
> omap@vger.kernel.org; linux-mmc@vger.kernel.org; Adrian Hunter; Paasikivi
> Teemu.3 (EXT-Ixonos/Tampere)
> Subject: Re: sdio irq hack for omap_hsmmc.c (was: Re: [PATCH]
> OMAP35xx:SDIO IRQ Support for OMAP35xx)
>
> Just to be clear, my post was in response to the reported problems
> with enabling sdio irqs with this patch:
> http://patchwork.kernel.org/patch/69122/
>
> The patch originator reported good results but others reported
> complete failure. My hack fixed the problem for me. I believe this
> much more modest patch will also fix the problem but it is untested
> because I don't have a board running right now. Beware, I'm sending
> this from gmail so it may get line wrapped but it is a trivial patch
> so I think it is understandable.
>
> John
>
> diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
> index fa94580..7af970e 100644
> --- a/drivers/mmc/host/omap_hsmmc.c
> +++ b/drivers/mmc/host/omap_hsmmc.c
> @@ -1727,10 +1727,16 @@ static int __init omap_hsmmc_probe
>
> omap_hsmmc_context_save(host);
>
> +#if 0
> mmc->caps |= MMC_CAP_DISABLE;
> mmc_set_disable_delay(mmc, OMAP_MMC_DISABLED_TIMEOUT);
> /* we start off in DISABLED state */
> host->dpm_state = DISABLED;
> +#else
> + /* we start off in ENABLED state */
> + host->dpm_state = ENABLED;
> + clk_enable(host->fclk);
> +#endif
>
> if (mmc_host_enable(host->mmc) != 0) {
> clk_put(host->iclk);
>
>
> On Wed, Jan 27, 2010 at 4:14 PM, Madhusudhan <madhu.cr@ti.com> wrote:
> > It is hard to comment on what is happening here without a patch. Is it a
> > performance issue or that SDIO functionality failure with PM enabled?
> >
> > The MMC controller supports wakeup capability on the dat1 line using a
> GPIO
> > for a SDIO interrupt. I guess that should help.
> >
> > Regards,
> > Madhu
> >
next prev parent reply other threads:[~2010-01-28 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 17:04 sdio irq hack for omap_hsmmc.c (was: Re: [PATCH] OMAP35xx:SDIO IRQ Support for OMAP35xx) John Rigby
2010-01-27 23:14 ` Madhusudhan
2010-01-27 23:56 ` John Rigby
2010-01-28 23:52 ` Madhusudhan [this message]
2010-01-29 0:13 ` Kevin Hilman
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='000801caa074$fca47fd0$544ff780@am.dhcp.ti.com' \
--to=madhu.cr@ti.com \
--cc=adrian.hunter@nokia.com \
--cc=benzyg@ti.com \
--cc=dirk.behme@googlemail.com \
--cc=ext-teemu.3.paasikivi@nokia.com \
--cc=jcrigby@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=phani@embwise.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