devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	arm@kernel.org, Arnd Bergmann <arnd@arndb.de>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Kevin Hilman <khilman@linaro.org>,
	Olof Johansson <olof@lixom.net>,
	Simon Horman <horms@verge.net.au>,
	Linus Walleij <linus.walleij@linaro.org>,
	Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH v2] ARM: dts: fix gpio-keys wakeup-source property
Date: Wed, 21 Oct 2015 16:23:41 +0100	[thread overview]
Message-ID: <5627ADFD.4050003@arm.com> (raw)
In-Reply-To: <1445011296-29042-1-git-send-email-sudeep.holla@arm.com>

Hi Arnd,

On 16/10/15 17:01, Sudeep Holla wrote:
> The keyboard driver for GPIO buttons(gpio-keys) checks for one of the
> two boolean properties to enable gpio buttons as wakeup source:
> 1. "wakeup-source" or
> 2. the legacy "gpio-key,wakeup"
>
> However juno, ste-snowball and emev2-kzm9d dts file have a undetected
> "wakeup" property to indictate the wakeup source.
>
> This patch fixes it by making use of "wakeup-source" property.
>
> Cc: Magnus Damm <magnus.damm@gmail.com>
> Acked-by: Simon Horman <horms@verge.net.au>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
>   arch/arm/boot/dts/emev2-kzm9d.dts             |  8 ++++----
>   arch/arm/boot/dts/ste-snowball.dts            | 10 +++++-----
>   arch/arm64/boot/dts/arm/juno-motherboard.dtsi | 12 ++++++------
>   3 files changed, 15 insertions(+), 15 deletions(-)
>
> Hi ARM-SoC group,
>
> Please consider this as a fix for v4.3 if possible.
>

Can you include this for v4.3 fixes please ?

-- 
Regards,
Sudeep

  reply	other threads:[~2015-10-21 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 16:01 [PATCH v2] ARM: dts: fix gpio-keys wakeup-source property Sudeep Holla
2015-10-21 15:23 ` Sudeep Holla [this message]
2015-10-22 16:54 ` Olof Johansson

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=5627ADFD.4050003@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=khilman@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=olof@lixom.net \
    /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).