Searched hist:"44 ade291b77c1cff25f253782c486c0c1e7296eb" (Results 1 – 2 of 2) sorted by relevance
| /linux/Documentation/devicetree/bindings/media/i2c/ |
| H A D | ovti,ov5693.yaml | diff 44ade291b77c1cff25f253782c486c0c1e7296eb Thu Aug 17 22:26:46 CEST 2023 Rob Herring <robh@kernel.org> media: dt-bindings: Merge OV5695 into OV5693 binding
The OV5695 binding is almost the same as the OV5693 binding. The only
difference is 'clock-names' is defined for OV5695. However, the lack of
clock-names is an omission as the Linux OV5693 driver expects the same
'xvclk' clock name.
'link-frequencies' is required by OV5693, but not OV5695, so make that
conditional. Really, this shouldn't vary by device, but we're stuck with
the existing binding use.
The rockchip-isp1 binding example is missing required properties, so it
has to be updated as well.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://lore.kernel.org/r/20230817202647.2179609-1-robh@kernel.org
Signed-off-by: Rob Herring <robh@kernel.org>
|
| /linux/Documentation/devicetree/bindings/media/ |
| H A D | rockchip-isp1.yaml | diff 44ade291b77c1cff25f253782c486c0c1e7296eb Thu Aug 17 22:26:46 CEST 2023 Rob Herring <robh@kernel.org> media: dt-bindings: Merge OV5695 into OV5693 binding
The OV5695 binding is almost the same as the OV5693 binding. The only
difference is 'clock-names' is defined for OV5695. However, the lack of
clock-names is an omission as the Linux OV5693 driver expects the same
'xvclk' clock name.
'link-frequencies' is required by OV5693, but not OV5695, so make that
conditional. Really, this shouldn't vary by device, but we're stuck with
the existing binding use.
The rockchip-isp1 binding example is missing required properties, so it
has to be updated as well.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://lore.kernel.org/r/20230817202647.2179609-1-robh@kernel.org
Signed-off-by: Rob Herring <robh@kernel.org>
|