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: Sun, 7 Oct 2018 20:27:51 +0200 From: Andrew Lunn <andrew@...n.ch> To: Richard Cochran <richardcochran@...il.com> Cc: netdev@...r.kernel.org, devicetree@...r.kernel.org, David Miller <davem@...emloft.net>, Florian Fainelli <f.fainelli@...il.com>, Jacob Keller <jacob.e.keller@...el.com>, Mark Rutland <mark.rutland@....com>, Miroslav Lichvar <mlichvar@...hat.com>, Rob Herring <robh+dt@...nel.org>, Willem de Bruijn <willemb@...gle.com> Subject: Re: [PATCH V2 net-next 2/5] net: Introduce a new MII time stamping interface. On Sun, Oct 07, 2018 at 10:38:20AM -0700, Richard Cochran wrote: > Currently the stack supports time stamping in PHY devices. However, > there are newer, non-PHY devices that can snoop an MII bus and provide > time stamps. In order to support such devices, this patch introduces > a new interface to be used by both PHY and non-PHY devices. > > In addition, the one and only user of the old PHY time stamping API is > converted to the new interface. Hi Richard I'm a bit undecided about this. If you look at how we do HWMON sensors in PHYs, the probe function just registers with the HWMON subsystem. We don't have any support in phy_device, or anywhere else in the PHY core. The mii_timestamper is generic, in the same why hwmon is generic. It does not matter where the time stamper is. So i'm wondering if we should remove the special case for a PHY timestamper, remove all the phylib support, etc. I need to look at the other patches and see how this all fits together. Andrew
Powered by blists - more mailing lists