[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180321224702.cbcq3wckmojsrgjf@localhost>
Date: Wed, 21 Mar 2018 15:47:02 -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>,
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 net-next RFC V1 5/5] net: mdio: Add a driver for InES
time stamping IP core.
On Wed, Mar 21, 2018 at 11:16:52PM +0100, Andrew Lunn wrote:
> The MAC drivers are clients of this device. They then use a phandle
> and specifier:
>
> eth0: ethernet-controller@...00 {
> compatible = "marvell,kirkwood-eth";
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <0x72000 0x4000>;
>
> timerstamper = <×tamper 2>
> }
>
> The 2 indicates this MAC is using port 2.
>
> The MAC driver can then do the standard device tree things to follow
> the phandle to get access to the device and use the API it exports.
But that would require hacking every last MAC driver.
I happy to improve the modeling, but the solution should be generic
and work for every MAC driver.
Thanks,
Richard
Powered by blists - more mailing lists