From: Rob Herring <robh@kernel.org>
To: Louis Kuo <louis.kuo@mediatek.com>
Cc: hans.verkuil@cisco.com,
laurent.pinchart+renesas@ideasonboard.com, tfiga@chromium.org,
keiichiw@chromium.org, matthias.bgg@gmail.com,
mchehab@kernel.org, yuzhao@chromium.org, zwisler@chromium.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, Sean.Cheng@mediatek.com,
sj.huang@mediatek.com, christie.yu@mediatek.com,
frederic.chen@mediatek.com, Jerry-ch.Chen@mediatek.com,
jungo.lin@mediatek.com, linux-media@vger.kernel.org,
srv_heupstream@mediatek.com, devicetree@vger.kernel.org
Subject: Re: [RFC PATCH V6 2/3] dt-bindings: mt8183: Add sensor interface dt-bindings
Date: Mon, 20 Apr 2020 13:43:09 -0500 [thread overview]
Message-ID: <20200420184309.GA14720@bogus> (raw)
In-Reply-To: <20200410071723.19720-3-louis.kuo@mediatek.com>
On Fri, Apr 10, 2020 at 03:17:22PM +0800, Louis Kuo wrote:
> This patch adds the DT binding documentation for the sensor interface
> module in Mediatek SoCs.
checkpatch.pl reports some trailing WS.
>
> Signed-off-by: Louis Kuo <louis.kuo@mediatek.com>
> ---
> .../bindings/media/mediatek-seninf.yaml | 219 ++++++++++++++++++
> 1 file changed, 219 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/mediatek-seninf.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/mediatek-seninf.yaml b/Documentation/devicetree/bindings/media/mediatek-seninf.yaml
> new file mode 100644
> index 000000000000..c9e5776a2bd0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/mediatek-seninf.yaml
> @@ -0,0 +1,219 @@
> +# SPDX-License-Identifier: (GPL-2.0+ OR MIT)
(GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/mediatek-seninf.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Mediatek seninf MIPI-CSI2 host driver
Bindings aren't drivers.
> +
> +maintainers:
> + - Louis Kuo <louis.kuo@mediatek.com>
> +
> +description: |
> + Seninf MIPI-CSI2 host driver is a HW camera interface controller. It support
> + a widely adopted, simple, high-speed protocol primarily intended for
> + point-to-point image and video transmission between cameras and host devices.
> +
> +properties:
> + compatible:
> + const: mediatek,mt8183-seninf
> +
> + reg:
> + minItems: 2
> + items:
> + - description: The Seninf main register region
> + - description: The RX register region
> +
> + reg-names:
> + minItems: 2
Drop, implied.
> + items:
> + - const: base
> + - const: rx
> +
> + interrupts:
> + maxItems: 1
> +
> + power-domains:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: Seninf camsys clock
> + - description: Seninf top mux clock
> +
> + clock-names:
> + items:
> + - const: clk_cam_seninf
> + - const: clk_top_mux_seninf
Drop 'clk_' as it is redundant.
> +
> + # See ./video-interfaces.txt for details
> + ports:
> + type: object
> + additionalProperties: false
> +
> + properties:
> + port@0:
> + type: object
> + description: connection point for sensor at port 0
> + additionalProperties: false
> +
> + properties:
> + reg:
> + const: 0
> +
> + patternProperties:
> + endpoint:
> + type: object
> + additionalProperties: false
> +
> + properties:
> + data-lanes:
> + minItems: 1
> + maxItems: 4
> +
> + remote-endpoint: true
> +
> + port@1:
> + type: object
> + description: connection point for sensor at port 1
> + additionalProperties: false
> +
> + properties:
> + reg:
> + const: 1
> +
> + patternProperties:
> + endpoint:
> + type: object
> + additionalProperties: false
> +
> + properties:
> + data-lanes:
> + minItems: 1
> + maxItems: 4
> +
> + remote-endpoint: true
> +
> + port@4:
> + type: object
> + description: connection point for camsys
> + additionalProperties: false
> +
> + properties:
> + reg:
> + const: 4
> +
> + patternProperties:
> + endpoint:
> + type: object
> + additionalProperties: false
> +
> + properties:
> + remote-endpoint: true
> +
> + required:
> + - port@0
> + - port@1
> + - port@4
> +
> +required:
> + - compatible
> + - interrupts
> + - clocks
> + - clock-names
> + - power-domains
> + - ports
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> +
> + #include <dt-bindings/clock/mt8183-clk.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/power/mt8183-power.h>
> +
> + parent0: parent@0 {
bus {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + seninf: seninf@1a040000 {
> + compatible = "mediatek,mt8183-seninf";
> + reg = <0 0x1a040000 0 0x8000>,
> + <0 0x11c80000 0 0x6000>;
> + reg-names = "base", "rx";
> + interrupts = <GIC_SPI 251 IRQ_TYPE_LEVEL_LOW>;
> + power-domains = <&scpsys MT8183_POWER_DOMAIN_CAM>;
> + clocks = <&camsys CLK_CAM_SENINF>,
> + <&topckgen CLK_TOP_MUX_SENINF>;
> + clock-names = "clk_cam_seninf", "clk_top_mux_seninf";
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> +
> + mipi_in_bcam: endpoint {
> + data-lanes = <0 1 3 4>;
> + remote-endpoint = <&bcam_out>;
> + };
> + };
> +
> + port@1 {
> + reg = <1>;
> +
> + mipi_in_fcam: endpoint {
> + data-lanes = <1>;
> + remote-endpoint = <&fcam_out>;
> + };
> + };
> +
> + port@4 {
> + reg = <4>;
> +
> + seninf_camisp_endpoint: endpoint {
> + remote-endpoint = <&camisp_endpoint>;
> + };
> + };
> + };
> + };
> +
> + i2c2: i2c@11009000 {
This will give a warning on 5.7-rc. Add a reg property.
> + clock-frequency = <400000>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + wcam: camera@36 {
> + compatible = "ovti,ov5695";
> + reg = <0x36>;
> +
> + port {
> + bcam_out: endpoint {
> + remote-endpoint = <&mipi_in_bcam>;
> + data-lanes = <0 1 3 4>;
> + };
> + };
> + };
> + };
> +
> + i2c4: i2c@11008000 {
> + clock-frequency = <400000>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ucam: camera@3c {
> + compatible = "ovti,ov2685";
> + reg = <0x3c>;
> +
> + port {
> + fcam_out: endpoint {
> + remote-endpoint = <&mipi_in_fcam>;
> + data-lanes = <1>;
> + };
> + };
> + };
> + };
> + };
> \ No newline at end of file
Fix.
> --
> 2.18.0
next prev parent reply other threads:[~2020-04-20 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 7:17 [RFC PATCH V6 0/3] media: support Mediatek sensor interface driver Louis Kuo
2020-04-10 7:17 ` [RFC PATCH V6 1/3] media: platform: mtk-isp: Add " Louis Kuo
2020-04-11 0:16 ` Chun-Kuang Hu
[not found] ` <d6776ac432794cb593c4db54b8a7a089@mtkmbs02n2.mediatek.inc>
2020-04-13 9:27 ` Chun-Kuang Hu
2020-04-13 20:45 ` Helen Koike
[not found] ` <b9d97a7357954ba3a71be764091c5c4d@mtkmbs02n2.mediatek.inc>
2020-06-21 7:40 ` Louis Kuo (郭德寧)
2020-06-21 15:41 ` Chun-Kuang Hu
2020-07-08 11:12 ` Louis Kuo (郭德寧)
2020-04-11 10:25 ` Chun-Kuang Hu
2020-07-01 7:42 ` Louis Kuo (郭德寧)
2020-04-10 7:17 ` [RFC PATCH V6 2/3] dt-bindings: mt8183: Add sensor interface dt-bindings Louis Kuo
2020-04-20 18:43 ` Rob Herring [this message]
2020-04-10 7:17 ` [RFC PATCH V6 3/3] dts: arm64: mt8183: Add sensor interface nodes Louis Kuo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200420184309.GA14720@bogus \
--to=robh@kernel.org \
--cc=Jerry-ch.Chen@mediatek.com \
--cc=Sean.Cheng@mediatek.com \
--cc=christie.yu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=frederic.chen@mediatek.com \
--cc=hans.verkuil@cisco.com \
--cc=jungo.lin@mediatek.com \
--cc=keiichiw@chromium.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louis.kuo@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--cc=yuzhao@chromium.org \
--cc=zwisler@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).