[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86a531cc1q.wl-maz@kernel.org>
Date: Thu, 11 Sep 2025 15:13:21 +0100
From: Marc Zyngier <maz@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-acpi@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
Will Deacon <will@...nel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Rob Herring <robh@...nel.org>,
Saravana Kannan <saravanak@...gle.com>,
Greg Kroah-Hartman
<gregkh@...uxfoundation.org>,
Sven Peter <sven@...nel.org>,
Janne Grunau
<j@...nau.net>,
Suzuki K Poulose <suzuki.poulose@....com>,
James Clark
<james.clark@...aro.org>
Subject: Re: [PATCH 01/25] irqdomain: Add firmware info reporting interface
On Tue, 09 Sep 2025 10:18:01 +0100,
Thomas Gleixner <tglx@...utronix.de> wrote:
>
> On Mon, Sep 08 2025 at 17:31, Marc Zyngier wrote:
[...]
> > @@ -69,6 +90,8 @@ void of_phandle_args_to_fwspec(struct device_node *np, const u32 *args,
> > * @translate: Given @fwspec, decode the hardware irq number (@out_hwirq) and
> > * linux irq type value (@out_type). This is a generalised @xlate
> > * (over struct irq_fwspec) and is preferred if provided.
> > + * @get_info: Given @info, report additional firmware-provided information.
> > + * Optional.
>
> get_info() is pretty generic. Can we have some more descriptive name for
> that? Also please keep the tabular formatting of the doc intact.
Would get_fwspec_info() be descriptive enough?
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists