From: Tony Lindgren <tony@atomide.com>
To: Dmitry Lifshitz <lifshitz@compulab.co.il>
Cc: Balaji T K <balajitk@ti.com>,
Andreas Fenkart <afenkart@gmail.com>,
Chris Ball <chris@printf.net>,
Grant Likely <grant.likely@secretlab.ca>,
Felipe Balbi <balbi@ti.com>,
zonque@gmail.com, galak@codeaurora.org,
linux-doc@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v9 resend 1/3] mmc: omap_hsmmc: Enable SDIO interrupt
Date: Fri, 18 Apr 2014 09:46:30 -0700 [thread overview]
Message-ID: <20140418164630.GE5354@atomide.com> (raw)
In-Reply-To: <532FFB43.5020408@compulab.co.il>
Hi,
Sorry for the delay, just noticed this one.
* Dmitry Lifshitz <lifshitz@compulab.co.il> [140324 02:34]:
> Hi,
>
> I've tested the branch omap_hsmmc_sdio_irq_devm_cleanup on custom OMAP5
> based board.
> We have mwifiex connected to MMC3.
>
> I used two approaches:
>
> * Using dat1 line as GPIO with dynamic remuxing
> * Using separate GPIO connected to dat1 with static mux settings
>
> Both works just fine. Thanks Andreas for a great solution.
>
> I have just one issue - how to define GPIO IRQ using DT in OMAP5 case.
> As a temporary hack for testing I used a fixed GPIO number and gpio_to_irq()
> call in omap_hsmmc_configure_wake_irq().
>
> OMAP5 MMC3 has the following DT entry (omap5.dtsi):
>
> mmc3: mmc@480ad000 {
> compatible = "ti,omap4-hsmmc";
> reg = <0x480ad000 0x400>;
> interrupts = <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>;
> ti,hwmods = "mmc3";
> ti,needs-special-reset;
> dmas = <&sdma 77>, <&sdma 78>;
> dma-names = "tx", "rx";
> };
>
> What should be by board MMC3 setup?
You need to use the interrupts-extended property in omap5.dtsi
for the MMC interrupt. And if using the wake-up interrupts
for your board, you need to sepcify interrupts-extended in your
board file again to add the second wake-up interrupt.
If using the async wake-up path, the wake-up interrupt is the
OMAP5_CORE_IOPAD() or OMAP5_WKUP_IOPAD() pinctrl register offset
for that pin. If remuxing to GPIO for the wake-up, the wake-up
interrupt is the standard gpio interrupt property.
Then you also need this patch to avoid warnings during boot:
http://lkml.org/lkml/2014/4/10/620
After the above gets merged, we can apply the serial wake-up
patch too:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-November/213873.html
That shows you some examples on how to specify the wake-up
interrupt.
Regards,
Tony
next prev parent reply other threads:[~2014-04-18 16:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 12:20 [PATCH v9 resend 0/3] mmc: omap_hsmmc: Enable SDIO IRQ Andreas Fenkart
2014-03-21 12:20 ` [PATCH v9 resend 1/3] mmc: omap_hsmmc: Enable SDIO interrupt Andreas Fenkart
2014-03-21 16:10 ` Balaji T K
2014-03-24 9:30 ` Dmitry Lifshitz
2014-04-18 16:46 ` Tony Lindgren [this message]
2014-03-21 16:17 ` [PATCH 0/9] mmc: omap_hsmmc: convert to use devm_* and enable sdio irq Balaji T K
2014-03-21 16:17 ` [PATCH 1/9] mmc: omap_hsmmc: use devm_clk_get Balaji T K
2014-03-21 16:17 ` [PATCH 2/9] mmc: omap_hsmmc: use devm_request_irq Balaji T K
2014-03-21 16:17 ` [PATCH 3/9] mmc: omap_hsmmc: use devm_request_threaded_irq Balaji T K
2014-03-21 16:17 ` [PATCH 4/9] mmc: omap_hsmmc: use devm_request_mem_region Balaji T K
2014-03-21 16:18 ` Felipe Balbi
2014-03-21 16:27 ` Balaji T K
2014-03-21 16:30 ` Felipe Balbi
2014-03-21 16:17 ` [PATCH 5/9] mmc: omap_hsmmc: use devm_ioremap Balaji T K
2014-03-21 16:17 ` [PATCH 6/9] mmc: omap_hsmmc: Enable SDIO interrupt Balaji T K
2014-03-24 12:43 ` Ulf Hansson
2014-03-24 14:59 ` Andreas Fenkart
2014-03-24 16:02 ` Ulf Hansson
2014-03-24 16:34 ` Andreas Fenkart
2014-03-25 8:07 ` Ulf Hansson
2014-03-25 15:19 ` Balaji T K
2014-03-30 22:43 ` Andreas Fenkart
2014-03-21 16:17 ` [PATCH 7/9] mmc: omap_hsmmc: Pin remux workaround to support SDIO interrupt on AM335x Balaji T K
2014-03-21 16:17 ` [PATCH 8/9] mmc: omap_hsmmc: Extend debugfs for SDIO IRQ, GPIO and pinmux Balaji T K
2014-03-21 16:17 ` [PATCH 9/9] mmc: omap_hsmmc: enable wakeup event for sdio Balaji T K
2014-05-02 15:33 ` Balaji T K
2014-03-21 12:20 ` [PATCH v9 resend 2/3] mmc: omap_hsmmc: Pin remux workaround to support SDIO interrupt on AM335x Andreas Fenkart
2014-03-21 12:20 ` [PATCH v9 resend 3/3] mmc: omap_hsmmc: Extend debugfs for SDIO IRQ, GPIO and pinmux 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=20140418164630.GE5354@atomide.com \
--to=tony@atomide.com \
--cc=afenkart@gmail.com \
--cc=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=chris@printf.net \
--cc=galak@codeaurora.org \
--cc=grant.likely@secretlab.ca \
--cc=lifshitz@compulab.co.il \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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.