Re: [net-next 03/15] net/mlx5: Add adjphase function to support hardware-only offset control
From: Richard Cochran <richardcochran@gmail.com>
Date: 2023-01-23 22:39:45
From: Richard Cochran <richardcochran@gmail.com>
Date: 2023-01-23 22:39:45
On Mon, Jan 23, 2023 at 11:13:35AM -0800, Jacob Keller wrote:
quoted
1. Can the PHC servo change the frequency and not be expected to reset it back to the frequency before the phase control word is issued? If it's an expectation for the phase control word to reset the frequency back, I think that needs to be updated in the comments as a requirement.My understanding from what Richard said is that .adjphase basically offloads the entire servo and corrections to the hardware, and thus would become responsible for maintaining the phase correction long term, and callers would not use both .adjphase at the same time as .adjtime or .adjfine
Right.
quoted
2. Is it expected that a PHC servo implementation has a fixed configuration? In userspace servo implementations, configuration parameters are supported. Would we need devlink parameters to support configuring a PHC servo?I would assume some sort of parameter configuration, either via devlink or something in the ptp_clock ecosystem if we get a device that has such configuration?
Yeah, but so far no one has asked for this. Could also be debugfs if no commonality between hardware exists. Thanks, Richard