On 11/12/2022 19:21, Laurent Pinchart wrote:
I missed one issue.
On Sun, Dec 11, 2022 at 07:13:10PM +0200, Laurent Pinchart wrote:
Hi Tomi,
Thank you for the patch.
On Thu, Dec 08, 2022 at 12:40:01PM +0200, Tomi Valkeinen wrote:
Add DT bindings for TI DS90UB913 FPDLink-3 Serializer.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@xxxxxxxxxxxxxxxx>
---
.../bindings/media/i2c/ti,ds90ub913.yaml | 121 ++++++++++++++++++
1 file changed, 121 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ti,ds90ub913.yaml
diff --git a/Documentation/devicetree/bindings/media/i2c/ti,ds90ub913.yaml b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub913.yaml
new file mode 100644
index 000000000000..3a5b34c6bb64
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub913.yaml
@@ -0,0 +1,121 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/media/i2c/ti,ds90ub913.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Texas Instruments DS90UB913 FPD-Link 3 Serializer
I think TI consistently writes it "FPD-Link III". If you rename it,
please do so through the whole series.
+
+maintainers:
+ - Tomi Valkeinen <tomi.valkeinen@xxxxxxxxxxxxxxxx>
+
+description:
+ The TI DS90UB913 is an FPD-Link 3 video serializer for parallel video.
+
+properties:
+ compatible:
+ enum:
+ - ti,ds90ub913a-q1
Is the -q1 suffix needed, are there other variants ?
+
+ '#gpio-cells':
+ const: 2
+
+ gpio-controller: true
+
+ clocks:
+ maxItems: 1
+ description:
+ Reference clock connected to the CLKIN pin.
+
+ clock-names:
+ items:
+ - const: clkin
+
+ '#clock-cells':
+ const: 0
+
+ ports:
+ $ref: /schemas/graph.yaml#/properties/ports
+
+ properties:
+ port@0:
+ $ref: /schemas/graph.yaml#/$defs/port-base
+ unevaluatedProperties: false
+ description: CSI-2 input port
This should be "Parallel input port".
Oops...
+
+ properties:
+ endpoint:
+ $ref: /schemas/media/video-interfaces.yaml#
+ unevaluatedProperties: false
Should at least the bus-width property be mandatory, as the device
supports both 10- and 12-bit inputs ?
Hmm... It supports 10-bit, 12-bit HF and 12-bit LF modes. If we need to
configure the mode based on DT, we need one more property for the HF/LF.
Then again, the HF/LF is separate from the input port, it's more about
internal operation and the link to the deserializer.
However, this (the mode) should always be set in the HW via the MODE
pins. And the driver can read the HW's MODE from the registers. Only in
some very odd circumstances should the mode be configured by hand (and
then carefully, as the link to the deserializer will drop).
So the bus-width is not something that the driver would normally use. If
we would need to define the bus-width and HF/LF in the DT for some
reason in the future, I think an "old" DT without those specified should
continue working fine, as the mode can be read from a register.
That said, to complicate matters, the deserializer needs to know the
serializer's mode before it can communicate with it (and thus, before we
can read the mode). This is set with the deserializer's "ti,rx-mode"
property, where you find RAW10, RAW12LF and RAW12HF modes (and for
ub953, CSI-2 sync and non-sync modes).
So if we would define the bus-width and HF/LF in ub913's properties, the
deserializer could go peeking the mode from there. But is that a good
idea... I'm not so sure.
Tomi
