All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: Eyal Reizer <eyalr-l0cyMroinI0@public.gmane.org>,
	Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org>,
	Guy Mishol <guym-l0cyMroinI0@public.gmane.org>,
	Luca Coelho
	<luciano.coelho-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Maital Hahn <maitalm-l0cyMroinI0@public.gmane.org>,
	Maxim Altshul <maxim.altshul-l0cyMroinI0@public.gmane.org>,
	Shahar Patury <shaharp-l0cyMroinI0@public.gmane.org>,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] wlcore: Add support for optional wakeirq
Date: Fri,  5 Oct 2018 08:33:58 +0000 (UTC)	[thread overview]
Message-ID: <20181005083358.C9DA6601A0@smtp.codeaurora.org> (raw)
In-Reply-To: <20181001214110.86774-1-tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>

Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> wrote:

> Now with wlcore using PM runtime, we can also add support for Linux
> generic wakeirq handling for it if configured in the dts file.
> 
> The wakeirq can be configured as the second interrupt in the dts file
> with interrupts-extended property where it is the padconf irq of the OOB
> GPIO pin used for wlcore interrupt.
> 
> Note that eventually we should also allow configuring wlcore to use the
> SDIO dat1 IRQ for wake-up, and in that case the the wakeirq should be
> configured to be the padconf interrupt of the dat1 pin and not the
> padconf interrupt of the OOB GPIO pin.
> 
> Cc: Eyal Reizer <eyalr-l0cyMroinI0@public.gmane.org>
> Signed-off-by: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>

Patch applied to wireless-drivers-next.git, thanks.

3c83dd577c7f wlcore: Add support for optional wakeirq

-- 
https://patchwork.kernel.org/patch/10622795/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Eyal Reizer <eyalr@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>, Guy Mishol <guym@ti.com>,
	Luca Coelho <luciano.coelho@intel.com>,
	Maital Hahn <maitalm@ti.com>,
	Maxim Altshul <maxim.altshul@ti.com>,
	Shahar Patury <shaharp@ti.com>,
	linux-wireless@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] wlcore: Add support for optional wakeirq
Date: Fri,  5 Oct 2018 08:33:58 +0000 (UTC)	[thread overview]
Message-ID: <20181005083358.C9DA6601A0@smtp.codeaurora.org> (raw)
In-Reply-To: <20181001214110.86774-1-tony@atomide.com>

Tony Lindgren <tony@atomide.com> wrote:

> Now with wlcore using PM runtime, we can also add support for Linux
> generic wakeirq handling for it if configured in the dts file.
> 
> The wakeirq can be configured as the second interrupt in the dts file
> with interrupts-extended property where it is the padconf irq of the OOB
> GPIO pin used for wlcore interrupt.
> 
> Note that eventually we should also allow configuring wlcore to use the
> SDIO dat1 IRQ for wake-up, and in that case the the wakeirq should be
> configured to be the padconf interrupt of the dat1 pin and not the
> padconf interrupt of the OOB GPIO pin.
> 
> Cc: Eyal Reizer <eyalr@ti.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>

Patch applied to wireless-drivers-next.git, thanks.

3c83dd577c7f wlcore: Add support for optional wakeirq

-- 
https://patchwork.kernel.org/patch/10622795/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  parent reply	other threads:[~2018-10-05  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 21:41 [PATCH] wlcore: Add support for optional wakeirq Tony Lindgren
2018-10-01 21:41 ` Tony Lindgren
     [not found] ` <20181001214110.86774-1-tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2018-10-05  8:33   ` Kalle Valo [this message]
2018-10-05  8:33     ` Kalle Valo

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=20181005083358.C9DA6601A0@smtp.codeaurora.org \
    --to=kvalo-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
    --cc=eyalr-l0cyMroinI0@public.gmane.org \
    --cc=guym-l0cyMroinI0@public.gmane.org \
    --cc=kishon-l0cyMroinI0@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=luciano.coelho-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=maitalm-l0cyMroinI0@public.gmane.org \
    --cc=maxim.altshul-l0cyMroinI0@public.gmane.org \
    --cc=shaharp-l0cyMroinI0@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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 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.