From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: iMX53 and MMC_CAP_SDIO_IRQ
Date: Mon, 12 Mar 2012 12:06:24 +0100 [thread overview]
Message-ID: <20120312110624.GB2459@pengutronix.de> (raw)
In-Reply-To: <4F5DD28F.50600@linuxtv.org>
> Ok, to sum this up:
>
> SDIO IRQs are working in mx_sdhci in the Freescale tree because it was
> properly implemented and tested, obviously.
Not sure about "properly", but, yes ;)
> SDIO IRQs are working for sdhci in mainline probably for other
> non-freescale platforms.
Probably, but I can't say 'yes' for sure. You'd need to find out.
> You fixed the generic sdhci driver in mainline to work with iMX53 to get
> rid of the need for mx_sdhci, but probably never got the chance to test
> if SDIO IRQs are really working.
I worked mainly with MX25/35 back then, and a little bit with MX51. IIRC
I only had an SDIO card for which no Linux drivers were available, so I
only could test that the card was detected :(
> That means, the subtle difference between mx_sdhci and sdhci to get SDIO
> IRQS to work on sdhci with iMX53 has yet to be found.
Yup. Try 'git log --follow sdhci-esdhc-imx.c' to find people who worked
with MX53 or SDIO using that driver.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120312/fa9e24dc/attachment-0001.sig>
prev parent reply other threads:[~2012-03-12 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 8:45 iMX53 and MMC_CAP_SDIO_IRQ Michael Hunold
2012-03-12 10:10 ` Wolfram Sang
2012-03-12 10:40 ` Michael Hunold
2012-03-12 11:06 ` Wolfram Sang [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=20120312110624.GB2459@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).