summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorDmitry Torokhov <dmitry.torokhov@gmail.com>2016-10-20 02:36:19 +0300
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2016-11-08 03:24:29 +0300
commitea6aabf877d82fe10627f40069e0f3d412706a8a (patch)
tree7b9897bf407bb24e242333c436070f7348936c12 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent0f78ba96bbcf30a78224fe56f8fd72f87915afdd (diff)
downloadlinux-ea6aabf877d82fe10627f40069e0f3d412706a8a.tar.xz
Input: gpio_keys_polled - always use gpiod_get_value_cansleep
It does not matter if given GPIO may sleep or not when reading state, polling is always done in a non-atomic context, so we should always be able to simply use gpiod_get_value_cansleep(). Also let's note in the logs when we fail to read gpio state. Reviewed-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com> Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com> Acked-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions