Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Linus Walleij" <linusw@kernel.org>,
	"William Zhang" <william.zhang@broadcom.com>,
	"Anand Gore" <anand.gore@broadcom.com>,
	"Kursad Oney" <kursad.oney@broadcom.com>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"Broadcom internal kernel review list"
	<bcm-kernel-feedback-list@broadcom.com>,
	"Ray Jui" <rjui@broadcom.com>,
	"Scott Branden" <sbranden@broadcom.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] ARM: bcm: Enable SMP on the Genexis XG6846B
Date: Tue, 13 Oct 2026 15:22:29 -0700	[thread overview]
Message-ID: <b1666e68-6ea3-493b-9880-e896d15193bc@broadcom.com> (raw)
In-Reply-To: <20261012-genexis-xg6846-smp-v7-3-rc1-v1-0-a51d4afde4a7@kernel.org>

On 10/12/26 01:03, Linus Walleij wrote:
> When booted through CFE and mainline U-Boot, the XG6846B has no PSCI
> provider. CFE powers up CPU1 and leaves it waiting in a holding pen.
> 
> Preserve the holding pen, add a board-specific SMP method using CFE's
> GPIO mailbox and a wakeup IPI, and disable the inherited PSCI setup.
> Tested on the XG6846B with both CPUs coming online.
> 
> Assisted-by: LLM
> Signed-off-by: Linus Walleij <linusw@kernel.org>

This all looks reasonable to me, would appreciate a R-b tag from 
William/Anand/Kursad here before taking this.
-- 
Florian


  parent reply	other threads:[~2026-10-13 22:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12  8:03 [PATCH 0/3] ARM: bcm: Enable SMP on the Genexis XG6846B Linus Walleij
2026-10-12  8:03 ` [PATCH 1/3] ARM: dts: broadcom: Preserve the XG6846B CFE holding pen Linus Walleij
2026-10-12  8:03 ` [PATCH 2/3] ARM: bcm: Add CFE SMP support for the Genexis XG6846B Linus Walleij
2026-10-12  8:03 ` [PATCH 3/3] ARM: dts: broadcom: Use CFE CPU bring-up on the XG6846B Linus Walleij
2026-10-13 22:22 ` Florian Fainelli [this message]
2026-10-14  1:11 ` [PATCH 0/3] ARM: bcm: Enable SMP on the Genexis XG6846B William Zhang
2026-10-14  6:58   ` 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=b1666e68-6ea3-493b-9880-e896d15193bc@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=anand.gore@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=kursad.oney@broadcom.com \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=rafal@milecki.pl \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=william.zhang@broadcom.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