slippy/falco/peppy: Fix Chrome OS GPIO export in ACPI
The OIPG package needs to have >1 member to make the chromeos_acpi kernel driver do the right automagic sysfs topology creation. Additionally an "unimplemented" GPIO should be reported as 0xFF because 0 is a valid GPIO number. verify crossystem on slippy $ sudo crossystem | grep -e recoverysw_cur -e wpsw_cur recoverysw_cur = (error) wpsw_cur = 1 Change-Id: I06dff09152bde30a3ffe58b1defe9d299155472c Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/57471 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/4221 Tested-by: build bot (Jenkins) Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
This commit is contained in:
parent
6a805905cb
commit
f9da70618e
|
@ -18,7 +18,6 @@
|
|||
*/
|
||||
|
||||
Name(OIPG, Package() {
|
||||
// This GPIO is not available but the package cannot be empty
|
||||
Package () { 0x0001, 0, 0, "LynxPoint" }, // recovery
|
||||
Package () { 0x0001, 0, 0xFFFFFFFF, "LynxPoint" }, // no recovery button
|
||||
Package () { 0x0003, 1, 58, "LynxPoint" }, // firmware write protect
|
||||
})
|
||||
|
|
|
@ -18,7 +18,6 @@
|
|||
*/
|
||||
|
||||
Name(OIPG, Package() {
|
||||
// This GPIO is not available but the package cannot be empty
|
||||
Package () { 0x0001, 0, 0, "LynxPoint" }, // recovery
|
||||
Package () { 0x0001, 0, 0xFFFFFFFF, "LynxPoint" }, // no recovery button
|
||||
Package () { 0x0003, 1, 58, "LynxPoint" }, // firmware write protect
|
||||
})
|
||||
|
|
|
@ -18,7 +18,6 @@
|
|||
*/
|
||||
|
||||
Name(OIPG, Package() {
|
||||
// This GPIO is not available but the package cannot be empty
|
||||
Package () { 0x0001, 0, 0, "LynxPoint" }, // recovery
|
||||
Package () { 0x0001, 0, 0xFFFFFFFF, "LynxPoint" }, // no recovery button
|
||||
Package () { 0x0003, 1, 58, "LynxPoint" }, // firmware write protect
|
||||
})
|
||||
|
|
Loading…
Reference in New Issue