Re: [RFC v5 3/6] Add history to cross timestamp interface supporting slower devices

On Mon, Jan 4, 2016 at 4:45 AM, Christopher S. Hall wrote: > @@ -13,6 +13,9 @@ > /** > * struct tk_read_base - base structure for timekeeping readout > * @clock: Current clocksource used for timekeeping. > + * @cs_seq:Clocksource sequence is incremented per clocksource change. > + *

Re: [RFC v5 3/6] Add history to cross timestamp interface supporting slower devices

On Mon, Jan 4, 2016 at 4:45 AM, Christopher S. Hall wrote: > @@ -13,6 +13,9 @@ > /** > * struct tk_read_base - base structure for timekeeping readout > * @clock: Current clocksource used for timekeeping. > + * @cs_seq:Clocksource sequence is incremented

[RFC v5 3/6] Add history to cross timestamp interface supporting slower devices

Another representative use case of time sync and the correlated clocksource (in addition to PTP noted above) is PTP synchronized audio. In a streaming application, as an example, samples will be sent and/or received by multiple devices with a presentation time that is in terms of the PTP master

[RFC v5 3/6] Add history to cross timestamp interface supporting slower devices

Another representative use case of time sync and the correlated clocksource (in addition to PTP noted above) is PTP synchronized audio. In a streaming application, as an example, samples will be sent and/or received by multiple devices with a presentation time that is in terms of the PTP master