Commit 0d6c41cf authored by Andy Shevchenko's avatar Andy Shevchenko Committed by Rafael J. Wysocki
Browse files

Documentation: firmware-guide: gpio-properties: active_low only for GpioIo() 



It appears that people may misinterpret active_low field in _DSD
for GpioInt() resource. Add a paragraph to clarify this.

Reported-by: default avatarRicardo Ribalda <ribalda@chromium.org>
Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: default avatarMika Westerberg <mika.westerberg@linux.intel.com>
Reviewed-by: default avatarRicardo Ribalda <ribalda@chromium.org>
Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
parent 1bd33879

Documentation/firmware-guide/acpi/gpio-properties.rst

+3 −0
Original line number Diff line number Diff line
@@ -55,6 +55,9 @@ Since ACPI GpioIo() resource does not have a field saying whether it is 
active low or high, the "active_low" argument can be used here.  Setting

it to 1 marks the GPIO as active low.



Note, active_low in _DSD does not make sense for GpioInt() resource and

must be 0. GpioInt() resource has its own means of defining it.



In our Bluetooth example the "reset-gpios" refers to the second GpioIo()

resource, second pin in that resource with the GPIO number of 31.