| commit | 73159b9bd36c7b9607b740e76d609fb7b0cf2a7a | |
| author | Dave Airlie <airlied@redhat.com> | |
| Thu, 7 May 2009 12:57:24 +0000 (7 14:57 +0200) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Mon, 18 May 2009 23:34:43 +0000 (18 16:34 -0700) | ||
| tree | b4eb37fd084b1458bbb81a20d87bfb81d4e2fac7 | treesnapshot (tar.gz zip) |
| parent | a23e0b520920e6de02ceeb0f4e67a0463194f77a | commitdiff |
i2c-algo-bit: Fix timeout test
commit 0cdba07bb23cdd3e0d64357ec3d983e6b75e541f upstream
When fetching DDC using i2c algo bit, we were often seeing timeouts
before getting valid EDID on a retry. The VESA spec states 2ms is the
DDC timeout, so when this translates into 1 jiffie and we are close
to the end of the time period, it could return with a timeout less than
2ms.
Change this code to use time_after instead of time_after_eq.
Signed-off-by: Dave Airlie <airlied@redhat.com>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 0cdba07bb23cdd3e0d64357ec3d983e6b75e541f upstream
When fetching DDC using i2c algo bit, we were often seeing timeouts
before getting valid EDID on a retry. The VESA spec states 2ms is the
DDC timeout, so when this translates into 1 jiffie and we are close
to the end of the time period, it could return with a timeout less than
2ms.
Change this code to use time_after instead of time_after_eq.
Signed-off-by: Dave Airlie <airlied@redhat.com>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/i2c/algos/i2c-algo-bit.c | diffblobblamehistory |