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  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]
Date:   Wed, 13 Feb 2019 08:41:12 -0800
From:   Tony Lindgren <>
To:     Lokesh Vutla <>
Cc:, Nishanth Menon <>,
        Santosh Shilimkar <>,
        Rob Herring <>,,,
        Linux ARM Mailing List <>,,
        Device Tree Mailing List <>,
        Sekhar Nori <>, Tero Kristo <>,
        Peter Ujfalusi <>
Subject: Re: [PATCH v5 09/10] soc: ti: Add MSI domain support for K3
 Interrupt Aggregator

* Lokesh Vutla <> [190212 07:43]:
> With the system coprocessor managing the range allocation of the
> inputs to Interrupt Aggregator, it is difficult to represent
> the device IRQs from DT.
> The suggestion is to use MSI in such cases where devices wants
> to allocate and group interrupts dynamically.
> Create a MSI domain bus layer that allocates and frees MSIs for
> a device.
> APIs that are implemented are:
> - inta_msi_create_irq_domain() that creates a MSI domain
> - inta_msi_domain_alloc_irqs() that creates MSIs for the
>   specified device and source indexes.
> - inta_msi_domain_free_irqs() frees the grouped irqs.

Can you please describe what all code will be calling these

If the callers are limited to drivers/soc/ti, then you
can can maybe make it local and get rid of the exported
custom functions as it's all built-in anyways.

Or does the dma ring accelerator for example need to call

If various subsystems will be calling these I'd assume
we'd have some generic API.. Marc, any comments on that?



Powered by blists - more mailing lists