[FS#1055] Youku YK1: No ethernet devices

LEDE Bugs lede-bugs at lists.infradead.org
Thu Oct 12 03:37:38 PDT 2017


The following task has a new comment added:

FS#1055 - Youku YK1: No ethernet devices
User who did this - Mathias Kresin (mkresin)

----------
Nope, your issue is:

> [    0.932648] rt2880-pinmux pinctrl: pin io40 already requested by pinctrl; cannot claim for 10100000.ethernet
[    0.952295] rt2880-pinmux pinctrl: pin-40 (10100000.ethernet) status -22
[    0.965662] rt2880-pinmux pinctrl: could not request pin 40 (io40) from group ephy  on device rt2880-pinmux
[    0.985083] mtk_soc_eth 10100000.ethernet: Error applying setting, reverse things back
[    1.000882] mtk_soc_eth: probe of 10100000.ethernet failed with error -22

The SoC pins of the ephy group are referenced/configured twice with contrary settings.

In target/linux/ramips/dts/mt7620a.dtsi (which is included by YOUKU-YK1.dts), the ephy pins are configured as


ephy_pins: ephy {
	ephy {
		ralink,group = "ephy";
		ralink,function = "ephy";
	};
};


and referenced by the YOUKU-YK1.dts with


&ethernet {
	pinctrl-0 = ;
};


But in the YOUKU-YK1.dts the Pins of the ephy group are configured as GPIOs (&gpio2 0 to &gpio2 4 - used by the wan LED):


&pinctrl {
	state_default: pinctrl0 {
		default {
			ralink,group = "i2c", "uartf", "rgmii1", "rgmii2", "ephy", "wled", "nd_sd";
			ralink,function = "gpio";
		};
	};
};


Either of both is wrong.

Since it seems to me you are able to build images on your own. Would you please test which of both is wrong.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=1055#comment3587



More information about the lede-bugs mailing list