summaryrefslogtreecommitdiff
path: root/drivers/iio/light/lm3533-als.c
diff options
context:
space:
mode:
authorAlexandru Ardelean <alexandru.ardelean@analog.com>2020-06-03 14:40:22 +0300
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2020-06-14 13:50:02 +0300
commit2c9d8e1a6220ec1f0a7356d76926cc9feaf9d352 (patch)
tree45061bca03ed6314d6584c7789a408a242949aca /drivers/iio/light/lm3533-als.c
parent2cbd54129fddd6ce943d327eb22895d7ce93ce76 (diff)
downloadlinux-2c9d8e1a6220ec1f0a7356d76926cc9feaf9d352.tar.xz
iio: light: lm3533-als: use iio_device_set_parent() to assign parent
This assignment is the more peculiar as it assigns the parent of the platform-device's device (i.e. pdev->dev.parent) as the IIO device's parent. Since the devm_iio_device_alloc() [now] assigns the device argument as the default parent (and since this is the more common case), for cases where the parent needs to be different, the iio_device_set_parent helper should be used. That makes things a bit more obvious about the new behavior of devm_iio_device_alloc() and makes it clearer that iio_device_set_parent() should be used. Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/light/lm3533-als.c')
-rw-r--r--drivers/iio/light/lm3533-als.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/iio/light/lm3533-als.c b/drivers/iio/light/lm3533-als.c
index bc196c212881..8a621244dd01 100644
--- a/drivers/iio/light/lm3533-als.c
+++ b/drivers/iio/light/lm3533-als.c
@@ -852,7 +852,7 @@ static int lm3533_als_probe(struct platform_device *pdev)
indio_dev->channels = lm3533_als_channels;
indio_dev->num_channels = ARRAY_SIZE(lm3533_als_channels);
indio_dev->name = dev_name(&pdev->dev);
- indio_dev->dev.parent = pdev->dev.parent;
+ iio_device_set_parent(indio_dev, pdev->dev.parent);
indio_dev->modes = INDIO_DIRECT_MODE;
als = iio_priv(indio_dev);