Searched hist:a0e7df335afd2a8a8a688251ffee375b58b6517c (Results 1 – 5 of 5) sorted by relevance
| /openbmc/linux/drivers/hwtracing/intel_th/ |
| H A D | gth.h | diff a0e7df335afd2a8a8a688251ffee375b58b6517c Fri Feb 24 08:09:40 CST 2017 Alexander Shishkin <alexander.shishkin@linux.intel.com> intel_th: Perform time resync on capture start
On some devices (TH 2.x devices at the moment), the internal time counter
is initially not synchronized to the global crystal clock, so the time
stamps it produces will not be useful. In this case, the driver needs
to force the time counter resync.
This applies the workaround to relevant devices.
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
|
| H A D | gth.c | diff a0e7df335afd2a8a8a688251ffee375b58b6517c Fri Feb 24 08:09:40 CST 2017 Alexander Shishkin <alexander.shishkin@linux.intel.com> intel_th: Perform time resync on capture start
On some devices (TH 2.x devices at the moment), the internal time counter
is initially not synchronized to the global crystal clock, so the time
stamps it produces will not be useful. In this case, the driver needs
to force the time counter resync.
This applies the workaround to relevant devices.
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
|
| H A D | intel_th.h | diff a0e7df335afd2a8a8a688251ffee375b58b6517c Fri Feb 24 08:09:40 CST 2017 Alexander Shishkin <alexander.shishkin@linux.intel.com> intel_th: Perform time resync on capture start
On some devices (TH 2.x devices at the moment), the internal time counter
is initially not synchronized to the global crystal clock, so the time
stamps it produces will not be useful. In this case, the driver needs
to force the time counter resync.
This applies the workaround to relevant devices.
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
|
| H A D | core.c | diff a0e7df335afd2a8a8a688251ffee375b58b6517c Fri Feb 24 08:09:40 CST 2017 Alexander Shishkin <alexander.shishkin@linux.intel.com> intel_th: Perform time resync on capture start
On some devices (TH 2.x devices at the moment), the internal time counter
is initially not synchronized to the global crystal clock, so the time
stamps it produces will not be useful. In this case, the driver needs
to force the time counter resync.
This applies the workaround to relevant devices.
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
|
| H A D | pci.c | diff a0e7df335afd2a8a8a688251ffee375b58b6517c Fri Feb 24 08:09:40 CST 2017 Alexander Shishkin <alexander.shishkin@linux.intel.com> intel_th: Perform time resync on capture start
On some devices (TH 2.x devices at the moment), the internal time counter
is initially not synchronized to the global crystal clock, so the time
stamps it produces will not be useful. In this case, the driver needs
to force the time counter resync.
This applies the workaround to relevant devices.
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
|