Well I'm glad you spend time on this. So I'll explain more in detail where I am on this one. I have the vendor 3.0.29 kernel patched with LSP drivers from Marvell (which includes the PHY & Net drivers). With this version (called LSPkernel now on) pulling MPP24 GPIO output up shutdown the power of the device. At first I though it could be watchdog or wol related so I deep dive into both drivers and start uncommenting register write by register write, in the end the LSPKernel start rebooting instead of poweroff when no phy register were written at all... which is when I start thinking about that its was maybe not really which reg were written but that both phy were to be writtent to at least on reg for the MPP24 to poweroff the device and that worked out. So as soon as both phy get "m88e1318_config_aneg" fucntion called from "drivers/net/phy/marvell.c" it works fine. Also maybe you can help me there although the marvell.c has m88e1318_get_wol & m88e1318_set_wol setup as part of the MARVELL_PHY_ID_88E1318S calling "ethtool -s eth0 wol g" from debian return a non-supported error .. any though ? Benoit Le 24 juil. 2014 à 00:26, Andrew Lunn <andrew@xxxxxxx> a écrit : >> Both phy are : >> marvell,88e1318 > > I don't have the datasheet for this specific phy model, but i do have > the datasheet for another similar phy. > >> example of a minimal reg write that lead MPP24 to shutdown instead >> of rebooting on original BSP driver > >> XXXXX BasicInit > > I'm assuming regOffs is decimal, and data is hex? > >> phyAdr 0: regOffs: 16 data: 3 > > Copper Specific control register. 3 means Polarity Reversal Disable & > Jabber function disable. > >> phyAdr 0: regOffs: 10 data: 830 > > Reg 10 is the 1000BASE-T Status register, which is read only! > > So this is not making much sense. Are we missing some changes to the > page register? Register 16 of page 3 is the LED control register. > > Andrew > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
