aboutsummaryrefslogtreecommitdiff
path: root/LOCKS
diff options
context:
space:
mode:
authorAndriy Gapon <avg@FreeBSD.org>2020-07-21 07:35:03 +0000
committerAndriy Gapon <avg@FreeBSD.org>2020-07-21 07:35:03 +0000
commite57f9c8a9f9b9dc233428d2f86d71d9c2e6b62eb (patch)
treed6beb0036795d8e65e652e2a163d11bddcfe4776 /LOCKS
parentc4cbf1fbabcb84d9d0a49c2444ed398ed9907df5 (diff)
downloadsrc-e57f9c8a9f9b9dc233428d2f86d71d9c2e6b62eb.tar.gz
src-e57f9c8a9f9b9dc233428d2f86d71d9c2e6b62eb.zip
gpioiic: never drive lines active high
I2C communication is done by a combination of driving a line low or letting it float, so that it is either pulled up or driven low by another party. r355276 besides the stated goal of the change -- using the new GPIO API -- also changed the logic, so that active state is signaled by actively driving a line. That worked with iicbb prior to r362042, but stopped working after that commit on at least some hardware. My guess that the breakage was related to getting an ACK bit. A device expected to be able to drive SDA actively low, but controller was actively driving it high for some time. Anyway, this change seems to fix the problem. Tested using gpioiic on Orange Pi PC Plus with HTU21 sensor. Reported by: Nick Kostirya <nikolay.kostirya@i11.co> Reviewed by: manu MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D25684
Notes
Notes: svn path=/head/; revision=363382
Diffstat (limited to 'LOCKS')
0 files changed, 0 insertions, 0 deletions