diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2023-01-22 22:48:13 +0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@kernel.org> | 2023-02-08 10:07:15 +0300 |
| commit | cb90b196647282fc197804d680ad9d86889e27e4 (patch) | |
| tree | 33eed86cbdd1e437f9b051c21ebb53e6b68df9d7 /tools/perf/scripts/python/arm-cs-trace-disasm.py | |
| parent | edcb14e5139b09d2e2dc9e9bcf4c1bbdd4ad2e7c (diff) | |
| download | linux-cb90b196647282fc197804d680ad9d86889e27e4.tar.xz | |
media: atomisp: Put sensor ACPI devices in D3 before disable ACPI power-resources
The device core will call ACPI to turn the device (i2c_client) for a sensor
on / put it in D0 before calling its probe() method.
This takes a reference on all of the ACPI power-resources belonging to
the device. Since the atomisp_gmin_platform code disables ACPI
power-resource management and does its own pm, this reference never gets
released.
This is a problem for ACPI power-resources which are shared with other
devices since those now never get turned off again (nor back on again).
Explicitly put the device in D3 before disabling the ACPI power-resource
management.
Note that atomisp_register_i2c_module() runs near the end of the sensor
driver's probe() function, after the driver is done with probing the hw.
So the power-resouces (the same resources as directly controlled by
the atomisp platform code) getting turned off (a second time, as they are
already off) is not a problem.
Reviewed-by: Andy Shevchenko <andy@kernel.org>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/arm-cs-trace-disasm.py')
0 files changed, 0 insertions, 0 deletions
