diff options
| author |   jcs <jcs@openbsd.org> | 2019-07-31 16:04:16 +0000 |
|---|---|---|
| committer | jcs <jcs@openbsd.org> | 2019-07-31 16:04:16 +0000 |
| commit | 1f51046f99d3ae3af9939adb7c7bcd011c7a3d22 (patch) | |
| tree | 4ba9b9126a0978edbc06f62a688e94aeddd4f621 /sys/dev/i2c | |
| parent | aml_find_node: perform callback on matched direct-child nodes before (diff) | |
| download | wireguard-openbsd-1f51046f99d3ae3af9939adb7c7bcd011c7a3d22.tar.xz wireguard-openbsd-1f51046f99d3ae3af9939adb7c7bcd011c7a3d22.zip | |
dwiic: stop enabling polling by default
The interrupt problem had nothing to do with changes in the Intel
100 Series and was due to most of these machines using the same DSDT
template where we were walking _INI nodes in the wrong order.
This lead to the touchpad device's _INI method being called before
\_SB_.PCI0._INI (where \OSYS is initialized), making the touchpad
device's interrupts setup for an OSYS of 0, but when its _CRS method
was called later during ihidev attachment (after \_SB_.PCI0._INI was
executed, modifying OSYS), it returned information for interrupts as
if were initially setup for the proper OSYS.
Diffstat (limited to 'sys/dev/i2c')
0 files changed, 0 insertions, 0 deletions