Home
last modified time | relevance | path

Searched refs:Block (Results 1 – 3 of 3) sorted by relevance

/third_party/lib/acpica/source/tools/examples/
A Dextables.c316 [0004] PM1A Event Block Address : 00000001
317 [0004] PM1B Event Block Address : 00000000
318 [0004] PM1A Control Block Address : 00000001
319 [0004] PM1B Control Block Address : 00000000
320 [0004] PM2 Control Block Address : 00000001
324 [0001] PM1 Event Block Length : 04
325 [0001] PM1 Control Block Length : 02
326 [0001] PM2 Control Block Length : 01
327 [0001] PM Timer Block Length : 04
328 [0001] GPE0 Block Length : 08
[all …]
/third_party/lib/acpica/source/components/debugger/
A Ddbdisply.c829 UINT32 Block = 0; in AcpiDbDisplayGpes() local
841 Block = 0; in AcpiDbDisplayGpes()
869 Block, GpeBlock, GpeBlock->Node, Buffer, GpeType); in AcpiDbDisplayGpes()
998 Block++; in AcpiDbDisplayGpes()
/third_party/lib/acpica/
A Dchanges.txt2098 FADT-defined GPE0 and GPE1). For GPE0, GPE1, and each GPE Block Device,
5118 including FADT-based and GPE Block Devices, execute any _PRW methods in
5122 immediately enabled. Handles the FADT-defined GPEs as well as GPE Block
12740 The GPE Block Device support has been completed. New interfaces
12744 Events (GPEs) in order to support GPE Block Devices properly.
12774 in preparation for support of GPE Block Devices (ID ACPI0006).
12783 isn't very clear. The full 256 Block 0/1 GPEs are now supported

Completed in 22 milliseconds