Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Shah, Tanmay" <tanmays@amd.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
	Michal Simek <michal.simek@amd.com>, Harini T <harini.t@amd.com>,
	Tanmay Shah <tanmay.shah@amd.com>,
	Saeed Nowshadi <saeed.nowshadi@amd.com>
Subject: Re: [Q] zynqmp-ipi-mailbox and SGI interrupts
Date: Fri, 16 Oct 2026 11:10:29 -0500	[thread overview]
Message-ID: <1ee3f542-e0b2-41d4-bf6a-b103dabf50cd@amd.com> (raw)
In-Reply-To: <20261015083937.8SDbdK8P@linutronix.de>

Hello,

Thank you for your email, please find my response below:

On 10/15/2026 3:39 AM, Sebastian Andrzej Siewior wrote:
> Hi,
> 
> The ZynqMP IPI Mailbox driver supports two bindings of which
> xlnx,versal-ipi-mailbox is not present in any kernel dts file and

This new bindings are for Versal and later SoCs which has buffer-less
IPI. It supports only notification to the other core without any data
transfer. The device-tree nodes may not be available in the upstream
kernel yet, but it is used by other consumers. Here is an example:

https://github.com/Xilinx/u-boot-xlnx/blob/master/arch/arm/dts/versal-net-vn-x-b2197-01-revA.dts#L100


> xlnx,zynqmp-ipi-mailbox is used in two .dtsi files.
> For the per-CPU interrupts the irq-type should be 2 (which would
> correspond with GIC_ESPI in the dts, no?) which I can't find.
> Before the IPI_IRQ_TYPE_SGI it used to check for the value less than 16
> I also can't find this in the two available dts file.
> I did browse over the "AMD Versal Virt" but it also looks not present.
> 
> My question is whether this is used or just a development step that
> never got somewhere. 

No, it is the actual use case supported by the driver. Just the
device-tree node is not in the upstream kernel, because it is usually
project/vendor/consumer specific.

> My guess is that the device tree here is preconfigured from the boot
> firmware.

Yes.

> So is this SGI-IPI a thing or not?
> 

Yes it is. Ideally, TF-A and Linux can share the IPI. If the IPI
interrupt is used by the TF-A and the expectation is that Linux mailbox
work on the same IPI (because all other IPIs are busy) then the work
around is, TF-A will generate SGI for the linux mbox driver, and the
mbox driver will use that SGI via device-tree.

It is a vendor specific use case. So the dt-node for this use case, may
not be available in the usptream kernel, but can be enabled if correct
SGI is configured via the device-tree.

Thank you,
Tanmay

> Sebastian



      reply	other threads:[~2026-10-16 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  8:39 [Q] zynqmp-ipi-mailbox and SGI interrupts Sebastian Andrzej Siewior
2026-10-16 16:10 ` Shah, Tanmay [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=1ee3f542-e0b2-41d4-bf6a-b103dabf50cd@amd.com \
    --to=tanmays@amd.com \
    --cc=bigeasy@linutronix.de \
    --cc=harini.t@amd.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=saeed.nowshadi@amd.com \
    --cc=tanmay.shah@amd.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