Age | Commit message (Collapse) | Author |
|
From Alex Deucher
c1af59449d80a4f642dbe64fd8be7c1ce86fc2cf in linux 5.15.y/5.15.24
6e7545ddb13416fd200e0b91c0acfd0404e2e27b in mainline linux
|
|
From Zhan Liu
a277422a8d975966de1bd3351cc6cfd8718a166d in linux 5.15.y/5.15.24
ac46d93235074a6c5d280d35771c23fd8620e7d9 in mainline linux
|
|
From Raymond Jay Golo
9696125fb3ca1660d28a0aef53bcaa1a20a02bdb in linux 5.15.y/5.15.24
d3cbc6e323c9299d10c8d2e4127c77c7d05d07b1 in mainline linux
|
|
|
|
|
|
ok deraadt@
|
|
re-creating the original (2 weeks ago) order of last-minute-disk-parking
needs a different approach, hmm.
|
|
than scheduling an acpi thread
|
|
able to react to this suitably.
|
|
attached audio device, i.e. audio0. This approach does not work well
while using additional audio devices equipped with physical volume keys
since those would only affect the volume of audio0.
Instead, correlate audio and ucc devices attached over USB in order to
adjust the volume of the correct audio device. This is done by passing a
cookie from the common point of attachment which is later used to
correlate the audio and wskbd device.
The same approach could be adopted for audio and wskbd devices attaching
on a different bus. Keep in mind that it's of importance to make use of
and increment the same global cookie identifier to avoid collisions.
Makes the volume keys on my Logitech G435 Headset do the right thing.
ok ratchov@
|
|
unused but intended to be used to correlate audio and wskbd devices.
ok ratchov@
|
|
with AML parsing outside the acpi thread, the locking-release dance
around wsdisplay_{suspend,resume} can be removed
ok kettenis
|
|
ok deraadt@
|
|
reset the MD state before bailing out. New MD function sleep_abort()
does that.
|
|
Fixes my com0 issues after zzz and ZZZ.
OK kettenis@ miod@
|
|
|
|
ok miod@
|
|
|
|
in sleep_resume(), which seems sensible for other future systems also
|
|
steps, so shuffle the MD steps to reinforce the order.
|
|
accidentally broken with the reorganization of the suspend/resume code that
was committed a few days ago.
ok deraadt@
|
|
ok claudio@ deraadt@
|
|
|
|
match the device.
ok visa@
|
|
spotted by and ok tb@, ok tobhe@
|
|
|
|
adapted from a diff by Ted Bullock
|
|
|
|
from Ted Bullock who tested on sparc64 with xvr-100
|
|
from Ted Bullock
|
|
ok deraadt@ gnezdo@
|
|
ok kettenis@
|
|
from jan@; test and OK dlg@
|
|
OK kettenis@
|
|
update_bw_bounding_box() lost in drm 5.15 update
should avoid 'SSE FP exception trap' infrequently seen on boot
with renoir and cezanne
problem reported by beck@ and claudio@
|
|
for sharing between i386 and amd64.
ok mlarkin kettenis
|
|
Microsoft decided to break with basic ACPI standards with the Go 3.
In this case, they don't expose the battery in a standard way, so
acpibat(4) needs to look for the special Microsoft hid.
From mlarkin@, ok kettenis@
|
|
ok miod@
|
|
also tested on both x86 and sparc64.
|
|
When using device trees, the ia_name field of struct i2c_attach_args
points to the first string of the device node's "compatible" array.
However, in many cases it would be preferable to use the last, most
general "compatible" entry as a device matching criterion.
Enable more flexible device matching by permitting ia_name to point to
the raw "compatible" data which is a concatenation of NUL-terminated
strings. I2C bus code will supply the data and set ia_name and
ia_namelen. I2C device drivers will use iic_is_compatible() to check
matches. This method is also backwards compatible with the old, direct
use of ia_name.
Prompted by a related patch from kettenis@.
OK kettenis@
|
|
From Mario Limonciello
8a15ac1786c92dce6ecbeb4e4c237f5f80c2c703 in linux 5.15.y/5.15.22
e55a3aea418269266d84f426b3bd70794d3389c8 in mainline linux
|
|
From Dan Carpenter
5cba71707f0a7fe19fa1feaf25a4c094876c2db1 in linux 5.15.y/5.15.22
90a3d22ff02b196d5884e111f39271a1d4ee8e3e in mainline linux
|
|
panels
From Aun-Ali Zaidi
2093ecf557e733f995c7db6df716c91c43923972 in linux 5.15.y/5.15.22
30fbce374745a9c6af93c775a5ac49a97f822fda in mainline linux
|
|
From Paul Hsieh
7ff0ed88e4eb6bd7ccd7cf422ab855032ed0528c in linux 5.15.y/5.15.22
f5fa54f45ab41cbb1f99b1208f49554132ffb207 in mainline linux
|
|
From Evan Quan
4f4c77ad5a13ac39d38cc3f1b963e85ecf9d528f in linux 5.15.y/5.15.22
3ec5586b4699cfb75cdfa09425e11d121db40773 in mainline linux
|
|
From Imre Deak
39ac3945d966168bdede467446dec45cee3382bb in linux 5.15.y/5.15.22
3c6f13ad723e7206f03bb2752b01d18202b7fc9d in mainline linux
|
|
From Ville Syrjala
d63d077fc44645d51df7e9007df87853f5c13e4c in linux 5.15.y/5.15.22
99510e1afb4863a225207146bd988064c5fd0629 in mainline linux
|
|
tested on sparc64 and x86
|
|
This splits out the MI sequencing, backing it with per-architecture helper
functions. Further steps will be neccesary because ACPI and MD are too
tightly coupled, but soon we'll be able to use this code for more architectures
(which depends on figuring out the lowest-level cpu sleeping method)
ok kettenis
|
|
iwm_wakeup() must initialize the task reference counter only if
resuming the device succeeds. Otherwise, the newstate task will
not be scheduled and hence the ref counter must remain at zero.
Problem observed by + ok kettenis@
|