Hi,
I am porting the kernel from 4.9.59 to 5.10.100 according to our custom board speciifcations..
While poring with respect o dts file i found the error "Label or path phy_sel not found dts file"
when i went back to 4.9.59 kernel that phy_sel is defined in am33xx.dtsi file.. hence forth i am not finding error. in 4.9.59 kernel compilations.. as i am able to find phy_sel that is defined in am33xx.dtsi
when i compile with kernel 5.10.100.. its throwing above error.. when i went through am33xx.dtsi file.(8.2.0.24 sdk) i am not able to find phy_sel in MAC node.. how can we compile in current 5.10.100 kernel..
FYI, I am referring am335x-evmsk.dts (5.10.100 of 8.2.0.24) as we are loading during kernel booting..
Also 1 more observation i found that mac node is observed as below in 4.9.59 kernel,
mac: ethernet@4a100000 {
compatible = "ti,am335x-cpsw","ti,cpsw";
ti,hwmods = "cpgmac0";
clocks = <&cpsw_125mhz_gclk>, <&cpsw_cpts_rft_clk>;
clock-names = "fck", "cpts";
cpdma_channels = <8>;
ale_entries = <1024>;
bd_ram_size = <0x2000>;
mac_control = <0x20>;
slaves = <2>;
active_slave = <0>;
cpts_clock_mult = <0x80000000>;
cpts_clock_shift = <29>;
reg = <0x4a100000 0x800
0x4a101200 0x100>;
#address-cells = <1>;
#size-cells = <1>;
interrupt-parent = <&intc>;
/*
* c0_rx_thresh_pend
* c0_rx_pend
* c0_tx_pend
* c0_misc_pend
*/
interrupts = <40 41 42 43>;
ranges;
syscon = <&scm_conf>;
status = "disabled";
davinci_mdio: mdio@4a101000 {
compatible = "ti,cpsw-mdio","ti,davinci_mdio";
#address-cells = <1>;
#size-cells = <0>;
ti,hwmods = "davinci_mdio";
bus_freq = <1000000>;
reg = <0x4a101000 0x100>;
status = "disabled";
};
cpsw_emac0: slave@4a100200 {
/* Filled in by U-Boot */
mac-address = [ 00 00 00 00 00 00 ];
};
cpsw_emac1: slave@4a100300 {
/* Filled in by U-Boot */
mac-address = [ 00 00 00 00 00 00 ];
};
phy_sel: cpsw-phy-sel@44e10650 {
compatible = "ti,am3352-cpsw-phy-sel";
reg= <0x44e10650 0x4>;
reg-names = "gmii-sel";
};
};
But the same is not observed in the kernel which we are using 5.10.100.(8.2.0.24 sdk) is it
please let me know how to address this.. as we are using ethernet port in our custom board
