From: Lee Jones <lee@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Yassine Oudjana" <y.oudjana@protonmail.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Fabien Parent" <fparent@baylibre.com>,
Reported-by: "Louis-Alexis Eyraud"
<louisalexis.eyraud@collabora.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org;
Subject: Re: [PATCH] MFD: mt6397: do not use generic name for keypad sub-devices
Date: Tue, 1 Jul 2025 11:58:11 +0100 [thread overview]
Message-ID: <20250701105811.GI10134@google.com> (raw)
In-Reply-To: <r4k3pgd3ew3ypne7ernxuzwgniiyvzosbce4cfajbcu7equblt@yato35tjb3lw>
On Mon, 30 Jun 2025, Dmitry Torokhov wrote:
> Do not use "mtk-pmic-keys" when creating sub-device for the keypad to
> make sure the keypad driver will only bind to the sub-device if it has
> support for the variant/has matching compatible.
>
> Reported-by: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
> Fixes: 6e31bb8d3a63 ("mfd: mt6397: Add initial support for MT6328")
> Fixes: de58cee8c6b8 ("mfd: mt6397-core: Add MT6357 PMIC support")
> Fixes: 4a901e305011 ("mfd: mt6397-core: Add resources for PMIC keys for MT6359")
> Cc: stable@vger.kernel.org
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
>
> This is not tested so if someone with hardware could try it out that
> would be great. I *think* it should work...
My suspicion is that this will not work. Providing compatible strings
here is only for device to node matching. I do not believe the drivers
will probe using them.
You don't need H/W to test this theory. You can just feed in a DTB and
see if it probes. QEMU should be good enough for this.
> drivers/mfd/mt6397-core.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/mfd/mt6397-core.c b/drivers/mfd/mt6397-core.c
> index 5f8ed8988907..3e58d0764c7e 100644
> --- a/drivers/mfd/mt6397-core.c
> +++ b/drivers/mfd/mt6397-core.c
> @@ -136,7 +136,7 @@ static const struct mfd_cell mt6323_devs[] = {
> .name = "mt6323-led",
> .of_compatible = "mediatek,mt6323-led"
> }, {
> - .name = "mtk-pmic-keys",
> + .name = "mt6323-keys",
> .num_resources = ARRAY_SIZE(mt6323_keys_resources),
> .resources = mt6323_keys_resources,
> .of_compatible = "mediatek,mt6323-keys"
> @@ -153,7 +153,7 @@ static const struct mfd_cell mt6328_devs[] = {
> .name = "mt6328-regulator",
> .of_compatible = "mediatek,mt6328-regulator"
> }, {
> - .name = "mtk-pmic-keys",
> + .name = "mt6328-keys",
> .num_resources = ARRAY_SIZE(mt6328_keys_resources),
> .resources = mt6328_keys_resources,
> .of_compatible = "mediatek,mt6328-keys"
> @@ -175,7 +175,7 @@ static const struct mfd_cell mt6357_devs[] = {
> .name = "mt6357-sound",
> .of_compatible = "mediatek,mt6357-sound"
> }, {
> - .name = "mtk-pmic-keys",
> + .name = "mt6357-keys",
> .num_resources = ARRAY_SIZE(mt6357_keys_resources),
> .resources = mt6357_keys_resources,
> .of_compatible = "mediatek,mt6357-keys"
> @@ -196,7 +196,7 @@ static const struct mfd_cell mt6331_mt6332_devs[] = {
> .name = "mt6332-regulator",
> .of_compatible = "mediatek,mt6332-regulator"
> }, {
> - .name = "mtk-pmic-keys",
> + .name = "mt6331-keys",
> .num_resources = ARRAY_SIZE(mt6331_keys_resources),
> .resources = mt6331_keys_resources,
> .of_compatible = "mediatek,mt6331-keys"
> @@ -240,7 +240,7 @@ static const struct mfd_cell mt6359_devs[] = {
> },
> { .name = "mt6359-sound", },
> {
> - .name = "mtk-pmic-keys",
> + .name = "mt6359-keys",
> .num_resources = ARRAY_SIZE(mt6359_keys_resources),
> .resources = mt6359_keys_resources,
> .of_compatible = "mediatek,mt6359-keys"
> @@ -272,7 +272,7 @@ static const struct mfd_cell mt6397_devs[] = {
> .name = "mt6397-pinctrl",
> .of_compatible = "mediatek,mt6397-pinctrl",
> }, {
> - .name = "mtk-pmic-keys",
> + .name = "mt6397-keys",
> .num_resources = ARRAY_SIZE(mt6397_keys_resources),
> .resources = mt6397_keys_resources,
> .of_compatible = "mediatek,mt6397-keys"
> --
> 2.50.0.727.gbf7dc18ff4-goog
>
>
> --
> Dmitry
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-07-01 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 23:01 [PATCH] MFD: mt6397: do not use generic name for keypad sub-devices Dmitry Torokhov
2025-07-01 10:58 ` Lee Jones [this message]
2025-07-01 21:04 ` Dmitry Torokhov
2025-07-03 10:38 ` Louis-Alexis Eyraud
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=20250701105811.GI10134@google.com \
--to=lee@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dmitry.torokhov@gmail.com \
--cc=fparent@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louisalexis.eyraud@collabora.com \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=y.oudjana@protonmail.com \
/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