From: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: kernel@collabora.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
Subject: [PATCH 0/3] Mediatek Genio EVKs: add MT6359 PMIC keys support
Date: Thu, 03 Jul 2025 17:41:02 +0200 [thread overview]
Message-ID: <20250703-add-mt6359-pmic-keys-support-v1-0-21a4d2774e34@collabora.com> (raw)
This patchset adds the support of the MT6359 PMIC keys (Power and Home)
that can be found on the Mediatek Genio 510, 700 and 1200 EVK boards
by:
- adding the MT6359 SoC support in the mtk-pmic-keys driver
- completing the existing definitions (only the Power key
support was present) in Genio 510/700 EVK board common
devicetree include file (mt8390-genio-common.dtsi)
- add the needed definitions in Genio 1200 EVK board devicetree
(mt8395-genio-1200-evk.dts)
I've tested this patchset on Mediatek Genio 1200-EVK board with a
kernel based on linux-next (tag: next-20250703) plus [1] patch.
Output of evtest tool:
```
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: mtk-pmic-keys
/dev/input/event1: gpio-keys
/dev/input/event2: Logitech USB Receiver
/dev/input/event3: Logitech USB Receiver Mouse
/dev/input/event4: Logitech USB Receiver Consumer Control
/dev/input/event5: Logitech USB Receiver System Control
/dev/input/event6: Goodix Capacitive TouchScreen
Select the device event number [0-6]: 0
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x1
Input device name: "mtk-pmic-keys"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 102 (KEY_HOME)
Event code 116 (KEY_POWER)
Properties:
Testing ... (interrupt to exit)
Event: time 1751548607.957644, type 1 (EV_KEY), code 102 (KEY_HOME),
value 1
Event: time 1751548607.957644, -------------- SYN_REPORT ------------
Event: time 1751548620.030611, type 1 (EV_KEY), code 116 (KEY_POWER),
value 1
Event: time 1751548620.030611, -------------- SYN_REPORT ---
```
[1] https://lore.kernel.org/linux-mediatek/r4k3pgd3ew3ypne7ernxuzwgniiyvzosbce4cfajbcu7equblt@yato35tjb3lw/
Signed-off-by: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
---
Louis-Alexis Eyraud (3):
Input: mtk-pmic-keys - add support for MT6359 PMIC keys
arm64: dts: mediatek: mt8390-genio-common: Add Home MT6359 PMIC key support
arm64: dts: mediatek: mt8395-genio-1200-evk: Add MT6359 PMIC key support
arch/arm64/boot/dts/mediatek/mt8390-genio-common.dtsi | 4 ++++
arch/arm64/boot/dts/mediatek/mt8395-genio-1200-evk.dts | 15 +++++++++++++++
drivers/input/keyboard/mtk-pmic-keys.c | 17 +++++++++++++++++
3 files changed, 36 insertions(+)
---
base-commit: b803ad80123e6efccfeeffa7cd37f98f642e37f4
change-id: 20250703-add-mt6359-pmic-keys-support-d08019d8d3c1
Best regards,
--
Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
next reply other threads:[~2025-07-03 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 15:41 Louis-Alexis Eyraud [this message]
2025-07-03 15:41 ` [PATCH 1/3] Input: mtk-pmic-keys - add support for MT6359 PMIC keys Louis-Alexis Eyraud
2025-07-04 5:33 ` Dmitry Torokhov
2025-07-03 15:41 ` [PATCH 2/3] arm64: dts: mediatek: mt8390-genio-common: Add Home MT6359 PMIC key support Louis-Alexis Eyraud
2025-07-03 15:41 ` [PATCH 3/3] arm64: dts: mediatek: mt8395-genio-1200-evk: Add " Louis-Alexis Eyraud
2025-07-07 9:38 ` (subset) [PATCH 0/3] Mediatek Genio EVKs: add MT6359 PMIC keys support AngeloGioacchino Del Regno
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=20250703-add-mt6359-pmic-keys-support-v1-0-21a4d2774e34@collabora.com \
--to=louisalexis.eyraud@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@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 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).