From: Jacopo Mondi <jacopo@jmondi.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org, "Lad,
Prabhakar" <prabhakar.csengg@gmail.com>,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
hverkuil-cisco@xs4all.nl, laurent.pinchart@ideasonboard.com,
linux-renesas-soc@vger.kernel.org, Rob Herring <robh@kernel.org>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v4 2/3] dt-bindings: media: ov772x: Make bus-type mandatory
Date: Fri, 4 Sep 2020 10:05:35 +0200 [thread overview]
Message-ID: <20200904080535.ppmaarnusrnjr4xt@uno.localdomain> (raw)
In-Reply-To: <20200903131029.18334-3-jacopo+renesas@jmondi.org>
Hi Laurent,
On Thu, Sep 03, 2020 at 03:10:28PM +0200, Jacopo Mondi wrote:
> In order to establish required properties based on the selected
> bus type, make the 'bus-type' property mandatory. As this change
> documents an endpoint property, also document the 'remote-endpoint'
> one now that the 'endpoint' schema has been expanded.
>
> Binary compatibility with existing DTB is kept as the driver does not
> enforce the property to be present, and shall fall-back to default
> parallel bus configuration, which was the only supported bus type, if
> the property is not specified.
>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> ---
> .../bindings/media/i2c/ovti,ov772x.yaml | 20 +++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov772x.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ov772x.yaml
> index e7e2d31fcc23..406e9cd463a2 100644
> --- a/Documentation/devicetree/bindings/media/i2c/ovti,ov772x.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov772x.yaml
> @@ -41,6 +41,25 @@ properties:
> description: |
> Video output port. See ../video-interfaces.txt.
>
> + properties:
> + endpoint:
> + type: object
> +
> + properties:
> + remote-endpoint:
> + description: See ../video-interfaces.txt
So I guess the same as you suggested for imx214 applies here (drop
remote-endpoint)
> +
> + bus-type:
> + enum: [5, 6]
> +
> + required:
> + - remote-endpoint
> + - bus-type
> +
> + additionalProperties: false
> +
> + additionalProperties: false
> +
> required:
> - compatible
> - reg
> @@ -65,6 +84,7 @@ examples:
>
> port {
> ov772x_0: endpoint {
> + bus-type = <5>;
> remote-endpoint = <&vcap1_in0>;
> };
> };
> --
> 2.28.0
>
next prev parent reply other threads:[~2020-09-04 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 13:10 [PATCH v4 0/3] dt-bindings: media: ov772x: Convert to json-schema Jacopo Mondi
2020-09-03 13:10 ` [PATCH v4 1/3] " Jacopo Mondi
2020-09-03 13:10 ` [PATCH v4 2/3] dt-bindings: media: ov772x: Make bus-type mandatory Jacopo Mondi
2020-09-04 8:05 ` Jacopo Mondi [this message]
2020-09-04 15:06 ` Laurent Pinchart
2020-09-04 15:16 ` Jacopo Mondi
2020-09-03 13:10 ` [PATCH v4 3/3] dt-bindings: media: ov772x: Document endpoint props Jacopo Mondi
2020-09-03 21:33 ` Laurent Pinchart
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=20200904080535.ppmaarnusrnjr4xt@uno.localdomain \
--to=jacopo@jmondi.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.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