Changes:
- Rebase onto v5.12.14
- Add "PCI: PM: Do not read power state in pci_enable_device_flags()"
which has been reverted upstream back.
Links:
- kernel: 81416742c5
Changes:
- Rebase onto v5.10.47
- Add "PCI: PM: Do not read power state in pci_enable_device_flags()"
which has been reverted upstream back.
Links:
- kernel: 459bd42a63
Changes:
- Rebase onto v4.19.196
- Add "PCI: PM: Do not read power state in pci_enable_device_flags()"
which has been reverted upstream back.
Links:
- kernel: 9c073cfc7c
We have moved from freenode libera.chat/#linux-surface, have a new
Matrix space and are discontinuing the use of Gitter in favor of Matrix
channels in that space.
While the atomisp driver might be used for Surface 3 and Surface Pro 3
cameras in the future, it currently resides in staging and doesn't seem
to work (at least according to its TODO file). It furthermore causes
a notice to be printed, warning about the use of trace_printk(). So
disable it for now to shut up that warning.
Changes:
- SAM:
- Fix bug when disabling events.
- Add support for forwarding events to user-space via debug device.
- Work around bug preventing IRQ setup and subsequently SAM drivers from
loading on the 13" AMD Surface Laptop 4.
- Add quirk to prevent incorrect battery reporting via the Surface Go
touchscreen.
Links:
- SAM: 6b6edef7c7
- kernel: 41c3cb4084
Changes:
- SAM:
- Fix bug when disabling events.
- Add support for forwarding events to user-space via debug device.
- Work around bug preventing IRQ setup and subsequently SAM drivers from
loading on the 13" AMD Surface Laptop 4.
- Add quirk to prevent incorrect battery reporting via the Surface Go
touchscreen.
Links:
- SAM: 6b6edef7c7
- kernel: 6a938d0615
Changes:
- SAM:
- Fix bug when disabling events.
- Add support for forwarding events to user-space via debug device.
- Add quirk to prevent incorrect battery reporting via the Surface Go
touchscreen.
Links:
- SAM: 6b6edef7c7
- kernel: 1028bcec86
Currently, the kernel emits a notice at boot, warning about the usage of
trace_printk(). Disabling samples in efaa3edaaa ("Do not build samples
for Debian/Ubuntu") apparently wasn't enough to get rid of that. So
disable more sample and testing stuff that might call this function.
