On Mon, Nov 02, 2015 at 07:23:12AM +, Sørensen, Stefan wrote:
> The workqueue is only used for delivering packets where the timestamp
> was lost - if a timestamp is received, the packet is delivered
> immediately. This patch may introduce a slight delay of the packets
> where the timestamp neve
On Fri, 2015-10-30 at 21:37 +0100, Richard Cochran wrote:
>
> NAK. We want to have the time stamp ASAP, because the delay between
> the transmission of the Sync and its application in the servo
> degrades or even spoils synchronization. Think of an ARM SoC with
> HZ=100. Two jiffies are 20 mill
On Fri, Oct 30, 2015 at 01:14:01PM +0100, Stefan Sørensen wrote:
> Currently rx_timestamp_work reschedules itself as a regular workqueue item,
> effectively causing it run constantly as long as there are packets left in
> the queue. Fix by using delayed workqueue items, limiting it to run only
> ev
Currently rx_timestamp_work reschedules itself as a regular workqueue item,
effectively causing it run constantly as long as there are packets left in
the queue. Fix by using delayed workqueue items, limiting it to run only
every two jiffies.
Signed-off-by: Stefan Sørensen
---
drivers/net/phy/dp
