starfive-tech/linux.git/drivers/media/i2c/ccs, branch visionfive

media: Remove redundant pm_runtime_mark_last_busy() calls

2025-08-18T07:55:08+00:00

pm_runtime_put_autosuspend(), pm_runtime_put_sync_autosuspend(), pm_runtime_autosuspend() and pm_request_autosuspend() now include a call to pm_runtime_mark_last_busy(). Remove the now-reduntant explicit call to pm_runtime_mark_last_busy(). Reviewed-by: Laurent Pinchart Acked-by: Thierry Reding (tegra-vde/h264.c) Acked-by: Tommaso Merciai (alvium-csi2.c) Reviewed-by: Dikshita Agarwal (iris_hfi_queue.c) Reviewed-by: Sean Young Acked-by: Dave Stevenson (imx219.c) Acked-by: Benjamin Mugnier Signed-off-by: Sakari Ailus Signed-off-by: Hans Verkuil

media: ccs: Don't complain about missing "clock-frequency" property

2025-04-25T08:15:34+00:00

The clock frequency is often available via the clock itself and not read by the driver from the "clock-frequency" property. Don't complain if the property doesn't exist. Signed-off-by: Sakari Ailus Signed-off-by: Hans Verkuil

media: ccs: Don't complain about lack of quirks

2025-04-25T08:15:34+00:00

Generally any deviance from the standard is handled via CCS static data nowadays and so not having quirks is expected. Don't warn about it. Signed-off-by: Sakari Ailus Signed-off-by: Hans Verkuil

media: ccs: Remove I²C write retry hack

2025-04-25T08:15:33+00:00

The I²C retry hack has been there in order to address transient I²C register write access issues on a few very old sensors and possibly it has addressed also first I²C access problems (device not responding until a certain amount of time has passed) but that is now separately handled. The retry hack has a good potential for introducing hard to debug problems in updating sensor settings while streaming. Remove it and instead pass those rare errors to the user space -- which is also what virtually all other drivers do. Signed-off-by: Sakari Ailus Signed-off-by: Hans Verkuil

media: ccs: Use read_poll_timeout() in reset polling

2025-04-25T08:15:33+00:00

Use read_poll_timeout() in polling the device after a reset, either hard or soft. While at it, improve the related error message. Signed-off-by: Sakari Ailus Signed-off-by: Hans Verkuil

media: ccs: Try a little longer to access the sensor before giving up

2025-04-25T08:15:33+00:00

Some sensors take longer to respond after reset than the spec-required time. Try up to 1 s for the sensor to become accessible. Signed-off-by: Sakari Ailus Signed-off-by: Hans Verkuil

media: ccs-pll: Drop LINK_DECOUPLED flag

2025-04-25T08:15:16+00:00

The LINK_DECOUPLED flag isn't used by the PLL calculator other than printing it. The number of OP/VT lanes are already printed in any case. Thus drop the flag as it has no function. Signed-off-by: Sakari Ailus Reviewed-by: Laurent Pinchart Signed-off-by: Hans Verkuil

media: i2c: ccs: Set the device's runtime PM status correctly in probe

2025-02-15T14:22:50+00:00

Set the device's runtime PM status to suspended in probe error paths where it was previously set to active. Fixes: 9447082ae666 ("[media] smiapp: Implement power-on and power-off sequences without runtime PM") Cc: stable@vger.kernel.org # for >= v5.15 Signed-off-by: Sakari Ailus Signed-off-by: Hans Verkuil

media: i2c: ccs: Set the device's runtime PM status correctly in remove

2025-02-15T14:22:50+00:00

Set the device's runtime PM status to suspended in device removal only if it wasn't suspended already. Fixes: 9447082ae666 ("[media] smiapp: Implement power-on and power-off sequences without runtime PM") Cc: stable@vger.kernel.org # for >= v5.15 Signed-off-by: Sakari Ailus Signed-off-by: Hans Verkuil

media: ccs: Fail the probe on CCS static data parser failure

2024-12-19T11:50:15+00:00

No need to continue probing when the CCS static data parser fails. Improve this by checking the return value and correctly exiting on failure. Signed-off-by: Mehdi Djait Signed-off-by: Sakari Ailus Signed-off-by: Mauro Carvalho Chehab