- 19 4月, 2016 1 次提交
-
-
由 Laxman Dewangan 提交于
Use devm_mfd_add_devices() for MFD devices registration and get rid of .remove callback to remove MFD child-devices. This is done by managed device framework. CC: Ingi Kim <ingi2.kim@samsung.com> Signed-off-by: NLaxman Dewangan <ldewangan@nvidia.com> Reviewed-by: NJavier Martinez Canillas <javier@osg.samsung.com> Signed-off-by: NLee Jones <lee.jones@linaro.org>
-
- 31 10月, 2015 1 次提交
-
-
由 Ingi Kim 提交于
This patch adds rt5033-led sub device to support it. Signed-off-by: NIngi Kim <ingi2.kim@samsung.com> Signed-off-by: NLee Jones <lee.jones@linaro.org>
-
- 26 10月, 2015 1 次提交
-
-
由 Javier Martinez Canillas 提交于
The driver has a I2C device id table that is used to create the module aliases which already contains a "rt5033". So the alias is not needed. Signed-off-by: NJavier Martinez Canillas <javier@osg.samsung.com> Signed-off-by: NLee Jones <lee.jones@linaro.org>
-
- 11 8月, 2015 1 次提交
-
-
由 Javier Martinez Canillas 提交于
The I2C core always reports the MODALIAS uevent as "i2c:<client name" regardless if the driver was matched using the I2C id_table or the of_match_table. So technically there's no need for a driver to export the OF table since currently it's not used. In fact, the I2C device ID table is mandatory for I2C drivers since a i2c_device_id is passed to the driver's probe function even if the I2C core used the OF table to match the driver. And since the I2C core uses different tables, OF-only drivers needs to have duplicated data that has to be kept in sync and also the dev node compatible manufacturer prefix is stripped when reporting the MODALIAS. To avoid the above, the I2C core behavior may be changed in the future to not require an I2C device table for OF-only drivers and report the OF module alias. So, it's better to also export the OF table to prevent breaking module autoloading if that happens. Signed-off-by: NJavier Martinez Canillas <javier@osg.samsung.com> Signed-off-by: NLee Jones <lee.jones@linaro.org>
-
- 22 1月, 2015 1 次提交
-
-
由 Beomho Seo 提交于
This patch adds a new driver for Richtek RT5033 driver. RT5033 is a Multifunction device which includes battery charger, fuel gauge, flash LED current source, LDO and synchronous Buck converter. It is interfaced to host controller using I2C interface. Signed-off-by: NBeomho Seo <beomho.seo@samsung.com> Acked-by: NChanwoo Choi <cw00.choi@samsung.com> Signed-off-by: NLee Jones <lee.jones@linaro.org>
-