|
Revision tags: v6.4.0, v6.4.0rc1, v6.5.0, v6.2.2, v6.2.1, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3 |
|
| #
0856d15d |
| 27-Oct-2019 |
François Tigeot <ftigeot@wolfpond.org> |
drm: Switch ktime_t to its post-Linux 4.10 definition
|
|
Revision tags: v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2 |
|
| #
eb67213a |
| 26-Mar-2019 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Rewrite the callout_*() API
* Rewrite the entire API from scratch and improve compatibility
with FreeBSD. This is not an attempt to achieve full API compatibility,
as FreeBSD's API has
kernel - Rewrite the callout_*() API
* Rewrite the entire API from scratch and improve compatibility
with FreeBSD. This is not an attempt to achieve full API compatibility,
as FreeBSD's API has unnecessary complexity that coders would frequently
make mistakes interpreting.
* Remove the IPI mechanisms in favor of fine-grained spin-locks instead.
* Add some robustness features in an attempt to track down corrupted
callwheel lists due to originating subsystems freeing structures out
from under an active callout.
* The code supports a full-blown type-stable/adhoc-reuse structural
separation between the front-end and the back-end, but this feature
is currently not operational and may be removed at some future point.
Instead we currently just embed the struct _callout inside the
struct callout.
* Replace callout_stop_sync() with callout_cancel().
* callout_drain() is now implemented as a synchronous cancel instead
of an asynchronous stop, which is closer to the FreeBSD API and
expected operation for ported code (usb stack in particular). We
will just have to fix any deadlocks which we come across.
* Retain our callout_terminate() function as the 'better' way to
stop using a callout, as it will not only cancel the callout but
also de-flag the structure so it can no longer be used.
show more ...
|
|
Revision tags: v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1 |
|
| #
a1c669c2 |
| 07-Jun-2017 |
Imre Vadász <imre@vdsz.com> |
drm - Fix hrtimer, don't reset timer->function to NULL in timeout handler.
* The same hrtimer object is activated multiple times by i915(4), so we
mustn't clear timer->function in the timeout hand
drm - Fix hrtimer, don't reset timer->function to NULL in timeout handler.
* The same hrtimer object is activated multiple times by i915(4), so we
mustn't clear timer->function in the timeout handler.
* This seems to fix the powersaving issues in i915(4) from the update to
Linux 4.7.10 code in 8621f4070e7cb342161183c980ae7fce2fd8124e.
show more ...
|
|
Revision tags: v4.8.0, v4.6.2 |
|
| #
5915b712 |
| 15-Mar-2017 |
François Tigeot <ftigeot@wolfpond.org> |
drm/linux: Implement hrtimers
This initial implementation is based on callouts and not
highly precise.
It nevertheless works fine with the drm/i915 driver from
Linux 4.7 and will be enough for now.
|