From: sashiko-bot@kernel.org
To: "Linus Walleij" <linusw@kernel.org>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] ARM: dts: ixp4xx: Drop the reg-offset hack
Date: Wed, 08 Jul 2026 22:33:09 +0000 [thread overview]
Message-ID: <20260708223310.71F431F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260709-ixp4xx-little-endian-v1-3-e9622d0ba9e4@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Removing `reg-offset = <3>` without a driver workaround or `reg-io-width = <4>` breaks big-endian serial consoles on IXP4xx.
--
--- Patch [3]: [PATCH 3/3] ARM: dts: ixp4xx: Drop the reg-offset hack ---
commit 441a4bee18082ddbc2bc878dd7fd00a516e2cc30
Author: Linus Walleij <linusw@kernel.org>
ARM: dts: ixp4xx: Drop the reg-offset hack
This commit removes the reg-offset = <3> property from the UART nodes in the
IXP4xx device tree. The commit message notes that this was a hack for big
endian support and that such workarounds should be handled in the drivers.
> diff --git a/arch/arm/boot/dts/intel/ixp/intel-ixp4xx.dtsi b/arch/arm/boot/dts/intel/ixp/intel-ixp4xx.dtsi
> index 0adeccabd4fef..b0f98da8def47 100644
> --- a/arch/arm/boot/dts/intel/ixp/intel-ixp4xx.dtsi
> +++ b/arch/arm/boot/dts/intel/ixp/intel-ixp4xx.dtsi
> @@ -84,11 +84,6 @@ pci@c0000000 {
> uart0: serial@c8000000 {
> compatible = "intel,xscale-uart";
> reg = <0xc8000000 0x1000>;
> - /*
> - * The reg-offset and reg-shift is a side effect
> - * of running the platform in big endian mode.
> - */
> - reg-offset = <3>;
[Severity: High]
Does removing this break big-endian serial consoles on IXP4xx?
Without reg-offset = <3> or a replacement like reg-io-width = <4>, the 8250
UART driver will default to 8-bit memory access at offset 0. On big endian
systems, this reads from the wrong byte lane, resulting in invalid data and
loss of the serial console.
Is the driver workaround mentioned in the commit message already in place to
handle this?
> reg-shift = <2>;
> interrupts = <15 IRQ_TYPE_LEVEL_HIGH>;
> clock-frequency = <14745600>;
> @@ -98,11 +93,6 @@ uart0: serial@c8000000 {
> uart1: serial@c8001000 {
> compatible = "intel,xscale-uart";
> reg = <0xc8001000 0x1000>;
> - /*
> - * The reg-offset and reg-shift is a side effect
> - * of running the platform in big endian mode.
> - */
> - reg-offset = <3>;
[Severity: High]
Similarly for uart1, will this cause a regression on big endian configurations
if the driver side doesn't already compensate for the missing offset?
> reg-shift = <2>;
> interrupts = <13 IRQ_TYPE_LEVEL_HIGH>;
> clock-frequency = <14745600>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260709-ixp4xx-little-endian-v1-0-e9622d0ba9e4@kernel.org?part=3
next prev parent reply other threads:[~2026-07-08 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 22:24 [PATCH 0/3] ARM: Enable IXP4xx to use little endian mode Linus Walleij
2026-07-08 22:24 ` [PATCH 1/3] ARM: decompressor: always set endianess on xscale Linus Walleij
2026-07-08 22:48 ` sashiko-bot
2026-07-09 19:32 ` Linus Walleij
2026-07-08 22:24 ` [PATCH 2/3] ARM: ixp4xx: Relax endianness Linus Walleij
2026-07-08 22:37 ` sashiko-bot
2026-07-08 23:04 ` Linus Walleij
2026-07-08 22:24 ` [PATCH 3/3] ARM: dts: ixp4xx: Drop the reg-offset hack Linus Walleij
2026-07-08 22:33 ` sashiko-bot [this message]
2026-07-08 23:05 ` Linus Walleij
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=20260708223310.71F431F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linusw@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