Age | Commit message (Collapse) | Author |
|
|
|
feedback and ok tb@ jmc@ ok ratchov@
|
|
|
|
a _HID. Should fix the issues with broken AML that Janne Johansson reported.
This issue should be fixed in a more generic way, but that is too risky for
the upcoming release.
tested by jmc@
ok deraadt@
|
|
after Device() ones, since we should prefer the newer node type.
If we see any Device() nodes, don't attach acpicpu(4) to any Processor()
nodes if they're also present. This also makes acpitz(4) and
acpipwrres(4) devices attach slightly later.
ok kettenis@, also tested by jmc@
|
|
ok jmatthew@
|
|
the ci_acpicpudev pointer in struct cpu_info. This simplifies matters
when we have lots of cpus.
ok kettenis@
|
|
no functional change as clflush is currently only done on Intel
|
|
|
|
are showing up with vendor 2 and it doesn't seem to mean anything: Linux
doesn't check it at all, so this exhibits all the normal ACPI spec lossage
tested in snaps for a few weeks
shrug kettenis@
|
|
ok mpi@, jung@, krw@, deraadt@
|
|
mwait info against CPUID is wrong; loosen the test per Intel's suggestion.
While here, fix the wrapping of dmesg lines when reporting bogus C-state
info.
ok mlarkin@ kettenis@ (who pointed out the email from Intel)
|
|
ok mlarkin
|
|
From Anton Lindqvist (anton.lindqvist(at)gmail.com)
|
|
when acpicpu tries to attach, leading to a NULL dereference. The ACPI
processor object on the Dells where this was reported is bogus and useless
anyway so apply the same test when deciding whether to attach to processor
objects as acpicpu would when matching them to cpus.
Problem reported by Eivind Eide (xenofil (at) gmail.com) and
Johan Huldtgren (johan+openbsd-bugs (at) huldtgren.com).
Testing by Eivind Eide.
ok kettenis@ mlarkin@
|
|
and improve the output for those we might.
output examples from mikeb@
ok kettenis@
|
|
The second argument of aml_showvalue() was probably supposed to set
the verbosity level through dnprintf() but in fact it does nothing.
OK deraadt@
|
|
acpicpu(4) drivers to the right cpu(4).
ok mlarkin@, guenther@
|
|
our own.
From Michal Mazurek, ok mmcc@
|
|
ACPI specs. With the correct value, it can now be used in a few places
instead of hardcoding 0x79.
ok kettenis@
|
|
ok tb@
|
|
would need to be freed in a couple other places
with deraadt
|
|
when all cores are in C3, so treat the latency+power values from ACPI as
advisory and stop skipping states based on them.
ok mlarkin@ kettenis@
|
|
ok millert@ kettenis@ and something like an ok mlarkin@
|
|
problem reported by patrick keshishian (pkeshish (at) gmail.com)
based on diff from mlarkin@, ok mlarkin@ deraadt@
|
|
repeat this action at resume time.
ok mlarkin guenther
|
|
Fixed systems that only provide _CST for a subset of the CPUs.
Problem reported by <david.a.baer (at) gmail.com>
ok mlarkin@ deraadt@
|
|
fallback C1 state using 'halt'
tested in snaps for a bit
problem laptops noted by and oks okan@ and kettenis@
|
|
testing by many, particularly krw@ and jcs@
tweaks by kettenis@
ok deraadt@
|
|
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.
ok tedu@ deraadt@
|
|
ok tedu@ deraadt@
|
|
ok mpi@ kspillner@
|
|
after discussions with beck deraadt kettenis.
|
|
and specifyig the wrong DWORD count. Moreover we should not evaluate _PDC
if _OSC is present. Might not be perfect yet, but what we had previously
was uterrly and totally wrong.
ok guenther@
|
|
(used only when ACPI_DEBUG is enabled)
From a diff on tech@ by Fabian Raetz, with a minor change by me, tested
on i386 and amd64 with ACPI_DEBUG enabled and disabled.
|
|
|
|
|
|
a problem after we started striking entires for containing
junk and /* should never happen */ happened.
Fixes PR 6175 confirmed by submiter: nick templeton nick @ nicktempleton.com
ok marco@
|
|
PDC (which tells the ACPI code what we as OSPM are capable of) we also evaluate
the OSC method on the acpicpu device. Original cause of problems that resulted
in this getting backed out appear to be fixed by the mp_setperf change, so
hopefully the third time is the charm. Tested by many.
ok marco@
|
|
hanging machines. backed out correctly this time, as pointed out by tedu.
|
|
backout of. COME ON. Be exact in your commit messages.
|
|
|
|
directly, we must call the global function pointer cpu_setperf because
we might be on an MP system and if we don't, we only attempt to change
the frequency on a single core.
ok marco@
|
|
powernow drivers if the _PPC is evaluated because an external
change has occured such as being disconnected from wall power
and the available states in _PSS change. Have the acpicpu setperf
driver register a listner for _PPC changes, that way we are not
calling the setperf method twice on powernow machines when an
change occurs.
ok marco@
|
|
from ACPI for est on amd64. This incorporates a few changes from krw@
to fix minor nits, its unlikely to fix the problems with some machines
from acer and dell but lots of machines benefit.
ok krw@
|
|
|
|
the intended meaning.
|
|
on amd64.
Evaluating the _PDC seems to lead to instability (PR5878 and a report by
jmc@) on lower end machines its too close to release and I don't have
enough nickels.
ok deraadt@
|
|
operating points from ACPI. In support of this add evaluation of the _PDC
object and give it the capability flags asserting OSPM management of CPU
power states.
ok marco@, canacar@
|
|
now too.
ok kettenis deraadt
|