From: Tony Lindgren <tony@atomide.com>
To: Andreas Fenkart <andreas.fenkart@streamunlimited.com>
Cc: Daniel Mack <zonque@gmail.com>, Chris Ball <cjb@laptop.org>,
devicetree-discuss@lists.ozlabs.org, linux-mmc@vger.kernel.org,
linux-omap@vger.kernel.org, santosh.shilimkar@ti.com
Subject: Re: omap_hsmmc: SDIO IRQ on AM335x family
Date: Thu, 3 Jan 2013 11:48:51 -0800 [thread overview]
Message-ID: <20130103194851.GH25633@atomide.com> (raw)
In-Reply-To: <20121220220444.GA350@blumentopf>
* Andreas Fenkart <andreas.fenkart@streamunlimited.com> [121220 14:07]:
> Hi,
>
> On Fri, Nov 30, 2012 at 07:57:35PM +0100, Daniel Mack wrote:
> >
> > On 30.11.2012 18:40, Tony Lindgren wrote:
> > > * Andreas Fenkart <andreas.fenkart@streamunlimited.com> [121130 03:21]:
> > >>
> > >> The alternative was to configure dat1 line as a GPIO, while
> > >> waiting for an IRQ. Then configuring it back as dat1 when the
> > >> SDIO card is signalling an IRQ. Or the host starts a transfer. I
> > >> guess this will perform poorly, hence not considering it really.
> > >
> > > This might work for SDIO cards. It should be disabled for data
> > > cards naturally to avoid potential data corruption.
> I don't understand your concern here, could you explain
>
> > > The way to implement this is set named states in the .dts file
> > > for the pins using pinctrl-single.c, then have the MMC driver
> > > request states "default" "active" and "idle" during the probe,
> > > then toggle between active and idle during the runtime.
> > >
> > > As far as I remember the GPIO functionality does not need to
> > > be enabled, just muxing the pin to GPIO mode for the wake-up
> > > is enough.
> >
> > Wouldn't that be racy, given that an interrupt which occurs at beween
> > the point in time when the driver decides to wait for IRQs again until
> > the mux has finished switching over, could potentially be lost?
>
> The IRQ is level triggered, so can't be lost. I implemented it as
> suggested and surprisingly performance is pretty good. Actually not
> worse than keeping the fclk enabled all times.
>
> module: 88W8787 / mwifiex
> tx bitrate: 150.0 MBit/s MCS 7 40Mhz short GI
>
> | tcp tx | signal | cpu idle
> ---------------------------------------------------------------
> keep fclk enabled | 50.3 Mbits/sec | -23 dBm | 15 %
> suspend/resume | 49.7 Mbits/sec | -22 dBM | 13 %
>
> patch follows
Hey that's cool :) Will take a look at the patch.
Tony
prev parent reply other threads:[~2013-01-03 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 11:18 omap_hsmmc: SDIO IRQ on AM335x family Andreas Fenkart
2012-11-30 17:40 ` Tony Lindgren
2012-11-30 18:57 ` Daniel Mack
2012-12-20 22:04 ` Andreas Fenkart
2012-12-20 22:12 ` [PATCH] mmc: omap_hsmmc: Enable SDIO IRQ using a GPIO in idle mode Andreas Fenkart
2013-01-10 20:22 ` Tony Lindgren
2013-02-18 10:26 ` Daniel Mack
2013-02-18 12:42 ` Andreas Fenkart
2013-02-08 13:05 ` Grant Likely
2013-01-03 19:48 ` Tony Lindgren [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=20130103194851.GH25633@atomide.com \
--to=tony@atomide.com \
--cc=andreas.fenkart@streamunlimited.com \
--cc=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=zonque@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.