On Thu, 09 May 2024 17:38:20 +0530, Anup Patel wrote: > Some of the PCI host controllers (such as generic PCI host controller) > use "interrupt-map" DT property to describe the mapping between PCI > endpoints and PCI interrupt pins. This is the only case where the > interrupts are not described in DT. > > Currently, there is no fw_devlink created based on "interrupt-map" > DT property so interrupt controller is not guaranteed to be probed > before the PCI host controller. This affects every platform where > both PCI host controller and interrupt controllers are probed as > regular platform devices. > > This creates fw_devlink between consumers (PCI host controller) and > supplier (interrupt controller) based on "interrupt-map" DT property. > > Signed-off-by: Anup Patel <apatel@xxxxxxxxxxxxxxxx> > Reviewed-by: Saravana Kannan <saravanak@xxxxxxxxxx> > --- > Changes since v3: > - Added a comment about of_irq_parse_raw() > - Removed redundant NULL assignments to sup_args.np > Changes since v2: > - No need for a loop to find #interrupt-cells property value > - Fix node de-reference leak when index is greater than number > of entries in interrupt-map property > Changes since v1: > - Updated commit description based on Rob's suggestion > - Use of_irq_parse_raw() for parsing interrupt-map DT property > --- > drivers/of/property.c | 52 +++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 52 insertions(+) > Applied, thanks!
