From: Stathis Voukelatos <stathis.voukelatos-zgcZaY4qg+21Qrn1Bg8BZw@public.gmane.org>
To: Richard Cochran <richardcochran-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver
Date: Wed, 25 Feb 2015 17:12:08 +0000 [thread overview]
Message-ID: <54EE0268.2040201@linn.co.uk> (raw)
In-Reply-To: <20150225170127.GD7703-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Hi Richard,
On 25/02/15 17:01, Richard Cochran wrote:
> 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).
>
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.
I need some more time to study your other suggestions regarding the PHY
timestamping framework.
> Thanks,
> Richard
>
Regards,
Stathis
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Stathis Voukelatos <stathis.voukelatos@linn.co.uk>
To: Richard Cochran <richardcochran@gmail.com>
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
Date: Wed, 25 Feb 2015 17:12:08 +0000 [thread overview]
Message-ID: <54EE0268.2040201@linn.co.uk> (raw)
In-Reply-To: <20150225170127.GD7703@localhost.localdomain>
Hi Richard,
On 25/02/15 17:01, Richard Cochran wrote:
> 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).
>
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.
I need some more time to study your other suggestions regarding the PHY
timestamping framework.
> Thanks,
> Richard
>
Regards,
Stathis
WARNING: multiple messages have this Message-ID (diff)
From: Stathis Voukelatos <stathis.voukelatos-zgcZaY4qg+21Qrn1Bg8BZw@public.gmane.org>
To: Richard Cochran <richardcochran-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver
Date: Wed, 25 Feb 2015 17:12:08 +0000 [thread overview]
Message-ID: <54EE0268.2040201@linn.co.uk> (raw)
In-Reply-To: <20150225170127.GD7703-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Hi Richard,
On 25/02/15 17:01, Richard Cochran wrote:
> 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).
>
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.
I need some more time to study your other suggestions regarding the PHY
timestamping framework.
> Thanks,
> Richard
>
Regards,
Stathis
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-25 17:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 16:48 [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver Stathis Voukelatos
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 ` 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 ` Stathis Voukelatos
2015-02-24 16:48 ` [PATCH net-next v4 3/3] Linn Ethernet packet sniffer driver Stathis Voukelatos
2015-02-24 16:48 ` 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
[not found] ` <20150225170127.GD7703-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-02-25 17:12 ` Stathis Voukelatos [this message]
2015-02-25 17:12 ` Stathis Voukelatos
2015-02-25 17:12 ` Stathis Voukelatos
2015-02-25 17:30 ` Richard Cochran
2015-02-27 17:22 ` Stathis Voukelatos
2015-02-27 17:22 ` Stathis Voukelatos
[not found] ` <54F0A4C4.3020407@linn.co.uk>
[not found] ` <54F0A4C4.3020407-zgcZaY4qg+21Qrn1Bg8BZw@public.gmane.org>
2015-02-27 18:14 ` Richard Cochran
2015-02-27 18:14 ` Richard Cochran
[not found] ` <20150227181447.GA11594-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-03-06 13:45 ` Stathis Voukelatos
2015-03-06 13:45 ` Stathis Voukelatos
2015-03-06 13:45 ` Stathis Voukelatos
2015-03-06 15:24 ` Richard Cochran
[not found] ` <54F98660.5070805@linn.co.uk>
2015-03-06 15:22 ` Richard Cochran
2015-03-11 11:20 ` Stathis Voukelatos
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54EE0268.2040201@linn.co.uk \
--to=stathis.voukelatos-zgczay4qg+21qrn1bg8bzw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=richardcochran-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.