Thread (10 messages) 10 messages, 4 authors, 2013-02-18

Re: omap_hsmmc: SDIO IRQ on AM335x family

From: Daniel Mack <zonque@gmail.com>
Date: 2012-11-30 18:57:35
Also in: linux-mmc, linux-omap

Hi Tony,
Hi Andreas,

On 30.11.2012 18:40, Tony Lindgren wrote:
* Andreas Fenkart [off-list ref] [121130 03:21]:
quoted
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.

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?

If there is another way to solve that cleanly on at least some hardware
derivats, I'd say that should be preferred and be supported by the driver.


Daniel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help