Hi, Shu-hsiang: On Wed, 2024-10-09 at 19:15 +0800, Shu-hsiang Yang wrote: > 1. Add camera isp7x module device document > 2. Add camera interface device document > > Signed-off-by: Shu-hsiang Yang <Shu-hsiang.Yang@xxxxxxxxxxxx> > --- [snip] > diff --git a/Documentation/devicetree/bindings/media/mediatek/mediatek,seninf.yaml b/Documentation/devicetree/bindings/media/mediatek/mediatek,seninf.yaml > new file mode 100644 > index 000000000000..37d94138c558 > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/mediatek/mediatek,seninf.yaml > @@ -0,0 +1,88 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +# Copyright (c) 2024 MediaTek Inc. > + > +%YAML 1.2 > +--- > +$id: https://urldefense.com/v3/__http://devicetree.org/schemas/media/mediatek/mediatek,seninf.yaml*__;Iw!!CTRNKA9wMg0ARbw!jkHmqtxOst6Dv88RaE-ss9VaxKxFo4FuPl1smXTEnkiijU7jS9nkYGBPoLr8g4Ji2dZpb_7LHWrLpIyu2qoPVkLta9M$ > +$schema: https://urldefense.com/v3/__http://devicetree.org/meta-schemas/core.yaml*__;Iw!!CTRNKA9wMg0ARbw!jkHmqtxOst6Dv88RaE-ss9VaxKxFo4FuPl1smXTEnkiijU7jS9nkYGBPoLr8g4Ji2dZpb_7LHWrLpIyu2qoPfKVBdTw$ > + > +title: The seninf unit of MediaTek ISP system > + > +maintainers: > + - Shu-hsiang Yang <shu-hsiang.yang@xxxxxxxxxxxx> > + - Shun-yi Wang <shun-yi.wang@xxxxxxxxxxxx> > + - Teddy Chen <teddy.chen@xxxxxxxxxxxx> > + > +description: > + MediaTek seninf is the MIPI-CSI2 port for seninf-core in MediaTek SoC. > + These ports provide the optional capability to define endpoints and set RX > + controller for camera sensors. > + > +properties: > + compatible: > + const: mediatek,seninf > + > + csi-port: > + description: MediaTek CSI Rx port name > + $ref: /schemas/types.yaml#/definitions/string > + > + port: > + description: > + MediaTek sensor interface endpoints for one sensor bus. > + $ref: /schemas/graph.yaml#/$defs/port-base > + > + properties: > + "#address-cells": > + const: 1 > + "#size-cells": > + const: 0 > + > + patternProperties: > + "^endpoint(@[0-9]+)?$": > + description: > + CSI port for one sensor endpoint configuration. > + Consider one sensor bus can support differet links for MIPI PHY. > + $ref: /schemas/media/video-interfaces.yaml# > + unevaluatedProperties: false > + properties: > + data-lanes: > + items: > + enum: [1, 2, 3, 4] > + maxItems: 4 > + > + additionalProperties: false > + > +required: > + - compatible > + - csi-port > + - port > + > +additionalProperties: false > + > +examples: > + - | > + seninf_top { > + seninf_csi_port_0: seninf_csi_port_0 { > + compatible = "mediatek,seninf"; > + csi-port = "0A"; This device has no reg property, so it's a virtual device not a real device. binding document is used to describe a real hardware device, so drop this binding document. There is another seninf device [1] which is upstreaming. Even though it's not upstreamed yet, it have been reviewed. You may take it as a reference. [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=874617 Regards, CK > + port { > + #address-cells = <1>; > + #size-cells = <0>; > + > + seninf_csi_port_0_in_1: endpoint { > + data-lanes = <1 2>; > + link-frequencies = /bits/ 64 <1440000000 624000000>; > + remote-endpoint = <&sensor0_out_1>; > + }; > + > + seninf_csi_port_0_in_2: endpoint@2 { > + reg = <2>; > + data-lanes = <1 2>; > + link-frequencies = /bits/ 64 <336000000 207000000>; > + remote-endpoint = <&sensor0_out_2>; > + }; > + }; > + }; > + }; > + > +...