wireguard-openbsd/sys/dev/acpi, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/acpi?h=jd%2Fqueueboosts 2020-06-20T18:06:22Z Shifts (<<) of more than 32 bits must be done on 64-bit values. 2020-06-20T18:06:22Z krw krw@openbsd.org 2020-06-20T18:06:22Z urn:sha1:c0937d19fbf615678794785c9dba640612a1221f COVERITY 1491295 ok kettenis@ needs param.h, not types.h 2020-06-17T16:16:05Z deraadt deraadt@openbsd.org 2020-06-17T16:16:05Z urn:sha1:e80e43fc0876077814e0cf40c04e86b34c3f7b39 Give userland a consistent battery and A/C state after resume 2020-06-10T22:26:40Z jca jca@openbsd.org 2020-06-10T22:26:40Z urn:sha1:dda5942a660d20d192f90a8468ec6b087e8662bc Previously we refreshed the state of acpiac(4) and acpibat(4)/acpisbs(4) by queueing fake ACPI events to be processed by the acpi thread. acpibat(4) using ACPIDEV_POLL meant that its status could be refreshed first, resulting in an APM_POWER_CHANGE event sent to userland before the state of acpiac(4) was up to date. Because of this, apmd(8) could see A/C unplugged when it was in fact plugged, possibly leading to a wrong decision. Instead of using fake ACPI events, refresh the status of acpiac(4) and acpibat(4)/acpisbs(4) right away at DVACT_WAKEUP time. To reuse the existing refresh code of those drivers, make their ACPI *_notify() handlers responsible for sending APM_POWER_CHANGE events instead. Also queue an APM_POWER_CHANGE event right after resume to retain existing behavior. This fixes the consistency of data shown to userland, and makes those drivers less special. Initially discussed last year (!) with mpi@ at Miod's place. Feedback and ok jcs@, deraadt@ agrees with the use of DVACT_WAKEUP here. disable debugging by default and only print unknown events when 2020-06-02T19:26:36Z jcs jcs@openbsd.org 2020-06-02T19:26:36Z urn:sha1:a2a1e6008f86f71601bca5705a08c083af49bcfc debug is enabled add acpihid(4) for ACPI HID event and 5-button array devices 2020-06-02T16:24:24Z jcs jcs@openbsd.org 2020-06-02T16:24:24Z urn:sha1:fa9d1ef83691efe74cddcecf306063709cfed905 ok kettenis dev/rndvar.h no longer has statistical interfaces (removed during various 2020-05-29T04:42:23Z deraadt deraadt@openbsd.org 2020-05-29T04:42:23Z urn:sha1:c8f27247b9f5f282483daaddbfd1267ad73569c5 conversion steps). it only contains kernel prototypes for 4 interfaces, all of which legitimately belong in sys/systm.h, which are already included by all enqueue_randomness() users. limit clflush before monitor errata workaround to Intel 2020-05-27T05:02:21Z jsg jsg@openbsd.org 2020-05-27T05:02:21Z urn:sha1:9914efbf395e5d2d4059aa7ec3dba9e5e70bfaa3 no functional change as clflush is currently only done on Intel Use the parsed address and interrupt information from 2020-05-22T10:16:37Z kettenis kettenis@openbsd.org 2020-05-22T10:16:37Z urn:sha1:9f1f78b7a13f9b43b5c02fb5e1b18bd245fb7e25 struct acpi_attach_args. tpm(4) tested by kn@ ok jmatthew@ Don't provide backlight control if the list returned by _BCL is empty. 2020-05-19T14:26:59Z kettenis kettenis@openbsd.org 2020-05-19T14:26:59Z urn:sha1:30345ed3e01fe2fb32af615930f4aa5d0c3f2702 Prevents crashes on broken AML. ok jcs@ Bring back the acpi(4) changes. This time around only use the ACPI _CRS 2020-05-14T13:07:10Z kettenis kettenis@openbsd.org 2020-05-14T13:07:10Z urn:sha1:a6e4dcfb212cd5cc293df160d767b2f1381f475a information on ACPI 5.0 and later. ok krw@, patrick@