From: afaerber@suse•de (Andreas Färber)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 6/8] arm64: dts: rockchip: Add power key to GeekBox
Date: Wed, 16 Mar 2016 11:58:11 +0100 [thread overview]
Message-ID: <56E93C43.1060500@suse.de> (raw)
In-Reply-To: <6BD669A2-4971-4702-8742-77C9994AA4E9@gmail.com>
Am 11.03.2016 um 00:04 schrieb Julien Chauveau:
>> Le 6 mars 2016 ? 20:53, Andreas F?rber <afaerber@suse•de> a ?crit :
>>
>> Signed-off-by: Andreas F?rber <afaerber@suse•de>
>> ---
>> v2 -> v3:
>> * Adopted wakeup-source instead of gpio-key,wakeup (Julien)
>> * Dropped gpio-keys #address-cells and #size-cells properties (Julien)
>> * Dropped power button reg property (Julien)
>> * Adopted KEY_POWER (Julien)
>> * Fixed power button pinctrl pull setting (Julien)
>>
>> v2: New
>>
>> arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts | 20 ++++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts b/arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts
>> index 098be3700a6f..7036b49c9206 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts
>> @@ -42,6 +42,7 @@
>>
>> /dts-v1/;
>> #include "rk3368.dtsi"
>> +#include <dt-bindings/input/input.h>
>>
>> / {
>> model = "GeekBox";
>> @@ -70,6 +71,19 @@
>> pinctrl-0 = <&ir_int>;
>> };
>>
>> + keys: gpio-keys {
>
> I think you don't need the "keys" label, because there?s no phandle that refers to this.
As discussed elsewhere, there are four additional keys on the
Landingship (you proposed as sub-node names key1-key4).
I prefer preparing the label now over adding it in a later patch.
>> + compatible = "gpio-keys";
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pwr_key>;
>> +
>> + button at 0 {
>
> Here you should use "power" instead of "button at 0".
Done.
>> + gpios = <&gpio0 2 GPIO_ACTIVE_LOW>;
>> + label = "GPIO Power";
>> + linux,code = <KEY_POWER>;
>
> According to Documentation/input/event-codes.txt, there?s a special event type for the power button.
> Should we use it here for that purpose?
>
> linux,input-type = <EV_PWR>
The other RK3368 boards don't, so unless you can give a justification to
convert all boards yet again and test how this makes a difference, I'd
rather not do experiments here but leave that to someone who knows what
they're doing and then do it consistently...
Thanks for the detailed review,
Andreas
>> + wakeup-source;
>> + };
>> + };
>> +
>> leds: gpio-leds {
>> compatible = "gpio-leds";
>>
>> @@ -265,6 +279,12 @@
>> };
>> };
>>
>> + keys {
>> + pwr_key: pwr-key {
>> + rockchip,pins = <0 2 RK_FUNC_GPIO &pcfg_pull_none>;
>> + };
>> + };
>> +
>> pmic {
>> pmic_sleep: pmic-sleep {
>> rockchip,pins = <0 0 RK_FUNC_2 &pcfg_pull_none>;
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2016-03-16 10:58 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457294038-14243-1-git-send-email-afaerber@suse.de>
2016-03-06 19:53 ` [PATCH v3 2/8] Documentation: devicetree: rockchip: Document GeekBox Andreas Färber
2016-03-06 19:53 ` [PATCH v3 3/8] arm64: dts: rockchip: Add GeekBox config Andreas Färber
2016-03-06 19:53 ` [PATCH v3 5/8] arm64: dts: rockchip: Clean up gpio-keys nodes Andreas Färber
2016-03-06 19:53 ` [PATCH v3 6/8] arm64: dts: rockchip: Add power key to GeekBox Andreas Färber
2016-03-10 23:04 ` Julien Chauveau
2016-03-16 10:58 ` Andreas Färber [this message]
2016-03-16 13:52 ` Andreas Färber
2016-03-10 23:09 ` Julien Chauveau
2016-03-06 19:53 ` [PATCH v3 7/8] Documentation: devicetree: rockchip: Document Landingship Andreas Färber
2016-03-17 14:46 ` Rob Herring
2016-03-06 19:53 ` [PATCH v3 8/8] arm64: dts: rockchip: Add Landingship config Andreas Färber
2016-03-07 12:17 ` [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement Andreas Färber
2016-03-07 12:24 ` Heiko Stübner
2016-03-07 12:35 ` Andreas Färber
2016-03-07 13:26 ` Giuseppe CAVALLARO
2016-03-07 14:27 ` Andreas Färber
2016-03-07 15:09 ` Giuseppe CAVALLARO
2016-03-07 15:46 ` Andreas Färber
2016-03-07 15:52 ` Giuseppe CAVALLARO
2016-03-07 17:15 ` Andreas Färber
2016-03-07 23:22 ` Dinh Nguyen
2016-03-08 7:24 ` Giuseppe CAVALLARO
2016-03-08 15:45 ` Dinh Nguyen
2016-03-09 7:24 ` Giuseppe CAVALLARO
2016-03-09 8:35 ` Tomeu Vizoso
2016-03-09 8:56 ` Giuseppe CAVALLARO
2016-03-09 9:00 ` Giuseppe CAVALLARO
2016-03-09 9:42 ` Tomeu Vizoso
2016-03-09 9:52 ` Giuseppe CAVALLARO
2016-03-09 10:27 ` Giuseppe CAVALLARO
2016-03-09 10:53 ` Tomeu Vizoso
2016-03-09 14:31 ` Giuseppe CAVALLARO
2016-03-09 14:53 ` Giuseppe CAVALLARO
2016-03-09 16:31 ` Dinh Nguyen
2016-03-10 9:13 ` Giuseppe CAVALLARO
2016-03-10 16:47 ` Dinh Nguyen
2016-03-11 9:09 ` Giuseppe CAVALLARO
2016-03-14 11:43 ` Tomeu Vizoso
2016-03-14 16:20 ` Giuseppe CAVALLARO
2016-03-15 7:23 ` Tomeu Vizoso
2016-03-15 12:36 ` Giuseppe CAVALLARO
2016-03-30 16:44 ` Dinh Nguyen
2016-03-31 7:53 ` Giuseppe CAVALLARO
2016-03-08 10:03 ` Gabriel Fernandez
2016-03-08 10:24 ` Giuseppe CAVALLARO
2016-03-08 10:33 ` Gabriel Fernandez
2016-03-11 12:12 ` Michael Trimarchi
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=56E93C43.1060500@suse.de \
--to=afaerber@suse$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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