On Sat, Nov 16, 2024 at 05:53:26PM -0800, Richard Cochran wrote:

On Thu, Nov 14, 2024 at 11:59:30AM +0200, David Arinzon wrote:

quoted

+**phc_skp**         Number of skipped get time attempts (during block period).
+**phc_err**         Number of failed get time attempts (entering into block state).

Just curious...  I understand that the HW can't support a very high
rate of gettime calls and that the driver will throttle them.

But why did you feel the need to document the throttling behavior in
such a overt way?  Are there user space programs out there calling
gettime excessively?

Answering my own question (maybe)

I see that your PHC only supports gettime(), and so I guess you must
have some atypical system setup in mind.

I didn't see any comments in the cover letter or in the patch about
why the PHC isn't adjustable or how offering gettime() only is useful?

Thanks,
Richard