From: sashiko-bot@kernel.org
To: "Daniel Palmer" <daniel@thingy.jp>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] of/address: Drop ISA parts when !CONFIG_ISA
Date: Fri, 26 Jun 2026 17:35:21 +0000 [thread overview]
Message-ID: <20260626173521.8D83A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260626171906.476688-1-daniel@thingy.jp>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Wrapping the 'isa' OF bus translator in `#ifdef CONFIG_ISA` breaks I/O address translation for LPC/ISA bridges on architectures that do not enable `CONFIG_ISA`.
--
commit 2b56de0432a2e0bc839872a80da8947f0a3d2b72
Author: Daniel Palmer <daniel@thingy.jp>
of/address: Drop ISA parts when !CONFIG_ISA
This commit wraps the ISA-specific address translation code in of/address.c
with #ifdef CONFIG_ISA. This is intended to reduce code and data size on
configurations that do not enable CONFIG_ISA.
> diff --git a/drivers/of/address.c b/drivers/of/address.c
> index cf4aab11e9b1f..9b2f0d462fb59 100644
> --- a/drivers/of/address.c
> +++ b/drivers/of/address.c
[ ... ]
> @@ -349,6 +351,7 @@ static const struct of_bus of_busses[] = {
> .get_flags = of_bus_pci_get_flags,
> },
> #endif /* CONFIG_PCI */
> +#ifdef CONFIG_ISA
> /* ISA */
> {
> .name = "isa",
> .addresses = "reg",
> .match = of_bus_isa_match,
> .count_cells = of_bus_isa_count_cells,
> .map = of_bus_isa_map,
> .translate = of_bus_default_flags_translate,
> .flag_cells = 1,
> .get_flags = of_bus_isa_get_flags,
> },
> +#endif /* CONFIG_ISA */
[Severity: High]
Will this break I/O address translation for LPC/ISA bridges on architectures
that do not enable CONFIG_ISA?
While the architecture itself might not have CONFIG_ISA enabled (such as
ARM64, PowerPC, or MIPS), they often still use LPC bridges in their device
trees for devices like RTC, UART, or IPMI nodes.
If this "isa" translator is completely disabled, the bus mapping will fall
back to the "default" translator. The default translator will incorrectly
parse these resources as IORESOURCE_MEM instead of IORESOURCE_IO.
Could this prevent drivers relying on I/O space access from probing or
mapping resources correctly on those platforms?
> /* Default with flags cell */
> {
> .name = "default-flags",
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260626171906.476688-1-daniel@thingy.jp?part=1
prev parent reply other threads:[~2026-06-26 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 17:19 [PATCH] of/address: Drop ISA parts when !CONFIG_ISA Daniel Palmer
2026-06-26 17:35 ` sashiko-bot [this message]
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=20260626173521.8D83A1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@thingy.jp \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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