* Re: [PATCH] dt-bindings: input: mediatek,mt6779-keypad: add the MT8173 keypad
2026-09-16 3:47 [PATCH] dt-bindings: input: mediatek,mt6779-keypad: add the MT8173 keypad Ryan Brue
@ 2026-09-16 7:32 ` Mattijs Korpershoek
2026-09-16 13:02 ` AngeloGioacchino Del Regno
` (2 subsequent siblings)
3 siblings, 0 replies; 6+ messages in thread
From: Mattijs Korpershoek @ 2026-09-16 7:32 UTC (permalink / raw)
To: Ryan Brue, Dmitry Torokhov, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Matthias Brugger, AngeloGioacchino Del Regno
Cc: linux-input, devicetree, linux-kernel, linux-arm-kernel,
linux-mediatek, Ryan Brue
Hi Ryan,
Thank you for the patch.
On Tue, Sep 15, 2026 at 22:47, Ryan Brue <ryanbrue.dev@gmail.com> wrote:
> MT8173's keypad controller is the same block this driver already handles.
> Its register map agrees offset for offset with the MT6779 one -- STA 0x00,
> MEM1..MEM5 0x04..0x14, DEBOUNCE 0x18, SEL 0x20, EN 0x24 -- and
> mt6779-keypad drives it with no code change, so the node only needs the
> fallback compatible in second position. Add the mt8173 string to the
> existing enum, which is what mt6873, mt8183, mt8365 and mt8516 already do.
>
> Verified on an MT8173 board (Amazon Fire HD 10 2017): the volume rocker
> reports through mt6779-keypad with no driver modification.
>
> Assisted-by: LLM
> Signed-off-by: Ryan Brue <ryanbrue.dev@gmail.com>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH] dt-bindings: input: mediatek,mt6779-keypad: add the MT8173 keypad
2026-09-16 3:47 [PATCH] dt-bindings: input: mediatek,mt6779-keypad: add the MT8173 keypad Ryan Brue
2026-09-16 7:32 ` Mattijs Korpershoek
@ 2026-09-16 13:02 ` AngeloGioacchino Del Regno
2026-09-24 21:49 ` Rob Herring (Arm)
2026-11-02 3:24 ` Ryan Brue
3 siblings, 0 replies; 6+ messages in thread
From: AngeloGioacchino Del Regno @ 2026-09-16 13:02 UTC (permalink / raw)
To: Ryan Brue, Mattijs Korpershoek, Dmitry Torokhov, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Matthias Brugger
Cc: linux-input, devicetree, linux-kernel, linux-arm-kernel, linux-mediatek
On 9/16/26 05:47, Ryan Brue wrote:
> MT8173's keypad controller is the same block this driver already handles.
> Its register map agrees offset for offset with the MT6779 one -- STA 0x00,
> MEM1..MEM5 0x04..0x14, DEBOUNCE 0x18, SEL 0x20, EN 0x24 -- and
> mt6779-keypad drives it with no code change, so the node only needs the
> fallback compatible in second position. Add the mt8173 string to the
> existing enum, which is what mt6873, mt8183, mt8365 and mt8516 already do.
>
> Verified on an MT8173 board (Amazon Fire HD 10 2017): the volume rocker
> reports through mt6779-keypad with no driver modification.
>
> Assisted-by: LLM
> Signed-off-by: Ryan Brue <ryanbrue.dev@gmail.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> This is the binding half only. The board device tree that uses it, an Amazon
> Fire HD 10 (2017), is not upstream yet and comes with the rest of that
> board's nodes later; adding the compatible first keeps that submission from
> carrying a forward reference.
>
> No driver change goes with it. mt6779-keypad matches on the fallback, which
> is how mt8183, mt8365 and mt8516 bind today -- only mt6779 and mt6873 are in
> the driver's own match table.
> ---
> Documentation/devicetree/bindings/input/mediatek,mt6779-keypad.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/input/mediatek,mt6779-keypad.yaml b/Documentation/devicetree/bindings/input/mediatek,mt6779-keypad.yaml
> index 914dd3283df3..b45dbf805ac8 100644
> --- a/Documentation/devicetree/bindings/input/mediatek,mt6779-keypad.yaml
> +++ b/Documentation/devicetree/bindings/input/mediatek,mt6779-keypad.yaml
> @@ -27,6 +27,7 @@ properties:
> - items:
> - enum:
> - mediatek,mt6873-keypad
> + - mediatek,mt8173-keypad
> - mediatek,mt8183-keypad
> - mediatek,mt8365-keypad
> - mediatek,mt8516-keypad
>
> ---
> base-commit: fd73f4a6659897191fa0d40695fe370925dd3780
> change-id: 20260914-rbrue-suez-upstreaming-mt8173-keypad-fddc316ae098
>
> Best regards,
> --
> Ryan Brue <ryanbrue.dev@gmail.com>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] dt-bindings: input: mediatek,mt6779-keypad: add the MT8173 keypad
2026-09-16 3:47 [PATCH] dt-bindings: input: mediatek,mt6779-keypad: add the MT8173 keypad Ryan Brue
2026-09-16 7:32 ` Mattijs Korpershoek
2026-09-16 13:02 ` AngeloGioacchino Del Regno
@ 2026-09-24 21:49 ` Rob Herring (Arm)
2026-11-02 3:24 ` Ryan Brue
3 siblings, 0 replies; 6+ messages in thread
From: Rob Herring (Arm) @ 2026-09-24 21:49 UTC (permalink / raw)
To: Ryan Brue
Cc: Krzysztof Kozlowski, AngeloGioacchino Del Regno, linux-kernel,
Conor Dooley, Dmitry Torokhov, linux-arm-kernel, devicetree,
Mattijs Korpershoek, Matthias Brugger, linux-mediatek,
linux-input
On Tue, 15 Sep 2026 22:47:50 -0500, Ryan Brue wrote:
> MT8173's keypad controller is the same block this driver already handles.
> Its register map agrees offset for offset with the MT6779 one -- STA 0x00,
> MEM1..MEM5 0x04..0x14, DEBOUNCE 0x18, SEL 0x20, EN 0x24 -- and
> mt6779-keypad drives it with no code change, so the node only needs the
> fallback compatible in second position. Add the mt8173 string to the
> existing enum, which is what mt6873, mt8183, mt8365 and mt8516 already do.
>
> Verified on an MT8173 board (Amazon Fire HD 10 2017): the volume rocker
> reports through mt6779-keypad with no driver modification.
>
> Assisted-by: LLM
> Signed-off-by: Ryan Brue <ryanbrue.dev@gmail.com>
> ---
> This is the binding half only. The board device tree that uses it, an Amazon
> Fire HD 10 (2017), is not upstream yet and comes with the rest of that
> board's nodes later; adding the compatible first keeps that submission from
> carrying a forward reference.
>
> No driver change goes with it. mt6779-keypad matches on the fallback, which
> is how mt8183, mt8365 and mt8516 bind today -- only mt6779 and mt6873 are in
> the driver's own match table.
> ---
> Documentation/devicetree/bindings/input/mediatek,mt6779-keypad.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] dt-bindings: input: mediatek,mt6779-keypad: add the MT8173 keypad
2026-09-16 3:47 [PATCH] dt-bindings: input: mediatek,mt6779-keypad: add the MT8173 keypad Ryan Brue
` (2 preceding siblings ...)
2026-09-24 21:49 ` Rob Herring (Arm)
@ 2026-11-02 3:24 ` Ryan Brue
2026-11-02 4:04 ` Dmitry Torokhov
3 siblings, 1 reply; 6+ messages in thread
From: Ryan Brue @ 2026-11-02 3:24 UTC (permalink / raw)
To: Mattijs Korpershoek, Dmitry Torokhov, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Matthias Brugger,
AngeloGioacchino Del Regno
Cc: linux-input, devicetree, linux-kernel, linux-arm-kernel, linux-mediatek
Hi Dmitry,
Gentle ping on this one. It has an ack from Rob and reviews from Mattijr
and AngeloGioacchino. The device tree for the Amazon Fire HD 10 (2017)
that I'm posting for 7.5 uses it for the volume keys. The patch should
apply to input/next with a three-way merge. I can resend it rebased if
that's easier.
Thank you, best regards,
Ryan Brue
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH] dt-bindings: input: mediatek,mt6779-keypad: add the MT8173 keypad
2026-11-02 3:24 ` Ryan Brue
@ 2026-11-02 4:04 ` Dmitry Torokhov
0 siblings, 0 replies; 6+ messages in thread
From: Dmitry Torokhov @ 2026-11-02 4:04 UTC (permalink / raw)
To: Ryan Brue
Cc: Mattijs Korpershoek, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Matthias Brugger, AngeloGioacchino Del Regno,
linux-input, devicetree, linux-kernel, linux-arm-kernel,
linux-mediatek
Hi Ryan,
On Sun, Nov 01, 2026 at 09:24:58PM -0600, Ryan Brue wrote:
> Hi Dmitry,
>
> Gentle ping on this one. It has an ack from Rob and reviews from Mattijr and
> AngeloGioacchino. The device tree for the Amazon Fire HD 10 (2017) that I'm
> posting for 7.5 uses it for the volume keys. The patch should apply to
> input/next with a three-way merge. I can resend it rebased if that's easier.
Applied, sorry for the delay.
--
Dmitry
^ permalink raw reply [flat|nested] 6+ messages in thread