lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 12 Mar 2014 15:06:34 -0700 From: Florian Fainelli <f.fainelli@...il.com> To: Rob Herring <robherring2@...il.com> Cc: Jason Gunthorpe <jgunthorpe@...idianresearch.com>, Rob Herring <robh+dt@...nel.org>, "David S. Miller" <davem@...emloft.net>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, netdev <netdev@...r.kernel.org> Subject: Re: [PATCH v2a RESEND 2/2] of_mdio: Allow the DT to specify the phy ID and avoid autoprobing 2014-03-12 14:35 GMT-07:00 Rob Herring <robherring2@...il.com>: > On Wed, Mar 12, 2014 at 4:05 PM, Jason Gunthorpe > <jgunthorpe@...idianresearch.com> wrote: >> This makes the generic of_mdiobus_register parse the DT compatible string for >> the pattern ethernet-phy-idAAAA.BBBB. If present it should be a value that >> matches the phy-id register normally readable through MDIO. >> >> When the ID is given the phy autoprobing is defeated and the phy is >> created directly. >> >> This is necessary to support phy's that cannot be autoprobed when >> of_mdiobus_register is called. Specifically, my case has the phy in reset at >> of_mdiobus_register, the reset is only released once the ethernet driver >> starts, before it attaches to the phy. >> >> Tested on ARM Kirkwood with phy id 0x01410e90 (Marvell 88E1318) >> >> Signed-off-by: Jason Gunthorpe <jgunthorpe@...idianresearch.com> >> Acked-by: Florian Fainelli <f.fainelli@...il.com> >> --- >> drivers/of/of_mdio.c | 30 +++++++++++++++++++++++++++++- >> 1 file changed, 29 insertions(+), 1 deletion(-) >> >> There was some reworking of the original code in v3.14-rc6, this resolves the >> merge conflicts and I retested the resolved patch on Kirkwood. >> >> Florian, do you know what path to mainline a this patch should take? > > Via David's net tree. In that case, this is probably more relevant for the 'net-next' tree since it is not a bug fix and we are fairly late in the 3.14 cycle? -- Florian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists