From: Andreas Fenkart <afenkart@gmail.com>
To: Chris Ball <cjb@laptop.org>
Cc: Tony Lindgren <tony@atomide.com>,
Grant Likely <grant.likely@secretlab.ca>,
Felipe Balbi <balbi@ti.com>, Balaji T K <balajitk@ti.com>,
zonque@gmail.com, linux-doc@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org,
Andreas Fenkart <afenkart@gmail.com>
Subject: [PATCH v3 0/3] mmc: omap_hsmmc: Enable SDIO IRQ.
Date: Mon, 25 Nov 2013 14:26:46 +0100 [thread overview]
Message-ID: <1385386009-14981-1-git-send-email-afenkart@gmail.com> (raw)
v3:
- removed gpio_irq from platform_data
v2:
- incorparated changes as suggested by reviewers
- simplified workaround for am335x, gpio will now only wake
the module from runtime suspend, not handle the sdio irq
itself
Andreas Fenkart (3):
mmc: omap_hsmmc: Enable SDIO IRQ.
mmc: omap_hsmmc: Pin remux workaround to support SDIO interrupt on
AM335x.
mmc: omap_hsmmc: Extend debugfs for SDIO IRQ, GPIO and pinmux.
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 42 +++
drivers/mmc/host/omap_hsmmc.c | 303 ++++++++++++++++++--
include/linux/platform_data/mmc-omap.h | 1 +
3 files changed, 324 insertions(+), 22 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-11-25 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 13:26 Andreas Fenkart [this message]
2013-11-25 13:26 ` [PATCH v3 1/3] mmc: omap_hsmmc: Enable SDIO IRQ Andreas Fenkart
2013-11-25 13:26 ` [PATCH v3 2/3] mmc: omap_hsmmc: Pin remux workaround to support SDIO interrupt on AM335x Andreas Fenkart
2013-11-25 22:46 ` Tony Lindgren
2013-11-26 1:16 ` Felipe Balbi
2013-11-26 18:06 ` Tony Lindgren
2013-11-27 16:59 ` Balaji T K
2013-11-27 17:04 ` Tony Lindgren
2013-11-25 13:26 ` [PATCH v3 3/3] mmc: omap_hsmmc: Extend debugfs for SDIO IRQ, GPIO and pinmux Andreas Fenkart
-- strict thread matches above, loose matches on Subject: below --
2013-11-18 7:53 [PATCH v3 0/3] mmc: omap_hsmmc: Enable SDIO IRQ Andreas Fenkart
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=1385386009-14981-1-git-send-email-afenkart@gmail.com \
--to=afenkart@gmail.com \
--cc=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=cjb@laptop.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 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).