Interfaces that have AQR-s attached to them are using USXGMII and not just
the default SGMII.
This was fine until SSDK added some sanity checking and now on Qnap 301W it
would fail with:
[ 24.740197] nss-dp
3a001800.dp5 10g-1 (uninitialized): failed to connect to phy device
[ 24.740264] nss-dp: probe of
3a001800.dp5 failed with error -14
Since this is not Qnap 301W specific lets fix it subtarget wide by
declaring the correct PHY mode for 10G AQR-s.
Signed-off-by: Robert Marko <robimarko@gmail.com>
&dp6_syn {
status = "okay";
qcom,mactype = <1>;
&dp6_syn {
status = "okay";
qcom,mactype = <1>;
phy-handle = <&aqr113c>;
label = "wan";
};
phy-handle = <&aqr113c>;
label = "wan";
};
&dp6_syn {
status = "okay";
&dp6_syn {
status = "okay";
phy-handle = <&aqr113c>;
label = "10g";
nvmem-cells = <&macaddr_lan 0>;
phy-handle = <&aqr113c>;
label = "10g";
nvmem-cells = <&macaddr_lan 0>;
&dp6_syn {
status = "okay";
&dp6_syn {
status = "okay";
phy-handle = <&aqr111b0>;
label = "lan5";
nvmem-cells = <&macaddr_dp6_syn>;
phy-handle = <&aqr111b0>;
label = "lan5";
nvmem-cells = <&macaddr_dp6_syn>;
&dp5_syn {
status = "okay";
&dp5_syn {
status = "okay";
phy-handle = <&aqr113c_1>;
label = "wan";
nvmem-cells = <&macaddr_appsblenv_ethaddr>;
phy-handle = <&aqr113c_1>;
label = "wan";
nvmem-cells = <&macaddr_appsblenv_ethaddr>;
&dp6_syn {
status = "okay";
&dp6_syn {
status = "okay";
phy-handle = <&aqr113c_2>;
label = "lan1";
nvmem-cells = <&macaddr_appsblenv_ethaddr>;
phy-handle = <&aqr113c_2>;
label = "lan1";
nvmem-cells = <&macaddr_appsblenv_ethaddr>;