7 Jan
2014
7 Jan
'14
4:02 p.m.
On Tue, Jan 7, 2014 at 10:58 AM, Grigori Goronzy greg@chown.ath.cx wrote:
On 07.01.2014 16:14, Alex Deucher wrote:
The hw i2c engines are disabled by default as the current implementation is still experimental. Print a warning when users enable it so that it's obvious when the option is enabled.
Does hardware I2C actually have any advantage in the DDC use case? AFAICT it's only transferring small amounts of data and mostly on display connect events, so not very often.
It's lower CPU usage compared to bit-banging and can generate interrupts if you want to do something else while it fetches the EDID.
Alex