From: Adam Ford <aford173@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Xavier Roumegue <xavier.roumegue@oss.nxp.com>,
linux-imx@nxp.com, kernel@pengutronix.de,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/3] dt-bindings: media: imx8-isi: Use 'port' instead of 'ports' for i.MX8MN
Date: Thu, 26 Jan 2023 12:31:16 -0600 [thread overview]
Message-ID: <CAHCN7xJNGCd=Sghu3oe9_yjSg0ybXRFHaVLaZmC2guXCy7ty1A@mail.gmail.com> (raw)
In-Reply-To: <20230126170603.11896-3-laurent.pinchart@ideasonboard.com>
On Thu, Jan 26, 2023 at 11:06 AM Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> .../bindings/media/nxp,imx8-isi.yaml | 39 +++++++++++--------
> 1 file changed, 22 insertions(+), 17 deletions(-)
>
Is there a reason not to squash the two bindings into just one patch?
> diff --git a/Documentation/devicetree/bindings/media/nxp,imx8-isi.yaml b/Documentation/devicetree/bindings/media/nxp,imx8-isi.yaml
> index 6038b9b5ab36..121594569395 100644
> --- a/Documentation/devicetree/bindings/media/nxp,imx8-isi.yaml
> +++ b/Documentation/devicetree/bindings/media/nxp,imx8-isi.yaml
> @@ -52,11 +52,21 @@ properties:
> power-domains:
> maxItems: 1
>
> + port:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: |
> + The port represents the Pixel Link input to the ISI. It shall have a
> + single endpoint. This property is only used for ISI instances with a
> + single port (as in the i.MX8MN). For instances that includes multiple
> + ports, the 'ports' property shall be used instead.
> +
> ports:
> $ref: /schemas/graph.yaml#/properties/ports
> description: |
> Ports represent the Pixel Link inputs to the ISI. Their number and
> - assignment are model-dependent. Each port shall have a single endpoint.
> + assignment are model-dependent. For ISI instances that have a single
> + port, the 'port' property should be used instead. Each port shall have a
> + single endpoint.
>
> required:
> - compatible
> @@ -65,7 +75,6 @@ required:
> - clocks
> - clock-names
> - fsl,blk-ctrl
> - - ports
>
> allOf:
> - if:
> @@ -77,12 +86,11 @@ allOf:
> properties:
> interrupts:
> maxItems: 1
> - ports:
> - properties:
> - port@0:
> - description: MIPI CSI-2 RX
> - required:
> - - port@0
> + port:
> + description: MIPI CSI-2 RX
> + ports: false
> + required:
> + - port
>
> - if:
> properties:
> @@ -93,6 +101,7 @@ allOf:
> properties:
> interrupts:
> maxItems: 2
> + port: false
> ports:
> properties:
> port@0:
> @@ -102,6 +111,8 @@ allOf:
> required:
> - port@0
> - port@1
> + required:
> + - ports
>
> additionalProperties: false
>
> @@ -122,15 +133,9 @@ examples:
> fsl,blk-ctrl = <&disp_blk_ctrl>;
> power-domains = <&disp_blk_ctrl IMX8MN_DISPBLK_PD_ISI>;
>
> - ports {
> - #address-cells = <1>;
> - #size-cells = <0>;
> -
> - port@0 {
> - reg = <0>;
> - isi_in: endpoint {
> - remote-endpoint = <&mipi_csi_out>;
> - };
> + port {
> + isi_in: endpoint {
> + remote-endpoint = <&mipi_csi_out>;
> };
> };
> };
> --
> Regards,
>
> Laurent Pinchart
>
next prev parent reply other threads:[~2023-01-26 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230126170603.11896-1-laurent.pinchart@ideasonboard.com>
2023-01-26 17:06 ` [PATCH v4 1/3] dt-bindings: media: Add i.MX8 ISI DT bindings Laurent Pinchart
2023-01-30 18:56 ` Rob Herring
2023-01-26 17:06 ` [PATCH v4 2/3] dt-bindings: media: imx8-isi: Use 'port' instead of 'ports' for i.MX8MN Laurent Pinchart
2023-01-26 18:31 ` Adam Ford [this message]
2023-01-26 18:39 ` Laurent Pinchart
2023-01-26 18:47 ` Adam Ford
2023-01-30 18:55 ` Rob Herring
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='CAHCN7xJNGCd=Sghu3oe9_yjSg0ybXRFHaVLaZmC2guXCy7ty1A@mail.gmail.com' \
--to=aford173@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-imx@nxp.com \
--cc=linux-media@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=xavier.roumegue@oss.nxp.com \
/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).