public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	Robert Moore <robert.moore@intel.com>,
	Hanjun Guo <guohanjun@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	Thomas Gleixner <tglx@kernel.org>, <linux-acpi@vger.kernel.org>,
	<acpica-devel@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-pci@vger.kernel.org>
Subject: Re: [PATCH v3 1/6] irqdomain: Add parent field to struct irqchip_fwid
Date: Thu, 15 Jan 2026 12:17:51 +0000	[thread overview]
Message-ID: <20260115121751.00004b9f@huawei.com> (raw)
In-Reply-To: <20260115-gicv5-host-acpi-v3-1-c13a9a150388@kernel.org>

On Thu, 15 Jan 2026 10:50:47 +0100
Lorenzo Pieralisi <lpieralisi@kernel.org> wrote:

> The GICv5 driver IRQ domain hierarchy requires adding a parent field to
> struct irqchip_fwid so that core code can reference a fwnode_handle parent
> for a given fwnode.
> 
> Add a parent field to struct irqchip_fwid and update the related kernel API
> functions to initialize and handle it.
> 
> Signed-off-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
> Cc: Thomas Gleixner <tglx@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>

Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>



  reply	other threads:[~2026-01-15 12:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15  9:50 [PATCH v3 0/6] irqchip/gic-v5: Code first ACPI boot support Lorenzo Pieralisi
2026-01-15  9:50 ` [PATCH v3 1/6] irqdomain: Add parent field to struct irqchip_fwid Lorenzo Pieralisi
2026-01-15 12:17   ` Jonathan Cameron [this message]
2026-01-15  9:50 ` [PATCH v3 2/6] PCI/MSI: Make the pci_msi_map_rid_ctlr_node() interface firmware agnostic Lorenzo Pieralisi
2026-01-15  9:50 ` [PATCH v3 3/6] irqchip/gic-v5: Split IRS probing into OF and generic portions Lorenzo Pieralisi
2026-01-15 12:23   ` Jonathan Cameron
2026-01-15  9:50 ` [PATCH v3 4/6] irqchip/gic-v5: Add ACPI IRS probing Lorenzo Pieralisi
2026-01-15 12:30   ` Jonathan Cameron
2026-01-15  9:50 ` [PATCH v3 5/6] irqchip/gic-v5: Add ACPI ITS probing Lorenzo Pieralisi
2026-01-15  9:50 ` [PATCH v3 6/6] irqchip/gic-v5: Add ACPI IWB probing Lorenzo Pieralisi
2026-01-18 11:00 ` [PATCH v3 0/6] irqchip/gic-v5: Code first ACPI boot support Lorenzo Pieralisi
2026-01-18 14:47   ` Thomas Gleixner
2026-01-19  8:19     ` Lorenzo Pieralisi
2026-01-19 13:54       ` Thomas Gleixner
2026-01-20 10:16         ` Lorenzo Pieralisi
2026-01-23  8:42           ` Lorenzo Pieralisi
2026-01-26 20:42             ` Rafael J. Wysocki
2026-01-27 14:34               ` Rafael J. Wysocki

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=20260115121751.00004b9f@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=acpica-devel@lists.linux.dev \
    --cc=bhelgaas@google.com \
    --cc=guohanjun@huawei.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=maz@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robert.moore@intel.com \
    --cc=sudeep.holla@arm.com \
    --cc=tglx@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