diff options
| author | Sanjay Chitroda <sanjayembeddedse@gmail.com> | 2026-07-10 10:55:23 +0530 |
|---|---|---|
| committer | Sakari Ailus <sakari.ailus@linux.intel.com> | 2026-07-15 11:13:55 +0300 |
| commit | 15b8b49933507c9f437af51c2da626dc5840ef26 (patch) | |
| tree | d53c959c22bdd148c39c2060ebbfd06a41784ac4 /tools/perf/scripts/python/bin | |
| parent | 95a99456ff354a1bad4b4032ed1d044d608bd438 (diff) | |
media: i2c: gc0310: Use devm_v4l2_sensor_clk_get()
Several camera sensor drivers access the "clock-frequency" property
directly to retrieve the external clock rate or handle the external
clock manually in the driver. While this is valid on a subset of ACPI
platforms, implementing this logic directly in drivers is deprecated
and can lead to inconsistent behaviour across drivers.
This driver supports ACPI platforms only. It currently retrieves the
external clock rate from the "clock-frequency" property and fails
probing if the rate does not match the expected value, which is the
correct policy for ACPI platforms.
Switch to using the devm_v4l2_sensor_clk_get() helper to standardise
clock handling. This preserves the existing behaviour on ACPI
platforms that specify a clock-frequency property without providing
a clock. On platforms that provide a clock, the helper will program
the clock to the rate specified by clock-frequency, which is also
consistent with the driver's expectations.
Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
Signed-off-by: Sanjay Chitroda <sanjayembeddedse@gmail.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions
