On Wed, Feb 21, 2018 at 04:26:06PM +0100, Oliver Westermann wrote:
> I got curious after your last messages and again dove deeper into the
> kernel and drivers and tried to find out what happens when.
> Just FYI: I inherited the code, so feel free to criticize and suggest
> improvements where
2018-02-16 17:51 GMT+01:00 Keller, Jacob E :
>
> Even the interrupt itself takes up to 12 ms sometimes?
>
I got curious after your last messages and again dove deeper into the
kernel and drivers and tried to find out what happens when.
Just FYI: I inherited the code, so
On Wed, Feb 21, 2018 at 04:26:06PM +0100, Oliver Westermann wrote:
> This work queue is handled by the phy_change() function (in phy.c), which
> in a subfunction retrieves the timestamp from the phy (this is the
> add_event call from the trace above). This is delayed by 4ms.
That code in phy.c is
Hi,
> -Original Message-
> From: Oliver Westermann [mailto:owesterm...@gmail.com]
> Sent: Friday, February 16, 2018 1:20 AM
> To: Richard Cochran <richardcoch...@gmail.com>
> Cc: linuxptp-devel@lists.sourceforge.net
> Subject: Re: [Linuxptp-devel] Handling mis
2018-02-13 19:36 GMT+01:00 Richard Cochran :
> On Tue, Feb 13, 2018 at 07:01:22PM +0100, Oliver Westermann wrote:
> > The issue is that the PHY only has two slots for timestamps, one for
> > outgoing packages and one for incoming packages. If the device in
> question
> >
On Tue, Feb 13, 2018 at 07:01:22PM +0100, Oliver Westermann wrote:
> The issue is that the PHY only has two slots for timestamps, one for
> outgoing packages and one for incoming packages. If the device in question
> is a ptp master and has multiple slave, it sometimes happen that both
> DELAY_REQ
On Tue, Feb 13, 2018 at 07:01:22PM +0100, Oliver Westermann wrote:
> Is there a reason not to do this or a better idea to use linuxptp on
> systems with similar hardware constraints?
I have had such HW, and I usually just set "fault_reset_interval ASAP"
in the configuration.
> Are there design
I've a setup of multiple devices with a ARM CPU using a Marvell PHY with
hardware timestamping capabilitys for networking.
These Marvell PHYs analyse incoming and outgoing packages for PTP packages,
saves a hardware timestamp and issues a interrupt.
The PHY driver catches the interrupt, gets the