mfd: max77686: do not set i2c client data for rtc i2c client
authorLaxman Dewangan <[email protected]>
Tue, 9 Feb 2016 17:26:33 +0000 (22:56 +0530)
committerAlexandre Belloni <[email protected]>
Mon, 14 Mar 2016 16:08:12 +0000 (17:08 +0100)
There is different RTC I2C address for RTC block in MAX77686.
Driver is creating dummy i2c client for this address to access
the register of this IP block.

As there is no call to i2c_get_clientdata() for rtc_i2c client,
there is no need to store pointer and hence removing the call
to set client data for rtc i2c client.

Suggested-by: Krzysztof Kozlowski <[email protected]>
Signed-off-by: Laxman Dewangan <[email protected]>
Tested-by: Krzysztof Kozlowski <[email protected]>
Reviewed-by: Krzysztof Kozlowski <[email protected]>
Tested-by: Javier Martinez Canillas <[email protected]>
Reviewed-by: Javier Martinez Canillas <[email protected]>
Acked-by: Lee Jones <[email protected]>
Signed-off-by: Alexandre Belloni <[email protected]>
drivers/mfd/max77686.c

index d959ebbb2194aa29147d1201eb5e61b7d734b68c..bda6fd7b093bb2a3dddf41b86ac99b4140d70c59 100644 (file)
@@ -277,7 +277,6 @@ static int max77686_i2c_probe(struct i2c_client *i2c,
                                "Failed to allocate I2C device for RTC\n");
                        return -ENODEV;
                }
-               i2c_set_clientdata(max77686->rtc, max77686);
 
                max77686->rtc_regmap =
                        devm_regmap_init_i2c(max77686->rtc,