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

On 2026-10-16 11:10:29 [-0500], Shah, Tanmay wrote:
> Hello,
Hello,

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

Thank you for your email, too.

> > 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.

And it has to be a per-CPU interrupt? It can't become a regular
interrupt which is not per-CPU? Does the driver at some point access
per-CPU registers?

> Thank you,
> Tanmay
> 
Sebastian


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

Thread overview: 6+ 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
2026-10-16 16:23   ` Sebastian Andrzej Siewior [this message]
2026-10-16 16:44     ` Shah, Tanmay
2026-10-16 17:10       ` Sebastian Andrzej Siewior
2026-10-16 17:30         ` Shah, Tanmay

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=20261016162356.m2X9jbCa@linutronix.de \
    --to=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