07:18 <repk> In any case that someone is struggling with meson's pcie there is a mistake in the amlogic,meson-pcie.txt documentation that leads to weird behaviour depending on the device connected

07:19 <repk> ranges = <0x82000000 0 0 0x0 0xf9c00000 0 0x00300000>;

07:19 <repk> should be "ranges = <0x82000000 0 0xf9c00000 0x0 0xf9c00000 0 0x00300000>;" memory space bus address base should be at the same offset as the cpu address base

07:20 <repk> or the BARs would be wrongly configured

11:23 <narmstrong> repk: on which soc ? I adeed support on G12B https://github.com/superna9999/linux/tree/amlogic/v5.4/g12a-pcie and the VIM3

11:24 <narmstrong> repk: are you testing on AXG ? because the memory adresses on G12a/b are really different

11:24 <narmstrong> https://github.com/superna9999/linux/commit/6d3fd8258e30b3131ad1759c607da9bf57225a9a

11:24 <narmstrong> note: IRQ_TYPE_LEVEL_HIGH is needed otherwise we can miss MSI interrupts

12:14 <repk> narmstrong: yes I am on AXG

12:17 <repk> narmstrong: your ranges are fine in meson-g12-common.dtsi

12:17 <repk> anges = <0x81000000 0 0 0x0 0xfc600000 0 0x00100000

12:17 <repk> 0x82000000 0 0xfc700000 0x0 0xfc700000 0 0x1900000>;

12:18 <repk> memory range bus address base is at 0xfc700000 and not 0

12:18 <repk> that is why it works :)

12:19 <repk> I/O range (0x81000000) can be at 0x0. Also it seems to be deprecated so I removed it