On Sat, Sep 13, 2025 at 12:41:46AM +0200, Wolfram Sang wrote:
On Wed, Aug 13, 2025 at 12:49:23PM +0300, Laurent Pinchart wrote:
quoted
Usage of the clock-frequency property for camera sensors is discouraged
in favour of using assigned-clock-rates (and assigned-clock-parents
where needed). Mark the property as deprecated.
Update the examples accordingly. In DT examples where the sensor input
clock appears to come from a programmable clock generator, replace
clock-frequency by the assigned-clocks and assigned-clock-rates
properties. Otherwise, just drop clock-frequency.
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
---
Changes since v2:
- Don't remove clocks property in samsung,exynos4212-fimc-is.yaml
Changes since v1:
- Adapt examples in bindings that reference sensors
---
Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml | 6 ++++--
Can I have this i2c change seperately to avoid dependencies?
I'm afraid it has been merged in the media tree already.
--
Regards,
Laurent Pinchart