[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02dba55e-39a3-4853-ac52-834cb1c0fc7f@marvell.com>
Date: Fri, 7 Jun 2024 13:23:48 +0530
From: Amit Singh Tomar <amitsinght@...vell.com>
To: Lorenzo Pieralisi <lpieralisi@...nel.org>
Cc: linux-kernel@...r.kernel.org, Robin Murphy <robin.murphy@....com>,
Marc Zyngier <maz@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
Mark Rutland <mark.rutland@....com>,
"Rafael J. Wysocki"
<rafael@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-acpi@...r.kernel.org,
acpica-devel@...ts.linux.dev
Subject: Re: [PATCH v6 1/1] irqchip/gic-v3: Enable non-coherent
redistributors/ITSes ACPI probing
> On Fri, Jun 07, 2024 at 12:21:54AM +0530, Amit Singh Tomar wrote:
>
> [...]
>
>>> diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c
>>> index b203cfe28550..915713c0e9b7 100644
>>> --- a/drivers/acpi/processor_core.c
>>> +++ b/drivers/acpi/processor_core.c
>>> @@ -215,6 +215,21 @@ phys_cpuid_t __init acpi_map_madt_entry(u32 acpi_id)
>>> return rv;
>>> }
>>> +int __init acpi_get_madt_revision(void)
>>
>> Wondering, if we can have a generic function (acpi_get_tbl_revision) to
>> obtain the revision number for any ACPI table, not just specific to MADT?
>
> We could - I don't think there would be users other than code in this
> patch though so I thought it would not be necessary.
>
Right, it might not be essential now but I see that MPAM will be another
user of it once the MPAM patches are out.
https://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git/tree/drivers/acpi/arm64/mpam.c?h=mpam/snapshot/v6.7-rc2#n299
Thanks
-Amit
Powered by blists - more mailing lists