diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2022-11-27 01:02:49 +0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@kernel.org> | 2023-02-08 09:58:10 +0300 |
| commit | 553a64b7e7cef7690203bb07bd0280dd142c1015 (patch) | |
| tree | d4786efeb91f1c549a653ffc49bd4e64c9b75370 /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | 21b86873711be1aa019ee8991c293efd09c022fd (diff) | |
| download | linux-553a64b7e7cef7690203bb07bd0280dd142c1015.tar.xz | |
media: atomisp: Move power-management over to a custom pm-domain
The atomisp does not use standard PCI power-management through the
PCI config space. Instead this driver directly tells the P-Unit to
disable the ISP over the IOSF. The standard PCI subsystem pm_ops will
try to access the config space before (resume) / after (suspend) this
driver has turned the ISP on / off, resulting in the following errors:
Unable to change power state from D0 to D3hot, device inaccessible
Unable to change power state from D3cold to D0, device inaccessible
Getting logged into dmesg a whole bunch of time during boot as well as
every time the camera is used.
To avoid these errors use a custom pm_domain instead of standard driver
pm-callbacks so that all the PCI subsys suspend / resume handling is
skipped and call pci_save_state() / pci_restore_state() ourselves.
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/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions