Igor Grinberg wrote:
I don't think there is such a rule for this case, as if we "believe" the
Developer Manual, but do the opposite - we can get into trouble...
IMHO, at least we need to report a problem.
Or may be in some way reset the slave device,
if there is such an option available outside the i2c scope...
(Yeah, I know this is a crazy idea...)
Doing the oposite what the manual says is not a good idea. Let's discard
the patch for now.
From my experience, in master mode resetting the controller
does not help and if the bus is busy for too much time,
there always was a h/w problem involved.
Looks like it.
1) Well, you should check if you have a pull-up resistors on that bus.
2) Or if the slave device chip is broken, then it should be replaced.
Thanks for the hint. I try to check the HW and see if there can be done
something about it.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
