public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: linux-bluetooth@vger.kernel.org,
	Nishant Sarmukadam <nishants@marvell.com>,
	wnhuang@chromium.com, devicetree@vger.kernel.org,
	Cathy Luo <cluo@marvell.com>,
	linux-kernel@vger.kernel.org, Xinming Hu <huxm@marvell.com>
Subject: Re: [PATCH v4 3/3] mwifiex: parse host wakeup configuration from device
Date: Thu, 18 Feb 2016 08:37:54 -0600	[thread overview]
Message-ID: <20160218143754.GV9654@rob-hp-laptop> (raw)
In-Reply-To: <1455614079-4263-3-git-send-email-akarwar@marvell.com>

On Tue, Feb 16, 2016 at 01:14:39AM -0800, Amitkumar Karwar wrote:
> From: Xinming Hu <huxm@marvell.com>
> 
> This patch implement a framework for board specific wakeup.
> driver parse irq/gpio number from device tree, corresponding
> resources will be allocated, and used for host suspend/resume.
> driver private binding file is also updated in the patch.
> 
> Signed-off-by: Xinming Hu <huxm@marvell.com>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> ---
> v4: Replaced #ifdef with __maybe_unused(Arnd Bergmann)
> ---
>  .../bindings/net/wireless/marvell-sd8xxx.txt       | 10 +++
>  .../net/wireless/marvell/mwifiex/platform_drv.c    | 91 ++++++++++++++++++++++
>  2 files changed, 101 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/net/wireless/marvell-sd8xxx.txt b/Documentation/devicetree/bindings/net/wireless/marvell-sd8xxx.txt
> index c337fab..50138fd 100644
> --- a/Documentation/devicetree/bindings/net/wireless/marvell-sd8xxx.txt
> +++ b/Documentation/devicetree/bindings/net/wireless/marvell-sd8xxx.txt
> @@ -14,6 +14,11 @@ Optional properties:
>    - marvell,wakeup-gpios : Chip's wakeup gpio pin number. This needs to be downloaded
>  			to to firmware. Chip notifies wifi wakeup signal to SOC
>  			through this pin.
> +  - interrupt-parent: phandle of the parent interrupt controller
> +  - interrupts : interrupt number to the cpu
> +  - gpios: specify SOC's wakeup GPIO

If you define the GPIO line as an interrupt, you shouldn't need it to be 
as GPIO too. Same on the BT side.

> +  - pinctrl-names : a pinctrl state named "default" must be defined
> +  - pinctrl-0 : pin control group to be used for this controller
>  
>  Example:
>  
> @@ -27,5 +32,10 @@ wlan {
>  	marvell,caldata_00_txpwrlimit_2g_cfg_set = /bits/ 8 <
>  0x01 0x00 0x06 0x00 0x08 0x02 0x89 0x01 ...>;
>  	marvell,wakeup-gpios = <3>;
> +	interrupt-parent = <&pio>;
> +	interrupts = <38 IRQ_TYPE_LEVEL_LOW>;
> +	gpios = <&pio 38 GPIO_ACTIVE_HIGH>;
> +	pinctrl-names = "default";
> +	pinctrl-0 = <&wake_pins>;
>  };
>  

  reply	other threads:[~2016-02-18 14:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16  9:14 [PATCH v4 1/3] mwifiex: register platform specific driver Amitkumar Karwar
2016-02-16  9:14 ` [PATCH v4 2/3] mwifiex: parse chip specific gpio from device tree Amitkumar Karwar
2016-02-18 14:37   ` Rob Herring
2016-02-16  9:14 ` [PATCH v4 3/3] mwifiex: parse host wakeup configuration from device Amitkumar Karwar
2016-02-18 14:37   ` Rob Herring [this message]
     [not found] ` <1455614079-4263-1-git-send-email-akarwar-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
2016-02-16 11:28   ` [PATCH v4 1/3] mwifiex: register platform specific driver Arnd Bergmann
2016-02-18 14:38 ` Rob Herring
2016-02-29 14:04   ` Amitkumar Karwar

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=20160218143754.GV9654@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=devicetree@vger.kernel.org \
    --cc=huxm@marvell.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nishants@marvell.com \
    --cc=wnhuang@chromium.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