[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150225173053.GE7703@localhost.localdomain>
Date: Wed, 25 Feb 2015 18:30:53 +0100
From: Richard Cochran <richardcochran@...il.com>
To: Stathis Voukelatos <stathis.voukelatos@...n.co.uk>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver
On Wed, Feb 25, 2015 at 05:12:08PM +0000, Stathis Voukelatos wrote:
> Regarding this last point, the actual counter that generates the
> timestamps is not part of the sniffer H/W module. Timestamps are
> provided to the sniffer externally in H/W by a different module.
> Apart of that there is not eg. a sniffer register to read the
> current counter value. I wonder if it should be the driver for the
> module where the counter belongs (called Event Timer in the
> Pistachio Soc) that should register the PHC.
It is okay to have the PHC come from another driver. However, you do
need to export PHC index to the time stamping code, in order to
provide the 'phc_index' field for the ETHTOOL_GET_TS_INFO request.
You can also have one SW driver cover both HW modules, if that is
cleaner and easier. Among all the other drivers, only gianfar has the
PHC separate.
> I need some more time to study your other suggestions regarding the
> PHY timestamping framework.
>From my (limited) understanding of your HW device, I should think that
it will work. The PHY time stamping subsystem is not the most obvious
code in the world. Please feel free to ask if you have any questions.
Thanks,
Richard
--
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