Jason Thorpe <thor...@me.com> writes: >> On May 31, 2018, at 9:34 PM, Jason Thorpe <thor...@me.com> wrote: >> >> I spent some time reviewing NXP’s i2c spec this evening (well, during >> timeouts, etc. — GO DUBS), and I’m becoming convinced that there is a subtle >> error in our i2c_bitbang code… > > *smacks forehead* … RPI, of course, has a “smart” i2c controller. There may > be a bug in that driver. What I should do is try gpioiic to see if the > “quick read” method works there. > > Same caveat as below applies, however. > >> (Not sure I'll get to it this weekend, though… despite my kid’s spring >> soccer season being finished, I seem to have a full calendar nonetheless…) > > -- thorpej
gpioiic may have bugs too.. I could not get it to work with the am2315. Reads would not error, but no data was returned. However, the am2315 is a strange thing. However, the si70xxtemp(4) driver did work with gpioiic. -- Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
