diff options
| author |   Martin Blumenstingl <martin.blumenstingl@googlemail.com> | 2020-08-15 20:13:55 +0200 |
|---|---|---|
| committer |   Jonathan Cameron <Jonathan.Cameron@huawei.com> | 2020-08-31 10:47:52 +0100 |
| commit | d53bfdf2f0b2ec2d4bcebc4f1a1257d05f78dc51 (patch) | |
| tree | d902dac948227f09da0cfb99cf353d5e4941aa6c /drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | |
| parent | iio:adc:max1118 Fix alignment of timestamp and data leak issues (diff) | |
| download | linux-dev-d53bfdf2f0b2ec2d4bcebc4f1a1257d05f78dc51.tar.xz linux-dev-d53bfdf2f0b2ec2d4bcebc4f1a1257d05f78dc51.zip | |
iio: adc: meson-saradc: Use the parent device to look up the calib data
On the older-gen 32-bit SoCs the meson-saradc driver is used to read the
SoC temperature. This requires reading calibration data from the eFuse.
Looking up the calibration data nvmem-cell requires the OF device_node
pointer to be available in the struct device which is passed to
devm_nvmem_cell_get(). This however got lost with commit 8cb631ccbb1952
("iio: Remove superfluous of_node assignments") from indio_dev->dev. As
devm_nvmem_cell_get() is called in the initialization phase the
device_node is not yet available because the NVMEM cell is looked up
before iio_device_register() is called (which would then set the
device_node automatically).
Use the parent device to look up the NVMEM cell instead to fix this
issue.
Fixes: 8cb631ccbb1952 ("iio: Remove superfluous of_node assignments")
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_object.c')
0 files changed, 0 insertions, 0 deletions