Open jjakob opened 3 years ago
I can confirm that this also happens with the 5.6.14 and 5.7.2 images
Did some more digging. It looks like the following entry in drivers/staging/mt7621-dts/gbpc1.dts is causing the leds to fail:
&pcie {
pinctrl-names = "default";
pinctrl-0 = <&pcie_pins>;
reset-gpios = <&gpio 19 GPIO_ACTIVE_LOW>,
<&gpio 8 GPIO_ACTIVE_LOW>,
<&gpio 7 GPIO_ACTIVE_LOW>;
status = "okay";
};
On my PC2, I put this override in drivers/staging/mt7621-dts/gbpc1.dts:
&pcie {
pinctrl-names = "default";
pinctrl-0 = <&pcie_pins>;
reset-gpios = <&gpio 19 GPIO_ACTIVE_LOW>;
status = "okay";
};
I need to look at the schematic some more, but I don't think the other two resets are hooked up on the PC2 as the pins used are part of the RGMII interface for eth1. I also think they should be GPIO22 and GPIO27 based on my reading of the schematic.
Hope this helps.
After looking at the schematic and the BOMs some more here is what seems to be going on: GB-PC1: reset pins: GPIO 19, GPIO 22 and GPIO 27 but R70,R23,R319 and R1772 are not installed per the BOM so again, no reset pins are connected. GB-PC2: No Reset pins connected between the CPU and the Pcie to sata bridges
So I think the reset-gpios statement can be removed completely from the dts files, but leaving in gpio 19 does not seem to cause any harm.
Hi, I recently upgraded from 5.4 to 5.10 and after booting I noticed that the LEDs weren't working any more. Investigating, I found the leds-gpio module didn't load cause of "error -16". Looking at dmesg shows some errors in applying the DT settings. Full dmesg attached. dmesg_dt_failed.log