From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753151AbbBYRBf (ORCPT ); Wed, 25 Feb 2015 12:01:35 -0500 Received: from mail-we0-f179.google.com ([74.125.82.179]:39986 "EHLO mail-we0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752492AbbBYRBd (ORCPT ); Wed, 25 Feb 2015 12:01:33 -0500 Date: Wed, 25 Feb 2015 18:01:27 +0100 From: Richard Cochran To: Stathis Voukelatos Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver Message-ID: <20150225170127.GD7703@localhost.localdomain> References: <20150225151945.GB7703@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150225151945.GB7703@localhost.localdomain> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 25, 2015 at 04:19:45PM +0100, Richard Cochran wrote: > Let me suggest another approach that stays in line with the existing > frame work. Based on the device's limitations and your own example, > it seems clear that the intended use case is synchronization for AVB > applications using gPTP. Also, forgot to say, expose your clock as a PTP Hardware Clock (PHC). Thanks, Richard