linux-stable.git/include/acpi/actypes.h, branch v4.17.2

ACPICA: Cleanup/simplify module-level code support

2018-03-18T18:29:46+00:00

This prepares the code for eventual removal of the original
style of deferred execution of the MLC.

Signed-off-by: Bob Moore 
Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki

ACPICA: adding SPDX headers

2018-03-18T18:08:05+00:00

Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki

ACPICA: Remove calling of _STA from acpi_get_object_info()

2018-03-18T17:52:00+00:00

As the documentatuon above its declaration indicates, acpi_get_object_info()
is intended for early probe usage and as such should not call any methods
which may rely on op_regions, before this commit it was also calling _STA,
which on some systems does rely on op_regions.

Calling _STA before things are ready leads to errors such as these
(under Linux, on some hardware):

[    0.123579] ACPI Error: No handler for Region [ECRM] (00000000ba9edc4c)
               [generic_serial_bus] (20170831/evregion-166)
[    0.123601] ACPI Error: Region generic_serial_bus (ID=9) has no handler
               (20170831/exfldio-299)
[    0.123618] ACPI Error: Method parse/execution failed
               \_SB.I2C1.BAT1._STA, AE_NOT_EXIST (20170831/psparse-550)

End 2015 support for the _SUB method was removed for exactly the same
reason. Removing current_status from struct acpi_device_info only has a limited
impact. Within ACPICA it is only used by 2 debug messages, both
of which are modified to no longer print it with this commit.

Outside of ACPICA, there was one user in Linux, which has been patched to
no longer use current_status in Torvald's current master.

I've not checked if free_BSD or others are using the current_status field.

Signed-off-by: Hans de Goede 
Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki

ACPICA: Events: Dispatch GPEs after enabling for the first time

2018-03-18T17:52:00+00:00

After being enabled for the first time, the GPEs may have STS bits already
set. Setting EN bits is not sufficient to trigger the GPEs again, so this
patch polls GPEs after enabling them for the first time.
This is a cleaner version on top of the "GPE clear" fix generated according
to Mika's report and Rafael's original Linux based fix. Based on Linux
commit originated from Rafael J. Wysocki, fixed by Lv Zheng.

Signed-off-by: Lv Zheng 
Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki

ACPICA: All acpica: Update copyrights to 2018

2018-02-06T09:31:20+00:00

including tool signons.

Signed-off-by: Bob Moore 
Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki

ACPICA: Add a missing pair of parentheses

2018-02-04T07:58:31+00:00

Signed-off-by: Jung-uk Kim 
Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki

ACPICA: Prefer ACPI_TO_POINTER() over ACPI_ADD_PTR()

2018-02-04T07:58:31+00:00

This is more easy to read.

Signed-off-by: Jung-uk Kim 
Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki

ACPICA: Avoid NULL pointer arithmetic

2018-02-04T07:58:31+00:00

We should not assume NULL is defined as "(void *)0" because NULL is
an implementation-defined macro.  Especially, Clang 6 complains about
it, i.e., "arithmetic on a null pointer treated as a cast from integer
to pointer is a GNU extension".

Signed-off-by: Jung-uk Kim 
Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki

ACPICA: Recognize the Windows 10 version 1607 and 1703 OSI strings

2018-01-05T00:33:23+00:00

ACPICA commit 35a4a3ea723b3066f575e63e5f0116f7ce65e713

The public Microsoft document listing recognized OSI strings [1]
shows that these two strings were introduced.
version 1607 / Anniversary Update / "Redstone 1"
version 1703 / Creators Update / "Redstone 2"

[1] http://download.microsoft.com/download/7/e/7/7e7662cf-cbea-470b-a97e-ce7ce0d98dc2/winacpi_osi.docx

Link: https://github.com/acpica/acpica/commit/35a4a3ea
Signed-off-by: Mario Limonciello 
Signed-off-by: Bob Moore 
Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki

ACPICA: Dispatcher: Introduce timeout mechanism for infinite loop detection

2017-11-27T00:20:29+00:00

ACPICA commit 9605023e7e6d1f05581502766c8cf2905bcc03d9

This patch implements a new infinite loop detection mechanism to replace
the old one, it uses acpi_os_get_timer() to limit loop execution into a
determined time slice.
This is useful in case some hardware/firmware operations really require the
AML interpreter to wait while the old mechanism could expire too fast on
recent machines.

The new mechanism converts old acpi_gbl_max_loop_iterations to store the user
configurable value for the new mechanism in order to allow users to be
still able to configure this value for acpiexec via command line. This
patch also removes wrong initilization code of acpi_gbl_max_loop_iterations
accordingly (it should have been initialized by ACPI_INIT_GLOBAL, and the
default value is also properly tuned for acpiexec). Reported by M. Foronda,
fixed by Lv Zheng.

Link: https://github.com/acpica/acpica/commit/9605023e
Link: https://bugzilla.kernel.org/show_bug.cgi?id=156501
Reported-by: M. Foronda 
Signed-off-by: Lv Zheng 
Signed-off-by: Bob Moore 
Signed-off-by: Erik Schmauss 
Signed-off-by: Rafael J. Wysocki