Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Han Gao <rabenda.cn@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Han Gao <rabenda.cn@gmail.com>,
	gaohan@iscas.ac.cn, Sudeep Holla <sudeep.holla@kernel.org>,
	Cristian Marussi <cristian.marussi@arm.com>,
	Michal Simek <michal.simek@amd.com>,
	arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: arm_scmi: Drop the ARM architecture dependency
Date: Fri, 20 Nov 2026 16:43:31 +0800	[thread overview]
Message-ID: <20261120084335.3492524-1-rabenda.cn@gmail.com> (raw)
In-Reply-To: <CAMuHMdUov1u3kXzBX3ZM8rRkBdLq_M8LwQ2VtxSEOH9w68Rr2g@mail.gmail.com>

On Fri, 20 Nov 2026 09:26:47 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> Hi Han,
> 
> On Fri, 6 Nov 2026 at 20:40, Han Gao via B4 Relay
> <devnull+gaohan.iscas.ac.cn@kernel.org> wrote:
> > From: Han Gao <gaohan@iscas.ac.cn>
> >
> > The SCMI core and the mailbox and shared memory transports only use
> > generic kernel interfaces. Transports that need architecture support,
> > such as SMC, already carry their own dependencies.
> >
> > Drop the ARM and ARM64 dependency so that other architectures can use
> > SCMI. Depend on HAS_IOMEM instead, for devm_ioremap().
> >
> > Suggested-by: Michal Simek <michal.simek@amd.com>
> > Signed-off-by: Han Gao <gaohan@iscas.ac.cn>
> 
> Thanks for your patch, which is now commit fe87ede443a15969 ("firmware:
> arm: scmi: Drop the ARM architecture dependency") in scmi/for-linux-next.
> 
> > ---
> > This was patch 1 of the Zhihe A210 SoC series [1]. As Michal asked, it
> > now goes on its own through the SCMI tree.
> >
> > Since [1], it depends on HAS_IOMEM: Sashiko found that UML, which has
> > no HAS_IOMEM, failed to link devm_ioremap().
> >
> > Build tested on x86_64 without OF, i386, loongarch64, ppc64le, riscv64
> > and arm64. On UML, SCMI can no longer be selected.
> >
> > [1] https://patch.msgid.link/20261103-a210-scmi-v3-0-ee6b31580808@iscas.ac.cn
> 
> > --- a/drivers/firmware/arm_scmi/Kconfig
> > +++ b/drivers/firmware/arm_scmi/Kconfig
> > @@ -3,7 +3,7 @@ menu "ARM System Control and Management Interface Protocol"
> >
> >  config ARM_SCMI_PROTOCOL
> >         tristate "ARM System Control and Management Interface (SCMI) Message Protocol"
> > -       depends on ARM || ARM64 || COMPILE_TEST
> > +       depends on HAS_IOMEM || COMPILE_TEST
> 
> Please extend the dependencies to RISCV (from the link above, I assume
> you are targeting riscv?) instead.  There is no point in showing this
> option on architectures that have no users of SCMI; one already has
> too many relevant symbols to configure.
> People who want to build test on x86_64 without OF, i386, loongarch64,
> ppc64le, ... can just enable COMPILE_TEST.

Following Michal's suggestion[1], I'm dropping ARM/ARM64.

[1] https://lore.kernel.org/all/3d38c4a5-1a12-4af1-ac2e-413a457ce4c5@amd.com/

> 
> >         help
> >           ARM System Control and Management Interface (SCMI) protocol is a
> >           set of operating system-independent software interfaces that are
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> -- 
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds

Sent using hkml (https://github.com/sjp38/hackermail)


  reply	other threads:[~2026-11-20  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 19:40 [PATCH] firmware: arm_scmi: Drop the ARM architecture dependency Han Gao via B4 Relay
2026-11-09  7:30 ` Michal Simek
2026-11-20  8:26 ` Geert Uytterhoeven
2026-11-20  8:43   ` Han Gao [this message]
2026-11-20  8:51     ` Geert Uytterhoeven

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=20261120084335.3492524-1-rabenda.cn@gmail.com \
    --to=rabenda.cn@gmail.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=gaohan@iscas.ac.cn \
    --cc=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=sudeep.holla@kernel.org \
    /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