[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181008153612.woazb6qmk3bvj65s@localhost>
Date: Mon, 8 Oct 2018 08:36:12 -0700
From: Richard Cochran <richardcochran@...il.com>
To: Andrew Lunn <andrew@...n.ch>
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 Mon, Oct 08, 2018 at 08:28:00AM -0700, Richard Cochran wrote:
> Let's stick to phylib for now. We can cross the other bridge when we
> come to it. Maybe the net_device->phylink will emerge for purposes
> other that time stamping. Let's not guess about how it should look.
In fact, it is kernel policy to reject new framework that lacks users.
Even if we added new net_device->phylink hooks, I bet that davem would
reject them for that reason. We can't just add to net_device for
vaporware.
The whole point of _this_ series is the first patch. That new option
is important for complete PTP support, and it could be used by every
PTP hardware. Unfortunately I only have one device in hand that
implements this, and that is the reason why you see patches 2-5.
Thanks,
Richard
Powered by blists - more mailing lists