From: Michal Simek <michal.simek@xilinx.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH] ARM: dts: zynqmp: replace gpio-key,wakeup with wakeup-source property
Date: Thu, 3 Jan 2019 11:50:13 +0100 [thread overview]
Message-ID: <63f7ded1-8f1c-6aa7-9397-75c1c2d194b8@xilinx.com> (raw)
In-Reply-To: <20181221181213.6812-1-sudeep.holla@arm.com>
On 21. 12. 18 19:12, Sudeep Holla wrote:
> Most of the legacy "gpio-key,wakeup" boolean property is already
> replaced with "wakeup-source". However few occurrences of old property
> has popped up again, probably from the remnants in downstream trees.
>
> Replace the legacy properties with the unified "wakeup-source"
> property introduced in the commit 700a38b27eef ("Input: gpio_keys -
> switch to using generic device properties")
>
> Cc: Michal Simek <michal.simek@xilinx.com>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> arch/arm/boot/dts/zynq-zturn.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Hi Michal,
>
> Olof requested to slipt the patch and send it via platform maintainers.
> I totally forgot to follow up on this. You had acked this previously but
> please pick this up and submit via your tree to ARM SoC. Sorry for the
> confusion.
>
> Regards,
> Sudeep
>
> diff --git a/arch/arm/boot/dts/zynq-zturn.dts b/arch/arm/boot/dts/zynq-zturn.dts
> index b38704657960..5ec616ebca08 100644
> --- a/arch/arm/boot/dts/zynq-zturn.dts
> +++ b/arch/arm/boot/dts/zynq-zturn.dts
> @@ -54,7 +54,7 @@
> label = "K1";
> gpios = <&gpio0 0x32 0x1>;
> linux,code = <0x66>;
> - gpio-key,wakeup;
> + wakeup-source;
> autorepeat;
> };
> };
> --
> 2.17.1
>
Applied.
Thanks,
Michal
prev parent reply other threads:[~2019-01-03 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 18:12 [PATCH] ARM: dts: zynqmp: replace gpio-key, wakeup with wakeup-source property Sudeep Holla
2019-01-03 10:50 ` Michal Simek [this message]
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=63f7ded1-8f1c-6aa7-9397-75c1c2d194b8@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).