linux-kernel - Re: [PATCH RFC v2 2/2] irqchip: irq-ti-sci-inta: Add direct mapped interrupts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d9d6dc1b-cc1d-d823-8777-3a8d6d2328f7@ti.com>
Date:   Sat, 8 Apr 2023 16:57:51 +0530
From:   "Raghavendra, Vignesh" <vigneshr@...com>
To:     Marc Zyngier <maz@...nel.org>
CC:     Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
        Santosh Shilimkar <ssantosh@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC v2 2/2] irqchip: irq-ti-sci-inta: Add direct mapped
 interrupts

Hi,

On 4/8/2023 4:10 PM, Marc Zyngier wrote:
>> +static unsigned int ti_sci_inta_direct_events_am62x[] = {
>> +	/* CPSW etherenti DMA events */
>> +	TO_HWIRQ(DEV_DMASS0_PKTDMA_0, 4627),
>> +	TO_HWIRQ(DEV_DMASS0_PKTDMA_0, 4635),
>> +	TO_HWIRQ(DEV_DMASS0_PKTDMA_0, 4643),
>> +	TO_HWIRQ(DEV_DMASS0_PKTDMA_0, 4651),
>> +	TO_HWIRQ(DEV_DMASS0_PKTDMA_0, 4659),
>> +	TO_HWIRQ(DEV_DMASS0_PKTDMA_0, 4667),
>> +	TO_HWIRQ(DEV_DMASS0_PKTDMA_0, 4675),
>> +	TO_HWIRQ(DEV_DMASS0_PKTDMA_0, 4683),
>> +	TO_HWIRQ(DEV_DMASS0_PKTDMA_0, 5651),
>> +};
>> +
>> +static struct ti_sci_inta_soc_data soc_data_am62x = {
>> +	.events_list = ti_sci_inta_direct_events_am62x,
>> +	.events_list_size = ARRAY_SIZE(ti_sci_inta_direct_events_am62x),
>> +};
> I don't think these tables belong in a driver, and they are bound to
> grow without any obvious limits. 

Fair point.

> You have firmware tables that can express these things. Surely they can be put to a good use.

By firmware tables you mean device tree?

Regards
Vignesh