[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a0f38ev5E4Zvg_3BS+1UN2NzYSw+dyRHXDwLCWgREXJ6g@mail.gmail.com>
Date: Wed, 15 Aug 2018 22:33:01 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Bryan.Whitehead@...rochip.com
Cc: UNGLinuxDriver@...rochiptechnology.mail.onmicrosoft.com,
David Miller <davem@...emloft.net>,
YueHaibing <yuehaibing@...wei.com>,
Networking <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] net: lan743x_ptp: convert to ktime_get_clocktai_ts64
On Wed, Aug 15, 2018 at 8:03 PM <Bryan.Whitehead@...rochip.com> wrote:
>
> >
> > Question: this is the only ptp driver that sets the hardware time to the
> > current system time in TAI. Why does it do that?
>
> This is done when the driver starts up after reset. Otherwise the clock is off by 48 years.
> It seemed to me that the system time was the most appropriate clock to sync to.
> If my reasoning is incorrect, please enlighten me.
I've never worked with PTP, but my understanding from looking at the other
drivers is that the time normally gets set either from another host through the
PTP protocol, or using clock_settime() from user space with the current time.
Arnd
Powered by blists - more mailing lists