Re: [PATCH v4 1/4] Produce system time from correlated clocksource

Richard Cochran
2015-10-20T19:36:50Z

On Tue, Oct 20, 2015 at 09:11:21PM +0200, Thomas Gleixner wrote:
> Darn, we don't want to have that kind of sampling in every driver
> which has this kind of problem even if it looks like the simpler
> choice for this particular use case. This is going to be something
> which next generation chips will have on more than just the audio
> interface and we realy want to have a generic solution for this.

Right, having multiple drivers sampling is bad.

Just thinking out loud: how about a service layer that can handle
multiple drivers? The layer samples at the maximum requested rate,
and buffers the history for the maximum requested backlog. The
non-max rate users simply get a higher resolution than they need.

A generic solution would handle any history length for old time
stamps, within reason. I think hard coding 4 ms (or 8 ms or 800 ms)
is clunky.

Thanks,
Richard