[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <F8F52C51-9E03-4E05-AB56-809C37C2BF58@gmail.com>
Date: Wed, 08 Jun 2022 13:58:45 -0700
From: Jonathan Lemon <jonathan.lemon@...il.com>
To: Richard Cochran <richardcochran@...il.com>
Cc: netdev@...r.kernel.org, kernel-team@...com,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Lasse Johnsen <l@...johnsen.me>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH net-next v6 3/3] net: phy: Add support for 1PPS out and external timestamps
On 8 Jun 2022, at 13:50, Richard Cochran wrote:
> On Wed, Jun 08, 2022 at 01:44:51PM -0700, Jonathan Lemon wrote:
>> The perout function is used to generate a 1PPS signal, synchronized
>> to the PHC. This is accomplished by a using the hardware oneshot
>> functionality, which is reset by a timer.
>
> Is this now really in sync with the PHC?
>
> (previously there was talk about it being random phase/frequency)
Yes - I removed that function.
In the current code, the target time is loaded into the registers,
and the hw generates an output when the PHC matches the target.
—
Jonathan
Powered by blists - more mailing lists