From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Vishal Thanki <vishalthanki@gmail.com>
Cc: Andreas Fenkart <afenkart@gmail.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-omap@vger.kernel.org
Subject: Re: omap_hsmmc: sdio: issue with generic wakeup IRQ handling
Date: Thu, 25 Feb 2016 13:47:13 +0200 [thread overview]
Message-ID: <56CEE9C1.2050207@ti.com> (raw)
In-Reply-To: <20160225111813.GA19506@c50.bag.software>
On 02/25/2016 01:18 PM, Vishal Thanki wrote:
[...]
>>
>> Suspend or Runtime suspend?
>
> The it is the runtime suspend routine for omap_hsmmc.c
>
> mmc1_pins: pinmux_mmc1_pins {
> pinctrl-single,pins = <
> 0x0fc 0x38 /* MMC0_DAT0 */
> 0x0f8 0x38 /* MMC0_DAT1 */
> 0x0f4 0x38 /* MMC0_DAT2 */
> 0x0f0 0x38 /* MMC0_DAT3 */
> 0x100 0x38 /* MMC0_CLK */
> 0x104 0x38 /* MMC0_CMD */
> 0x88 0x07 /* GPMC_CSN3 -> GPIO2_0 */
> >;
> };
>
> mmc1_sleep_pins: pinmux_mmc1_sleep_pins {
> pinctrl-single,pins = <
> 0x0fc 0x3f /* MMC0_DAT0 */
> 0x0f8 0x3f /* MMC0_DAT1 */
> 0x0f4 0x3f /* MMC0_DAT2 */
> 0x0f0 0x3f /* MMC0_DAT3 */
> 0x100 0x3f /* MMC0_CLK */
> 0x104 0x3f /* MMC0_CMD */
> 0x88 0x17 /* GPMC_CSN3 -> GPIO2_0 PULL UP */
> >;
> };
>
> mmc1_cirq_pin: pinmux_cirq_pin {
> pinctrl-single,pins = <
> 0x0f8 0x3f /* MMC0_DAT1 as GPIO2_28 */
> >;
> };
>
> wlan0_pwrseq: pwrseq {
> compatible = "mmc-pwrseq-simple";
> reset-gpios = <&gpio2 0 GPIO_ACTIVE_LOW>;
> clocks = <&clk_32768_ck>;
> clock-names = "ext_clock";
> };
>
> &mmc1 {
> status = "okay";
> pinctrl-names = "default", "idle", "sleep";
> pinctrl-0 = <&mmc1_pins>;
> pinctrl-1 = <&mmc1_cirq_pin>;
> pinctrl-2 = <&mmc1_sleep_pins>;
> interrupts-extended = <&intc 64 &gpio2 28 0>;
^^ you can define IRQ type here
&gpio2 28 IRQ_TYPE_LEVEL_LOW
> ti,non-removable;
> bus-width = <4>;
> vmmc-supply = <&ldo2_reg>;
> vmmc_aux-supply = <&vmmc>;
> keep-power-in-suspend;
> enable-sdio-wakeup;
> mmc-pwrseq = <&wlan0_pwrseq>;
> };
>
>
>>
>>>>
>>>
>>> Is there any other suggestion for mwifiex that I should try out? Or
>>> is there any way in omap_hsmmc to specify the wakeup interrupt
>>> type (IRQF_TRIGGER_LOW) while using generic wakeup IRQ
>>> mechanism. I could not find it, but I may be missing something.
>>
>> How your irqs defined in DT? Could you provide mmc+wifi nodes?
>
>
>
>>
>>
[..]
--
regards,
-grygorii
next prev parent reply other threads:[~2016-02-25 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 18:27 omap_hsmmc: sdio: issue with generic wakeup IRQ handling Vishal Thanki
2016-02-18 21:31 ` Andreas Fenkart
2016-02-19 14:11 ` Vishal Thanki
2016-02-24 21:32 ` Vishal Thanki
2016-02-25 10:46 ` Grygorii Strashko
2016-02-25 11:18 ` Vishal Thanki
2016-02-25 11:47 ` Grygorii Strashko [this message]
2016-02-25 12:18 ` Vishal Thanki
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=56CEE9C1.2050207@ti.com \
--to=grygorii.strashko@ti.com \
--cc=afenkart@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vishalthanki@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