On 2018-09-13 00:22, Ajay Gupta wrote: > Hi Peter, > Can we get the working set in while the issues is being debugged? I'm not the one making the decision, and I don't even know if this is going through the i2c or the usb tree? If it's going through the i2c tree you need a tag from the usb people (Greg?) on patch 2/2, and if it's going through the usb tree, you need a tag from Wolfram on patch 1/2. As I said, I'm not involved with that part, I'm just reviewing these patches because I felt like it. The remaining issue that bothers me is the looping reads, and your email address reveals that you should be in a very good position to work out why they do not work, and fix it or let us know why they don't. However, your responses indicate that you have given up. That coupled with the fact that the datasheet is not publicly available (but why, seems a little over-protective to think the interface to an i2c controller is worth all that much) makes me think that perhaps this little detail might never be fixed if it's not fixed now. Once merged, there is no pressure on you to actually do anything about it, and others are stuck in darkness without a spec. > So I assume nothing more left to check on this for now. Have you hooked up a scope to the I2C bus while trying the various attempts to get looping reads working? What makes a difference? Have you talked to the hardware people and described what you have attempted? Maybe they know what is missing? Can the datasheet be made public so that someone with more passion can take a crack at it? Cheers, Peter
