From: Heiko Stuebner <heiko@sntech.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH 1/2] ARM: dts: rockchip: Split GPIO keys for veyron into multiple devices
Date: Thu, 06 Jun 2019 12:44:34 +0200 [thread overview]
Message-ID: <3394571.LkITImzWxP@phil> (raw)
In-Reply-To: <20190605204320.22343-1-mka@chromium.org>
Am Mittwoch, 5. Juni 2019, 22:43:19 CEST schrieb Matthias Kaehlcke:
> With a single device DT overrides can become messy, especially when
> keys are added or removed. Multiple devices also allow to
> enable/disable wakeup per key/group.
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
applied for 5.3 with 2 minor changes, detailed below.
> ---
> .../boot/dts/rk3288-veyron-chromebook.dtsi | 26 +++++++------
> arch/arm/boot/dts/rk3288-veyron-minnie.dts | 38 ++++++++++---------
> arch/arm/boot/dts/rk3288-veyron-pinky.dts | 2 +-
> arch/arm/boot/dts/rk3288-veyron.dtsi | 4 +-
> 4 files changed, 37 insertions(+), 33 deletions(-)
>
> diff --git a/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi b/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi
> index fbef34578100..c5f71af84a40 100644
> --- a/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi
> +++ b/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi
> @@ -70,6 +70,20 @@
> pinctrl-0 = <&ac_present_ap>;
> };
>
> + lid_switch: lid-switch {
> + compatible = "gpio-keys";
> + pinctrl-names = "default";
> + pinctrl-0 = <&ap_lid_int_l>;
added a blank line here
> + lid {
> + label = "Lid";
> + gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
> + wakeup-source;
> + linux,code = <0>; /* SW_LID */
> + linux,input-type = <5>; /* EV_SW */
actually used the constants in the properties, we have the keycodes as
dt-binding header nowadays.
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: rockchip: Split GPIO keys for veyron into multiple devices
Date: Thu, 06 Jun 2019 12:44:34 +0200 [thread overview]
Message-ID: <3394571.LkITImzWxP@phil> (raw)
In-Reply-To: <20190605204320.22343-1-mka@chromium.org>
Am Mittwoch, 5. Juni 2019, 22:43:19 CEST schrieb Matthias Kaehlcke:
> With a single device DT overrides can become messy, especially when
> keys are added or removed. Multiple devices also allow to
> enable/disable wakeup per key/group.
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
applied for 5.3 with 2 minor changes, detailed below.
> ---
> .../boot/dts/rk3288-veyron-chromebook.dtsi | 26 +++++++------
> arch/arm/boot/dts/rk3288-veyron-minnie.dts | 38 ++++++++++---------
> arch/arm/boot/dts/rk3288-veyron-pinky.dts | 2 +-
> arch/arm/boot/dts/rk3288-veyron.dtsi | 4 +-
> 4 files changed, 37 insertions(+), 33 deletions(-)
>
> diff --git a/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi b/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi
> index fbef34578100..c5f71af84a40 100644
> --- a/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi
> +++ b/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi
> @@ -70,6 +70,20 @@
> pinctrl-0 = <&ac_present_ap>;
> };
>
> + lid_switch: lid-switch {
> + compatible = "gpio-keys";
> + pinctrl-names = "default";
> + pinctrl-0 = <&ap_lid_int_l>;
added a blank line here
> + lid {
> + label = "Lid";
> + gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
> + wakeup-source;
> + linux,code = <0>; /* SW_LID */
> + linux,input-type = <5>; /* EV_SW */
actually used the constants in the properties, we have the keycodes as
dt-binding header nowadays.
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-06 10:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 20:43 [PATCH 1/2] ARM: dts: rockchip: Split GPIO keys for veyron into multiple devices Matthias Kaehlcke
2019-06-05 20:43 ` Matthias Kaehlcke
2019-06-05 20:43 ` [PATCH 2/2] ARM: dts: rockchip: Configure BT_HOST_WAKE as wake-up signal on veyron Matthias Kaehlcke
2019-06-05 20:43 ` Matthias Kaehlcke
2019-06-05 21:11 ` Heiko Stübner
2019-06-05 21:11 ` Heiko Stübner
2019-06-05 21:24 ` Matthias Kaehlcke
2019-06-05 21:24 ` Matthias Kaehlcke
2019-06-05 21:52 ` Heiko Stübner
2019-06-05 21:52 ` Heiko Stübner
2019-06-06 10:46 ` Heiko Stuebner
2019-06-06 10:46 ` Heiko Stuebner
2019-06-06 17:56 ` Matthias Kaehlcke
2019-06-06 17:56 ` Matthias Kaehlcke
2019-06-06 23:34 ` Doug Anderson
2019-06-06 23:34 ` Doug Anderson
2019-06-14 9:41 ` Heiko Stuebner
2019-06-14 9:41 ` Heiko Stuebner
2019-06-06 23:32 ` Doug Anderson
2019-06-06 23:32 ` Doug Anderson
2019-06-06 10:44 ` Heiko Stuebner [this message]
2019-06-06 10:44 ` [PATCH 1/2] ARM: dts: rockchip: Split GPIO keys for veyron into multiple devices Heiko Stuebner
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=3394571.LkITImzWxP@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.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.