diff options
| author | Tomoya MORINAGA <tomoya.rohm@gmail.com> | 2012-03-26 14:55:25 +0900 |
|---|---|---|
| committer | Wolfram Sang <w.sang@pengutronix.de> | 2012-04-22 21:29:06 +0200 |
| commit | 8a52f9f347da721b199b7f9dcc0168bbe7d0baae (patch) | |
| tree | 4233566199e319b6c6c6d18e14c9dc36244e1dd5 /drivers/i2c | |
| parent | f70893d08338b9cab8008d2e30404ce58930a513 (diff) | |
| download | linux-stable-8a52f9f347da721b199b7f9dcc0168bbe7d0baae.tar.gz linux-stable-8a52f9f347da721b199b7f9dcc0168bbe7d0baae.tar.bz2 linux-stable-8a52f9f347da721b199b7f9dcc0168bbe7d0baae.zip | |
i2c-eg20t: change timeout value 50msec to 1000msec
Currently, during i2c works alone, wait-event timeout is not occurred.
However, as CPU load increases, timeout occurs frequently.
So, I modified like this patch.
Modifying like this patch, I've never seen the timeout event with high
load test.
Signed-off-by: Tomoya MORINAGA <tomoya.rohm@gmail.com>
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Diffstat (limited to 'drivers/i2c')
| -rw-r--r-- | drivers/i2c/busses/i2c-eg20t.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/i2c/busses/i2c-eg20t.c b/drivers/i2c/busses/i2c-eg20t.c index f086131cb1c7..4a46c8b18188 100644 --- a/drivers/i2c/busses/i2c-eg20t.c +++ b/drivers/i2c/busses/i2c-eg20t.c @@ -324,7 +324,7 @@ static s32 pch_i2c_wait_for_xfer_complete(struct i2c_algo_pch_data *adap) { long ret; ret = wait_event_timeout(pch_event, - (adap->pch_event_flag != 0), msecs_to_jiffies(50)); + (adap->pch_event_flag != 0), msecs_to_jiffies(1000)); if (ret == 0) { pch_err(adap, "timeout: %x\n", adap->pch_event_flag); |