LKML Archive on
help / color / mirror / Atom feed
From: Stathis Voukelatos <>
To: <>, <>,
Subject: Re: [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver
Date: Fri, 6 Mar 2015 13:45:55 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20150227181447.GA11594@localhost.localdomain>

Hi Richard,

On 27/02/15 18:14, Richard Cochran wrote:
 >> The H/W does have the capability to do that. However, in order to
 >> implement it there will be some architectural changes needed
 >> in the kernel. This module cannot really pretend to be a PHY.
 >> In the real world it sits between the MAC and the PHY.
 > Right.
 > Here is one idea.  Put a link to the TS device in the PHY's DT node.
 > Then, in phy_probe, check if the PHY's four methods, ts_info,
 > hwtstamp, rxtstamp, and txtstamp, are all null.  If so, check for a DT
 > link from the PHY's node to a TS device driver.  If found, then set
 > the four methods to call into the TS driver's callbacks.
 > Just off of the top of my head.

Thank you for your help and suggestions.

Although the PTP way appears to be the best from an architectural point
of view, we have some questions as whether it is suitable for the audio
use cases that this module is mainly intended for.
To use the PTP terminology in a large installation we would have a
potentially large number of clock domains.
It is not clear how to easily manage the creation and allocation of 
domains. In addition the clock will be pulled according to the audio
stream and it would be undesirable for other unrelated PTPv2 devices
on the network to join the clock domain and have their clocks 
synchronized to it.

The patch in its current form would allow a move to Linux using our
existing synchronization protocols (which are open-source). A move
to PTP is something to consider but will involve a fair amount of
redesign including upgrade of legacy products.

 > Thanks,
 > Richard

Thank you,

  reply	other threads:[~2015-03-06 13:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 16:48 Stathis Voukelatos
2015-02-24 16:48 ` [PATCH net-next v4 1/3] Linn Ethernet packet sniffer: device tree binding and vendor prefix Stathis Voukelatos
2015-02-24 16:48 ` [PATCH net-next v4 2/3] Linn packet sniffer core framework Stathis Voukelatos
2015-02-24 16:48 ` [PATCH net-next v4 3/3] Linn Ethernet packet sniffer driver Stathis Voukelatos
2015-02-25 15:19 ` [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver Richard Cochran
2015-02-25 17:01   ` Richard Cochran
2015-02-25 17:12     ` Stathis Voukelatos
2015-02-25 17:30       ` Richard Cochran
2015-02-27 17:22         ` Stathis Voukelatos
     [not found]         ` <>
2015-02-27 18:14           ` Richard Cochran
2015-03-06 13:45             ` Stathis Voukelatos [this message]
2015-03-06 15:24               ` Richard Cochran
     [not found]             ` <>
2015-03-06 15:22               ` Richard Cochran
2015-03-11 11:20                 ` Stathis Voukelatos
2015-03-11 15:03                   ` Richard Cochran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).