<DC-IRC> <vitekst> Unfortunately, it isn't, I tried to power the board directly through the GPIO header with an LM2596-based buck converter with the voltage increased to 5.25 V, nothing changed.
<DC-IRC> <vitekst> I've also compiled a mainline 6.1.30 kernel with the config in `/boot/config-6.1.30-meson64` with added kgdb debugging support and the `ahci` driver built in. The -22 code (`-EINVAL`) is returned in the end by `pcim_iomap_regions`, called by `pcim_iomap_regions_request_all`, called by `ahci_init_one` (`drivers/ata/ahci.c:1758`), which is the probe function.
<DC-IRC> <vitekst> I, unfortunately, don't have a sufficient level of understanding of the PCIe bus to be able to dig deeper and actually understand what's going on. Any suggestions what I could do next, please?
<DC-IRC> <vitekst> Unfortunately, it isn't, I tried to power the board directly through the GPIO header with an LM2596-based buck converter with the voltage increased to 5.25 V, nothing changed. I didn't even attach any drives in this case - it's just the CM4IO board with the CM4 module in it and the mPCIe SATA controller.
<DC-IRC> <vitekst> I've also compiled a mainline 6.1.30 kernel with the config in `/boot/config-6.1.30-meson64` with added kgdb debugging support and the `ahci` driver built in. The -22 code (`-EINVAL`) is returned in the end by `pcim_iomap_regions`, called by `pcim_iomap_regions_request_all`, called by `ahci_init_one` (`drivers/ata/ahci.c:1758`), which is the probe function.
<DC-IRC> <vitekst> I, unfortunately, don't have a sufficient level of understanding of the PCIe bus to be able to dig deeper and actually understand what's going on. Any suggestions what I could do next, please?
<DC-IRC> <vitekst> Also, the patch for the Coral NPU or whatever (https://forum.khadas.com/t/problem-with-meson-pcie-patch/14683) isn't applied, at least in my case.
<DC-IRC> <narmstrong> The error is weird because on the boot log the bars has been set up for the device so iomap should work
<DC-IRC> <vitekst> Really? I believe the `[ 2.616260] pci 0000:00:00.0: BAR 6: assigned [mem 0xfc700000-0xfc70ffff pref]` line concerns only integrated USB 3.0 controller of the SoC (`16c3:abcd`, at `0000:00:00.0`). The ASmedia SATA controller is `0000:01:00.0` (`1b21:1064`).
<DC-IRC> <vitekst> ...and, hmm, I don't see any other BAR assignments anywhere in the kernel log.
<DC-IRC> <narmstrong> There’s no integrated pcie usb3 contrôler in the soc
<DC-IRC> <narmstrong> This is the root port
<DC-IRC> <narmstrong> Can you run a lspci -vvvv ?
<DC-IRC> <narmstrong> It’s weird the bars haven’t been assigned
<DC-IRC> <vitekst> Sure, here's the output.