From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Fabien Parent <fparent@baylibre.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Mattijs Korpershoek <mkorpershoek@baylibre.com>
Subject: [PATCH v3 0/4] input: MT6358 PMIC button support
Date: Fri, 2 Jul 2021 15:43:06 +0200 [thread overview]
Message-ID: <20210702134310.3451560-1-mkorpershoek@baylibre.com> (raw)
The MediaTek MT6358 PMIC has support for two buttons: PWR and HOME.
The interrupt logic is a little different than other PMICs from the
same family:
for MT6323 and MT6397, we have one interrupt source per button
* for MT6358, we have two interrupts lines per button: the press and
* release interrupts are distinct sources.
Changes since original v2 at [1]:
* added 4th patch with device tree enable
* cover letter title prefixed with 'input'
This series depends on [2]
[1] https://lore.kernel.org/r/20210512152648.39961-1-mkorpershoek@baylibre.com
[2] https://lore.kernel.org/r/20210506094116.638527-1-mkorpershoek@baylibre.com
This has been tested with evtest on mt8183-pumpkin
using for-mfd-next as base tree.
Mattijs Korpershoek (4):
Input: mtk-pmic-keys - use get_irq_byname() instead of index
dt-bindings: input: mtk-pmic-keys: add MT6358 binding definition
Input: mtk-pmic-keys - add support for MT6358
arm64: dts: mt6358: add mt6358-keys node
.../bindings/input/mtk-pmic-keys.txt | 5 +-
arch/arm64/boot/dts/mediatek/mt6358.dtsi | 12 ++++
drivers/input/keyboard/mtk-pmic-keys.c | 56 +++++++++++++++++--
3 files changed, 68 insertions(+), 5 deletions(-)
base-commit: 495fb48dbd9bcbe15859e086edd24519a6bd2961
--
2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Fabien Parent <fparent@baylibre.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Mattijs Korpershoek <mkorpershoek@baylibre.com>
Subject: [PATCH v3 0/4] input: MT6358 PMIC button support
Date: Fri, 2 Jul 2021 15:43:06 +0200 [thread overview]
Message-ID: <20210702134310.3451560-1-mkorpershoek@baylibre.com> (raw)
The MediaTek MT6358 PMIC has support for two buttons: PWR and HOME.
The interrupt logic is a little different than other PMICs from the
same family:
for MT6323 and MT6397, we have one interrupt source per button
* for MT6358, we have two interrupts lines per button: the press and
* release interrupts are distinct sources.
Changes since original v2 at [1]:
* added 4th patch with device tree enable
* cover letter title prefixed with 'input'
This series depends on [2]
[1] https://lore.kernel.org/r/20210512152648.39961-1-mkorpershoek@baylibre.com
[2] https://lore.kernel.org/r/20210506094116.638527-1-mkorpershoek@baylibre.com
This has been tested with evtest on mt8183-pumpkin
using for-mfd-next as base tree.
Mattijs Korpershoek (4):
Input: mtk-pmic-keys - use get_irq_byname() instead of index
dt-bindings: input: mtk-pmic-keys: add MT6358 binding definition
Input: mtk-pmic-keys - add support for MT6358
arm64: dts: mt6358: add mt6358-keys node
.../bindings/input/mtk-pmic-keys.txt | 5 +-
arch/arm64/boot/dts/mediatek/mt6358.dtsi | 12 ++++
drivers/input/keyboard/mtk-pmic-keys.c | 56 +++++++++++++++++--
3 files changed, 68 insertions(+), 5 deletions(-)
base-commit: 495fb48dbd9bcbe15859e086edd24519a6bd2961
--
2.27.0
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Fabien Parent <fparent@baylibre.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Mattijs Korpershoek <mkorpershoek@baylibre.com>
Subject: [PATCH v3 0/4] input: MT6358 PMIC button support
Date: Fri, 2 Jul 2021 15:43:06 +0200 [thread overview]
Message-ID: <20210702134310.3451560-1-mkorpershoek@baylibre.com> (raw)
The MediaTek MT6358 PMIC has support for two buttons: PWR and HOME.
The interrupt logic is a little different than other PMICs from the
same family:
for MT6323 and MT6397, we have one interrupt source per button
* for MT6358, we have two interrupts lines per button: the press and
* release interrupts are distinct sources.
Changes since original v2 at [1]:
* added 4th patch with device tree enable
* cover letter title prefixed with 'input'
This series depends on [2]
[1] https://lore.kernel.org/r/20210512152648.39961-1-mkorpershoek@baylibre.com
[2] https://lore.kernel.org/r/20210506094116.638527-1-mkorpershoek@baylibre.com
This has been tested with evtest on mt8183-pumpkin
using for-mfd-next as base tree.
Mattijs Korpershoek (4):
Input: mtk-pmic-keys - use get_irq_byname() instead of index
dt-bindings: input: mtk-pmic-keys: add MT6358 binding definition
Input: mtk-pmic-keys - add support for MT6358
arm64: dts: mt6358: add mt6358-keys node
.../bindings/input/mtk-pmic-keys.txt | 5 +-
arch/arm64/boot/dts/mediatek/mt6358.dtsi | 12 ++++
drivers/input/keyboard/mtk-pmic-keys.c | 56 +++++++++++++++++--
3 files changed, 68 insertions(+), 5 deletions(-)
base-commit: 495fb48dbd9bcbe15859e086edd24519a6bd2961
--
2.27.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-07-02 13:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 13:43 Mattijs Korpershoek [this message]
2021-07-02 13:43 ` [PATCH v3 0/4] input: MT6358 PMIC button support Mattijs Korpershoek
2021-07-02 13:43 ` Mattijs Korpershoek
2021-07-02 13:43 ` [PATCH v3 1/4] Input: mtk-pmic-keys - use get_irq_byname() instead of index Mattijs Korpershoek
2021-07-02 13:43 ` Mattijs Korpershoek
2021-07-02 13:43 ` Mattijs Korpershoek
2021-07-02 13:43 ` [PATCH v3 2/4] dt-bindings: input: mtk-pmic-keys: add MT6358 binding definition Mattijs Korpershoek
2021-07-02 13:43 ` Mattijs Korpershoek
2021-07-02 13:43 ` Mattijs Korpershoek
2021-07-02 13:43 ` [PATCH v3 3/4] Input: mtk-pmic-keys - add support for MT6358 Mattijs Korpershoek
2021-07-02 13:43 ` Mattijs Korpershoek
2021-07-02 13:43 ` Mattijs Korpershoek
2021-07-02 13:43 ` [PATCH v3 4/4] arm64: dts: mt6358: add mt6358-keys node Mattijs Korpershoek
2021-07-02 13:43 ` Mattijs Korpershoek
2021-07-02 13:43 ` Mattijs Korpershoek
2021-07-23 13:23 ` [PATCH v3 0/4] input: MT6358 PMIC button support Mattijs Korpershoek
2021-07-23 13:23 ` Mattijs Korpershoek
2021-07-23 13:23 ` Mattijs Korpershoek
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=20210702134310.3451560-1-mkorpershoek@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fparent@baylibre.com \
--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+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.