diff options
author | Petr Štetiar <ynezz@true.cz> | 2018-12-11 23:02:04 +0100 |
---|---|---|
committer | John Crispin <john@phrozen.org> | 2018-12-17 08:05:03 +0100 |
commit | d9753f0ec58429c9b9aa92918ff736004e4ca0d0 (patch) | |
tree | 50d1ef963d7561732d65b94c25ab6c72c4fb0364 /target/linux/ramips | |
parent | 7bd2595b6761a52cb69b58b9be1a84d25cbe66e3 (diff) | |
download | upstream-d9753f0ec58429c9b9aa92918ff736004e4ca0d0.tar.gz upstream-d9753f0ec58429c9b9aa92918ff736004e4ca0d0.tar.bz2 upstream-d9753f0ec58429c9b9aa92918ff736004e4ca0d0.zip |
ath79, brcm63xx: Fix debounce-interval properties in gpio-keys-polled nodes
This patch fixes wrong usage of debounce-interval subnode property of
gpio-keys-polled nodes, which was used inproperly in parent node, but it
belongs to the subnodes, excerpt from the docs:
Optional subnode-properties:
- debounce-interval: Debouncing interval time in milliseconds.
If not specified defaults to 5.
And the docs are up to date as the source code matches that description
as well:
if (fwnode_property_read_u32(child, "debounce-interval",
&button->debounce_interval))
button->debounce_interval = 5;
While at it, I've also re-formatted gpio-keys-polled nodes, usually just
adding new lines after every key subnode.
Cc: Tomasz Maciej Nowak <tomek_n@o2.pl>
Cc: Matt Merhar <mattmerhar@protonmail.com>
Cc: Jonas Gorski <jonas.gorski@gmail.com>
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Diffstat (limited to 'target/linux/ramips')
0 files changed, 0 insertions, 0 deletions