OpenBSD cvs log

created 2023-07-05T07:39:15Z
begin 2023-06-29T00:00:00Z
end 2023-06-30T00:00:00Z
path src/sys
commits 3

date 2023-06-29T07:58:15Z
author jsg
files src/sys/dev/pci/pcidevs log diff annotate
message add Intel Raptor Lake / 700 Series LP ids

from:
13th Generation Intel Core Processors
Datasheet, Volume 1 of 2, Doc. No.: 743844, Rev.: 005

Intel 700 Series Chipset Family On-Package Platform Controller Hub (PCH)
Datasheet, Volume 1 of 2, Doc. No.: 763122, Rev.: 001

0xa75d (IPU) 0xa72f 0xa76e (TBT PCIE) not in tables
inferred from a dmesg and pci dev:func descriptions in
13th Generation Intel Core Processors
Datasheet, Volume 2 of 2, Doc. No.: 764981, Rev.: 1.2

date 2023-06-29T07:58:54Z
author jsg
files src/sys/dev/pci/pcidevs.h log diff annotate
src/sys/dev/pci/pcidevs_data.h log diff annotate
message regen

date 2023-06-29T20:58:08Z
author dv
files src/sys/dev/acpi/acpi.c log diff annotate
src/sys/dev/acpi/acpibtn.c log diff annotate
src/sys/dev/acpi/acpivar.h log diff annotate
message acpi(4)/acpibtn(4): use opt-in approach for wakeup GPEs

Previously, any discovered GPE that could be enabled for wake was
being enabled prior to entering ACPI-based S3 or S4. On some newer
machines, this caused S3-based suspend to break as some devices we
don't fully control (e.g. lack of driver) might be capable of waking
the system and will do so almost instantly if the GPE is enabled for
wake up (i.e. the so called "instant wake" issue).

This changes to a model of having device drivers explicitly opt
into using their GPE for wake up.

The first driver to explicitly toggle a GPE for wake is acpibtn(4).

Variations of the above have been in snapshots for 2 weeks, so
tested by many.

ok deraadt@