[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v8xps705.fsf@baylibre.com>
Date: Tue, 08 Feb 2022 16:38:50 +0100
From: Mattijs Korpershoek <mkorpershoek@...libre.com>
To: Matthias Brugger <matthias.bgg@...il.com>
Cc: Fabien Parent <fparent@...libre.com>,
Kevin Hilman <khilman@...libre.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Rob Herring <robh+dt@...nel.org>, linux-input@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 4/4] arm64: dts: mt6358: add mt6358-keys node
Hi Matthias,
On ven., janv. 21, 2022 at 15:03, Mattijs Korpershoek <mkorpershoek@...libre.com> wrote:
> This enables the power,home keys on MediaTek boards with a mt6358 pmic.
>
> Signed-off-by: Mattijs Korpershoek <mkorpershoek@...libre.com>
Since the driver change has been merged [1], can we queue up the DT change?
Or should I resubmit this separately?
Thanks
[1] https://lore.kernel.org/all/YgIE%2F806gDmRJYCn@google.com/
> ---
> arch/arm64/boot/dts/mediatek/mt6358.dtsi | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt6358.dtsi b/arch/arm64/boot/dts/mediatek/mt6358.dtsi
> index 95145076b7e6..98f3b0e0c9f6 100644
> --- a/arch/arm64/boot/dts/mediatek/mt6358.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt6358.dtsi
> @@ -2,6 +2,7 @@
> /*
> * Copyright (c) 2020 MediaTek Inc.
> */
> +#include <dt-bindings/input/input.h>
>
> &pwrap {
> pmic: mt6358 {
> @@ -357,5 +358,16 @@ mt6358_vsim2_reg: ldo_vsim2 {
> mt6358rtc: mt6358rtc {
> compatible = "mediatek,mt6358-rtc";
> };
> +
> + mt6358keys: mt6358keys {
> + compatible = "mediatek,mt6358-keys";
> + power {
> + linux,keycodes = <KEY_POWER>;
> + wakeup-source;
> + };
> + home {
> + linux,keycodes = <KEY_HOME>;
> + };
> + };
> };
> };
> --
> 2.32.0
Powered by blists - more mailing lists