summaryrefslogtreecommitdiff
path: root/drivers/base
diff options
context:
space:
mode:
authorMilo Kim <milo.kim@ti.com>2015-08-24 07:09:55 (GMT)
committerJacek Anaszewski <j.anaszewski@samsung.com>2015-08-28 12:06:28 (GMT)
commited133352047e46687afd98c299ec8ce7f6ea07bd (patch)
tree6b35cca71f5451782c5979106336d1321a03cc71 /drivers/base
parent991a3f61fa93c1752a47ae157a8238395850c730 (diff)
downloadlinux-ed133352047e46687afd98c299ec8ce7f6ea07bd.tar.xz
leds:lp55xx: use the private data instead of updating I2C device platform data
Currently, lp55xx_of_populate_pdata() allocates lp55xx_platform_data if it's null. And it parses the DT and copies values into the 'client->dev.platform_data'. This may have architectural issue. Platform data is configurable through the DT or I2C board info inside the platform area. However, lp55xx common driver changes this configuration when it is loaded. So 'client->dev.platform_data' is not null anymore. Eventually, the driver initialization is not identical when it's unloaded and loaded again. The lp55xx common driver should use the private data, 'lp55xx_chip->pdata' instead of changing the original platform data. So, lp55xx_of_populate_pdata() is modified as follows. * Do not update 'dev->platform_data'. Return the pointer of new allocated lp55xx_platform_data. Then the driver points it to private data, 'lp55xx_chip->pdata'. * Each lp55xx driver checks the pointer and handles an error case. Then, original platform data configuration will be kept regardless of loading or unloading the driver. The driver allocates the memory and copies them from the DT if it's NULL. After the driver is loaded again, 'client->dev.platform_data' is same as initial load, so the driver is initialized identically. Cc: Toshi Kikuchi <toshik@chromium.org> Cc: linux-leds@vger.kernel.org Signed-off-by: Milo Kim <milo.kim@ti.com> Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
Diffstat (limited to 'drivers/base')
0 files changed, 0 insertions, 0 deletions