From: Vladimir <anykey196@gmail.com>
To: Chen-Yu Tsai <wens@kernel.org>, Samuel Holland <samuel@sholland.org>
Cc: linux-input@vger.kernel.org, linux-sunxi@lists.linux.dev,
Vladnwx <vladnwx@users.noreply.github.com>
Subject: [PATCH] Input: axp20x-pek - add AXP313a support
Date: Wed, 23 Sep 2026 15:52:14 +0500 [thread overview]
Message-ID: <20260923105215.1633-1-anykey196@gmail.com> (raw)
From: Vladnwx <vladnwx@users.noreply.github.com>
The AXP313a MFD driver registers its power button cell as "axp313a-pek",
but the axp20x-pek platform id table only matches "axp20x-pek" and
"axp221-pek". The power button therefore never probes on boards using the
AXP313a PMIC (e.g. the OrangePi Zero 2W).
Add the missing id table entry. The register layout used by the driver
matches the AXP313a, so the generic axp20x_info is reused.
Tested on: OrangePi Zero 2W (Allwinner H618 + AXP313a), kernel 7.1.13.
Signed-off-by: Vladnwx <vladnwx@users.noreply.github.com>
---
drivers/input/misc/axp20x-pek.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/input/misc/axp20x-pek.c b/drivers/input/misc/axp20x-pek.c
index 24f9e9d89..d4e2fc9a9 100644
--- a/drivers/input/misc/axp20x-pek.c
+++ b/drivers/input/misc/axp20x-pek.c
@@ -393,6 +393,10 @@ static const struct platform_device_id axp_pek_id_match[] = {
.name = "axp221-pek",
.driver_data = (kernel_ulong_t)&axp221_info,
},
+ {
+ .name = "axp313a-pek",
+ .driver_data = (kernel_ulong_t)&axp20x_info,
+ },
{ /* sentinel */ }
};
MODULE_DEVICE_TABLE(platform, axp_pek_id_match);
--
2.53.0
next reply other threads:[~2026-09-23 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 10:52 Vladimir [this message]
2026-09-23 11:02 ` [PATCH] Input: axp20x-pek - add AXP313a support sashiko-bot
[not found] ` <CANHPwASJBzich3-2QV3FNNdKX+GHQGe2FuFWu2CUXCYya=-1zA@mail.gmail.com>
2026-09-23 11:22 ` Влад СВН
2026-09-23 11:26 ` Влад СВН
-- strict thread matches above, loose matches on Subject: below --
2026-09-23 10:57 Vladimir
2026-09-23 11:07 ` sashiko-bot
2026-09-23 11:23 ` Влад СВН
2026-09-23 11:27 ` Влад СВН
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=20260923105215.1633-1-anykey196@gmail.com \
--to=anykey196@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=vladnwx@users.noreply.github.com \
--cc=wens@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