From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: Lei Xue <lei.xue@mediatek.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Sean Wang <sean.wang@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
yong.mao@mediatek.com, qingliang.li@mediatek.com,
Fred-WY.Chen@mediatek.com, ot_cathy.xu@mediatek.com,
ot_shunxi.zhang@mediatek.com, ot_yaoy.wang@mediatek.com,
ot_ye.wang@mediatek.com, linux-acpi@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH 2/3] pinctrl: mediatek: Add acpi support
Date: Wed, 26 Nov 2025 17:52:59 +0100 [thread overview]
Message-ID: <aScwaxBG53dnZ4a4@lpieralisi> (raw)
In-Reply-To: <CAD++jL=h4ZEgrjgGOfgFyAXBM7EL91ZD-La82UQ7GPOXv8h9WQ@mail.gmail.com>
[+cc: RobH for his information]
On Wed, Nov 26, 2025 at 10:10:15AM +0100, Linus Walleij wrote:
> On Tue, Nov 25, 2025 at 3:36 AM Lei Xue <lei.xue@mediatek.com> wrote:
>
> > Add acpi support in the common part of pinctrl driver. Parsing
> > hardware base addresses and irq number to initialize eint
> > accroding to the acpi table data.
> >
> > Signed-off-by: Lei Xue <lei.xue@mediatek.com>
>
> I'd ideally like Andy and the ARM64 ACPI maintainers look on
> this. (Added to To:) and CC linux-acpi@vger.kernel.org.
>
> I'm not aware of the best way to deal with ACPI in combined drivers
> but things like this:
>
> > - hw->base[i] = devm_platform_ioremap_resource_byname(pdev,
> > - hw->soc->base_names[i]);
> > + hw->base[i] = is_of_node(fwnode)
> > + ? devm_platform_ioremap_resource_byname(pdev, hw->soc->base_names[i])
> > + : devm_platform_get_and_ioremap_resource(pdev, i, NULL);
>
> Just look really quirky, I think there are better ways to go about
> this and sometimes the ACPI maintainers give some good
> pushback about the firmware as well.
How are pdev->resource initialized ? For OF I suppose the names come from
"reg-names" (that don't exist in ACPI, yet), for ACPI I assume they come
from a _CRS (and you can't tag them by name for the reason above) ?
I assume that in ACPI the _CRS resource order is foolproof against the
variaty of SOCs this code has to deal with.
I also assume/hope that we don't want to add a "reg-names" _DSD property either
in ACPI to deal with this seamlessly in DT/ACPI (that was done for
"interrupt-names"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware-guide/acpi/enumeration.rst?h=v6.18-rc7#n188
I am sorry I have got more questions than answers here - it would be good
to understand where the line is drawn when it comes to OF/ACPI and fwnode
heuristics compatibility.
Thanks,
Lorenzo
next prev parent reply other threads:[~2025-11-26 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 2:36 [PATCH 0/3] Add pinctrl and GPIO support for MediaTek MT8901 Lei Xue
2025-11-25 2:36 ` [PATCH 1/3] pinctrl: mediatek: Add gpio-range record in pinctrl driver Lei Xue
2025-11-26 18:06 ` Andy Shevchenko
2025-11-25 2:36 ` [PATCH 2/3] pinctrl: mediatek: Add acpi support Lei Xue
2025-11-26 9:10 ` Linus Walleij
2025-11-26 16:52 ` Lorenzo Pieralisi [this message]
2025-11-26 18:06 ` Andy Shevchenko
2025-11-27 10:06 ` Lorenzo Pieralisi
2025-11-27 14:29 ` Andy Shevchenko
2025-11-27 15:53 ` Lorenzo Pieralisi
2025-11-25 2:36 ` [PATCH 3/3] pinctrl: mediatek: mt8901: Add pinctrl driver for MT8901 Lei Xue
2025-11-25 9:56 ` 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=aScwaxBG53dnZ4a4@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=Fred-WY.Chen@mediatek.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=guohanjun@huawei.com \
--cc=lei.xue@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=ot_cathy.xu@mediatek.com \
--cc=ot_shunxi.zhang@mediatek.com \
--cc=ot_yaoy.wang@mediatek.com \
--cc=ot_ye.wang@mediatek.com \
--cc=qingliang.li@mediatek.com \
--cc=robh@kernel.org \
--cc=sean.wang@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=yong.mao@mediatek.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;
as well as URLs for NNTP newsgroup(s).