diff options
author | Janusz Krzysztofik <jmkrzyszt@gmail.com> | 2018-09-29 14:20:22 +0200 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2018-10-01 11:35:37 +0200 |
commit | 799d5eb4e7aede8ddfcdd313eeb875f4eea860be (patch) | |
tree | 4ba9a6bbca9fad889446d422016742eba38fdc5c /Documentation/driver-api/gpio/consumer.rst | |
parent | be8c8facc707d48f367d9313f5972353d24f19be (diff) |
gpiolib: Fix incorrect use of find_next_zero_bit()
Commit b17566a6b08b ("gpiolib: Implement fast processing path in
get/set array"), already fixed to some extent with commit 5d581d7e8cdc
("gpiolib: Fix missing updates of bitmap index"), introduced a new mode
of processing bitmaps where bits applicable for fast bitmap processing
path are supposed to be skipped while iterating bits which don't apply.
Unfortunately, find_next_zero_bit() function supposed to skip over
those fast bits is always called with a 'start' argument equal to an
index of last zero bit found and returns that index value again an
again, causing an infinite loop.
Fix it by incrementing the index uncoditionally before
find_next_zero_bit() is optionally called.
Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Janusz Krzysztofik <jmkrzyszt@gmail.com>
Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'Documentation/driver-api/gpio/consumer.rst')
0 files changed, 0 insertions, 0 deletions