[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ee121a9-6326-4cd0-8440-38f13255c3b4@machnikowski.net>
Date: Thu, 15 Aug 2024 11:41:04 +0200
From: Maciek Machnikowski <maciek@...hnikowski.net>
To: Richard Cochran <richardcochran@...il.com>, Andrew Lunn <andrew@...n.ch>
Cc: Miroslav Lichvar <mlichvar@...hat.com>,
Vadim Fedorenko <vadim.fedorenko@...ux.dev>, netdev@...r.kernel.org,
jacob.e.keller@...el.com, darinzon@...zon.com, kuba@...nel.org
Subject: Re: [RFC 0/3] ptp: Add esterror support
On 15/08/2024 06:16, Richard Cochran wrote:
> On Wed, Aug 14, 2024 at 08:33:26PM -0700, Richard Cochran wrote:
>> On Wed, Aug 14, 2024 at 03:08:07PM +0200, Andrew Lunn wrote:
>>
>>> So the driver itself does not know its own error? It has to be told
>>> it, so it can report it back to user space. Then why bother, just put
>>> it directly into the ptp4l configuration file?
>>
>> This way my first reaction as well.
>
> Actually, looking at the NTP code, we have:
>
> void process_adjtimex_modes(const struct __kernel_timex *txc,)
> {
> ...
> if (txc->modes & ADJ_ESTERROR)
> time_esterror = txc->esterror;
> ...
> }
>
> So I guess PHCs should also support setting this from user space?
>
> adding CC: Miroslav
>
> At least it would be consistent.
>
>
> Thanks,
> Richard
Yes! It's exactly what inspired this patchset :)
Powered by blists - more mailing lists