From: Richard Cochran Date: Tue, 20 Oct 2015 21:36:39 +0200 Subject: [Intel-wired-lan] [PATCH v4 1/4] Produce system time from correlated clocksource In-Reply-To: References: <20151020085408.GA2542@netboy> <20151020115113.GA23428@netboy> <20151020145523.GA5207@netboy> Message-ID: <20151020193639.GA15095@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: intel-wired-lan@osuosl.org List-ID: 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