From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>,
linux-kernel@vger.kernel.org
Cc: Ethan Nelson-Moore <enelsonmoore@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH v3] ARM: orion5x: update board check in mss2_pci_init() to use the DT
Date: Mon, 01 Jun 2026 10:27:19 +0200 [thread overview]
Message-ID: <87wlwizmvs.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <20260517023723.92731-1-enelsonmoore@gmail.com>
Ethan Nelson-Moore <enelsonmoore@gmail.com> writes:
> The mss2_pci_init() function contains a check for the ARM machine ID
> via the machine_is_mss2() macro. The board concerned now supports only
> FDT booting, which does not use machine IDs, and therefore the code
> should be updated to check the DT compatible property instead. The
> machine was converted to FDT booting in commit fbf04d814d0a ("ARM:
> orion5x: convert Maxtor Shared Storage II to the Device Tree"). The
> presence of this machine ID check prevents the removal of machine IDs
> no longer used by the kernel from arch/arm/tools/mach-types, because
> the machine_is_*() macros are generated from mach-types. To resolve
> this issue, use of_machine_is_compatible() instead.
>
> Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
> ---
> Changes from v1: Fix mistake in commit message and remove Fixes tag -
> machine ID checks still work with DT booting if the bootloader passes
> the ID
> Changes from v2: correct changelog formatting (there were two ---
> sections in v2)
>
Applied on mvebu/arm
Thanks,
Gregory
> arch/arm/mach-orion5x/board-mss2.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-orion5x/board-mss2.c b/arch/arm/mach-orion5x/board-mss2.c
> index 9e3d69891d2f..322ae29d05aa 100644
> --- a/arch/arm/mach-orion5x/board-mss2.c
> +++ b/arch/arm/mach-orion5x/board-mss2.c
> @@ -10,7 +10,7 @@
> #include <linux/platform_device.h>
> #include <linux/pci.h>
> #include <linux/irq.h>
> -#include <asm/mach-types.h>
> +#include <linux/of.h>
> #include <asm/mach/arch.h>
> #include <asm/mach/pci.h>
> #include "orion5x.h"
> @@ -47,7 +47,7 @@ static struct hw_pci mss2_pci __initdata = {
>
> static int __init mss2_pci_init(void)
> {
> - if (machine_is_mss2())
> + if (of_machine_is_compatible("maxtor,shared-storage-2"))
> pci_common_init(&mss2_pci);
>
> return 0;
> --
> 2.43.0
>
--
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-06-01 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 2:37 [PATCH v3] ARM: orion5x: update board check in mss2_pci_init() to use the DT Ethan Nelson-Moore
2026-06-01 8:27 ` Gregory CLEMENT [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=87wlwizmvs.fsf@BLaptop.bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=enelsonmoore@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=sebastian.hesselbarth@gmail.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