Documentation/acpi/gpio.md: Update implementation details
The weak functions were removed in bce7458
"acpi/acpigen.c: Remove weak gpio definition".
Change-Id: Ia6e51698d6209fbf4f59b7fbc988a1aa696e366f
Signed-off-by: Arthur Heymans <arthur@aheymans.xyz>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/58933
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
This commit is contained in:
parent
81beeae960
commit
615ab90db3
|
@ -84,15 +84,6 @@ the raw Rx gpio value.
|
||||||
|
|
||||||
## Implementation Details
|
## Implementation Details
|
||||||
|
|
||||||
ACPI library in coreboot will provide weak definitions for all the
|
|
||||||
above functions with error messages indicating that these functions
|
|
||||||
are being used. This allows drivers to conditionally make use of GPIOs
|
|
||||||
based on device-tree entries or any other config option. It is
|
|
||||||
recommended that the SoC code in coreboot should provide
|
|
||||||
implementations of all the above functions generating ACPI AML code
|
|
||||||
irrespective of them being used in any driver. This allows mainboards
|
|
||||||
to use any drivers and take advantage of this common infrastructure.
|
|
||||||
|
|
||||||
Platforms are restricted to using Local5, Local6 and Local7 variables
|
Platforms are restricted to using Local5, Local6 and Local7 variables
|
||||||
only in implementations of the above functions. Any AML methods called
|
only in implementations of the above functions. Any AML methods called
|
||||||
by the above functions do not have any such restrictions on use of
|
by the above functions do not have any such restrictions on use of
|
||||||
|
|
Loading…
Reference in New Issue