[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160218221704.GA26007@localhost.localdomain>
Date: Thu, 18 Feb 2016 23:17:04 +0100
From: Richard Cochran <richardcochran@...il.com>
To: "Christopher S. Hall" <christopher.s.hall@...el.com>
Cc: tglx@...utronix.de, mingo@...hat.com, john.stultz@...aro.org,
hpa@...or.com, jeffrey.t.kirsher@...el.com, x86@...nel.org,
linux-kernel@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
netdev@...r.kernel.org, kevin.b.stanton@...el.com,
kevin.j.clarke@...el.com
Subject: Re: [PATCH v7 5/8] time: Add history to cross timestamp interface
supporting slower devices
On Fri, Feb 12, 2016 at 12:25:26PM -0800, Christopher S. Hall wrote:
> /**
> * get_device_system_crosststamp - Synchronously capture system/device timestamp
> - * @sync_devicetime: Callback to get simultaneous device time and
> + * @get_time_fn: Callback to get simultaneous device time and
Fold this into earlier patch?
> * system counter from the device driver
> + * @history_ref: Historical reference point used to interpolate system
> + * time when counter provided by the driver is before the current interval
KernelDoc says history_ref,
> * @xtstamp: Receives simultaneously captured system and device time
> *
> * Reads a timestamp from a device and correlates it to system time
> @@ -920,6 +1035,7 @@ int get_device_system_crosststamp(int (*get_time_fn)
> struct system_counterval_t *sys_counterval,
> void *ctx),
> void *ctx,
> + struct system_time_snapshot *history_begin,
> struct system_device_crosststamp *xtstamp)
... but parameter is called history_begin.
Thanks,
Richard
Powered by blists - more mailing lists