The I2C driver makes a gpio_request during initialization. This request
happens again on resume and fails due to the earlier successful request.
Re-factor the code to only initialize the gpios during probe.

Errors on resume without this:
[   16.020000] s3c-i2c s3c2440-i2c.0: gpio [42] request failed
[   16.020000] s3c-i2c s3c2440-i2c.1: gpio [44] request failed
[   16.020000] s3c-i2c s3c2440-i2c.2: gpio [6] request failed

Signed-off-by: Abhilash Kesavan <[email protected]>
---
Changes from v1:
Refactor code to initialize gpios only during probe
Changes from v2:
Split an unrelated bug fix
Removed the new function added in v1

 drivers/i2c/busses/i2c-s3c2410.c |   16 +++++++++-------
 1 files changed, 9 insertions(+), 7 deletions(-)

diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-s3c2410.c
index 081e261..dea4cb2 100644
--- a/drivers/i2c/busses/i2c-s3c2410.c
+++ b/drivers/i2c/busses/i2c-s3c2410.c
@@ -907,13 +907,6 @@ static int s3c24xx_i2c_init(struct s3c24xx_i2c *i2c)
 
        pdata = i2c->pdata;
 
-       /* inititalise the gpio */
-
-       if (pdata->cfg_gpio)
-               pdata->cfg_gpio(to_platform_device(i2c->dev));
-       else if (IS_ERR(i2c->pctrl) && s3c24xx_i2c_parse_dt_gpio(i2c))
-               return -EINVAL;
-
        /* write slave address */
 
        writeb(pdata->slave_addr, i2c->regs + S3C2410_IICADD);
@@ -1054,6 +1047,15 @@ static int s3c24xx_i2c_probe(struct platform_device 
*pdev)
 
        i2c->pctrl = devm_pinctrl_get_select_default(i2c->dev);
 
+       /* inititalise the i2c gpio lines */
+
+       if (i2c->pdata->cfg_gpio) {
+               i2c->pdata->cfg_gpio(to_platform_device(i2c->dev));
+       } else if (IS_ERR(i2c->pctrl) && s3c24xx_i2c_parse_dt_gpio(i2c)) {
+               ret = -EINVAL;
+               goto err_clk;
+       }
+
        /* initialise the i2c controller */
 
        ret = s3c24xx_i2c_init(i2c);
-- 
1.6.6.1

--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to