Am 29.08.2014 17:35, schrieb Sören Brinkmann: > On Fri, 2014-08-29 at 05:18PM +0200, Andreas Färber wrote: >> Am 29.08.2014 16:08, schrieb Michal Simek: >>> I think resolution is: >>> 1. Do not use marvell,88e1518 because it is not listed anywhere >>> 2. Do not add ethernet-phy-idAAAA.BBBB because it breaks autodetection >>> if there is different phy on the board and we shouldn't restrict us in this. >>> In spite of autodetection takes some time. >>> 3. "ethernet-phy-ieee802.3-c22" is optional that's why doesn't need to be added >>> 4. Any listed compatible string has to be parsed which takes time >>> >>> That's why I think make sense not to use any compatible string. >>> This should give us all flexibility which we want to have. >> >> Sorry, but we do need some node that we can reference via phy-handle >> from the gem node, don't we? >> >> In that case, is not specifying any compatible string a valid option? >> >> If you don't want to specify the IDs, then I would've assumed we need to >> specify the -c22 in order to have *some* compatible string in order to >> trigger loading of the appropriate driver module. > > The compatible string is listed as optional property for PHYs. So, not > having one is an option, I guess. But, I'd also prefer to at least keep > the -c22 one, since I saw problems when I tried using -c45 (the Zed phy > should support it...). > Also, so far, we haven't had any phy nodes in our Zynq dts files and > Ethernet worked, so the auto-detection there works pretty well > apparently. But it may be problematic if more than a single PHY is on > the MDIO bus, I'd assume. Hm, it didn't work for me initially, but maybe some config option was missing in multi_v7 or something else. I'll re-test next week. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- 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
