I have setup my device tree according to the specification of NXP TJA1100.
pinctrl_enet: enetgrp { /* Ethernet MII */
fsl,pins = <
MX6QDL_PAD_ENET_CRS_DV__ENET_RX_EN 0x000130B0
MX6QDL_PAD_ENET_RX_ER__ENET_RX_ER 0x000130B0
MX6QDL_PAD_KEY_COL0__ENET_RX_DATA3 0x000130B0
MX6QDL_PAD_KEY_COL2__ENET_RX_DATA2 0x0001B0B0
MX6QDL_PAD_ENET_RXD0__ENET_RX_DATA0 0x000130B0
MX6QDL_PAD_ENET_RXD1__ENET_RX_DATA1 0x0001B0B0
MX6QDL_PAD_ENET_MDC__ENET_MDC 0x000130B0
MX6QDL_PAD_ENET_MDIO__ENET_MDIO 0x0001B0B0
MX6QDL_PAD_ENET_TXD0__ENET_TX_DATA0 0x000130B0
MX6QDL_PAD_ENET_TXD1__ENET_TX_DATA1 0x0001B0B0
MX6QDL_PAD_ENET_TX_EN__ENET_TX_EN 0x000130B0
MX6QDL_PAD_KEY_ROW0__ENET_TX_DATA3 0x000130B0
MX6QDL_PAD_KEY_ROW2__ENET_TX_DATA2 0x000130B0
MX6QDL_PAD_GPIO_18__ENET_RX_CLK 0x0001B0B0
MX6QDL_PAD_ENET_REF_CLK__ENET_TX_CLK 0x0001B0B0
MX6QDL_PAD_KEY_COL4__GPIO4_IO14 0x000130B0
>;
};
/*Ethernet*/
&fec{
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_enet>;
phy-mode = "mii";
phy-handle = <ðphy>;
phy-reset-gpios = <&gpio4 14 1>; //todo
status = "okay";
mdio {
ethphy: ethernet-phy@06{
compatible = "0x0180dc48";
device_type = "ethernet-phy";
reg = <0>;
};
};
};
First problem is it does not recognize other registers but only 0. When zero is assigned then it shows an error.
Error message: "fec 2188000.ethernet eth0: MDIO read timeout" and "TJA1100 2188000.ethernet:06: read error: did_interrupt failed"
Their is an link up error. It will be really helpful for any suggestion as I am stuck with this problem for 3 weeks. I cannot find any solution.
Hi MD Mosaddek Hossain
one can look at linux/drivers/net/phy/nxp
linux.git - Automotive Linux Tree
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
I have already created a patch for this driver and I am running the driver according to the specification. But it does not recognize the phy address.