[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1454491848-26551-5-git-send-email-ldewangan@nvidia.com>
Date: Wed, 3 Feb 2016 15:00:47 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: <lee.jones@...aro.org>, <alexandre.belloni@...e-electrons.com>,
<k.kozlowski@...sung.com>, <javier@....samsung.com>
CC: <cw00.choi@...sung.com>, <linux-kernel@...r.kernel.org>,
<rtc-linux@...glegroups.com>,
Laxman Dewangan <ldewangan@...dia.com>
Subject: [PATCH V2 4/5] mfd: max77686: do not set i2c client data for rtc i2c client
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 need to get any data from this rtc i2c client,
it is not required to set client data for this i2c client.
Suggested-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>
Signed-off-by: Laxman Dewangan <ldewangan@...dia.com>
CC: Krzysztof Kozlowski <k.kozlowski@...sung.com>
CC: Javier Martinez Canillas <javier@....samsung.com>
---
This is new in this series based on review comment from V1.
drivers/mfd/max77686.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mfd/max77686.c b/drivers/mfd/max77686.c
index d959ebb..bda6fd7 100644
--- a/drivers/mfd/max77686.c
+++ b/drivers/mfd/max77686.c
@@ -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,
--
2.1.4
Powered by blists - more mailing lists