From: liviu.dudau@arm.com (Liviu Dudau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: dts: juno: Fix "debounce-interval" property misspelling
Date: Thu, 10 May 2018 10:44:53 +0100 [thread overview]
Message-ID: <20180510094453.GP1027@e110455-lin.cambridge.arm.com> (raw)
In-Reply-To: <1525884291-18851-1-git-send-email-sudeep.holla@arm.com>
On Wed, May 09, 2018 at 05:44:49PM +0100, Sudeep Holla wrote:
> "debounce_interval" was never supported in the bindings. It should be
> "debounce-interval". Moreover, latest DTC complains the following:
>
> Warning (property_name_chars_strict): debounce_interval: Character '_' not recommended in property name
>
> This patch fixes the above warning by using the correct property as
> per the bindings.
>
> Cc: Liviu Dudau <liviu.dudau@arm.com>
Acked-by: Liviu Dudau <liviu.dudau@arm.com>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> arch/arm64/boot/dts/arm/juno-motherboard.dtsi | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/arm/juno-motherboard.dtsi b/arch/arm64/boot/dts/arm/juno-motherboard.dtsi
> index 69804c5f1197..4b38195a8bea 100644
> --- a/arch/arm64/boot/dts/arm/juno-motherboard.dtsi
> +++ b/arch/arm64/boot/dts/arm/juno-motherboard.dtsi
> @@ -58,42 +58,42 @@
> compatible = "gpio-keys";
>
> power-button {
> - debounce_interval = <50>;
> + debounce-interval = <50>;
> wakeup-source;
> linux,code = <116>;
> label = "POWER";
> gpios = <&iofpga_gpio0 0 0x4>;
> };
> home-button {
> - debounce_interval = <50>;
> + debounce-interval = <50>;
> wakeup-source;
> linux,code = <102>;
> label = "HOME";
> gpios = <&iofpga_gpio0 1 0x4>;
> };
> rlock-button {
> - debounce_interval = <50>;
> + debounce-interval = <50>;
> wakeup-source;
> linux,code = <152>;
> label = "RLOCK";
> gpios = <&iofpga_gpio0 2 0x4>;
> };
> vol-up-button {
> - debounce_interval = <50>;
> + debounce-interval = <50>;
> wakeup-source;
> linux,code = <115>;
> label = "VOL+";
> gpios = <&iofpga_gpio0 3 0x4>;
> };
> vol-down-button {
> - debounce_interval = <50>;
> + debounce-interval = <50>;
> wakeup-source;
> linux,code = <114>;
> label = "VOL-";
> gpios = <&iofpga_gpio0 4 0x4>;
> };
> nmi-button {
> - debounce_interval = <50>;
> + debounce-interval = <50>;
> wakeup-source;
> linux,code = <99>;
> label = "NMI";
> --
> 2.7.4
>
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
?\_(?)_/?
prev parent reply other threads:[~2018-05-10 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 16:44 [PATCH 1/3] arm64: dts: juno: Fix "debounce-interval" property misspelling Sudeep Holla
2018-05-09 16:44 ` [PATCH 2/3] arm64: dts: juno: replace '_' with '-' in node names Sudeep Holla
2018-05-09 21:15 ` Rob Herring
2018-05-10 9:45 ` Liviu Dudau
2018-05-09 16:44 ` [PATCH 3/3] arm64: dts: juno/rtsm: re-structure motherboard includes Sudeep Holla
2018-05-10 9:49 ` Liviu Dudau
2018-05-10 10:07 ` Sudeep Holla
2018-05-23 7:59 ` Linus Walleij
2018-05-10 9:44 ` Liviu Dudau [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=20180510094453.GP1027@e110455-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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).