From: Rob Herring <robh@kernel.org>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
laurent.pinchart@ideasonboard.com,
linux-renesas-soc@vger.kernel.org, "Lad,
Prabhakar" <prabhakar.csengg@gmail.com>,
sakari.ailus@linux.intel.com, linux-media@vger.kernel.org,
mchehab@kernel.org,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
hverkuil-cisco@xs4all.nl
Subject: Re: [PATCH v5 3/3] dt-bindings: media: ov772x: Document endpoint props
Date: Tue, 15 Sep 2020 14:12:01 -0600 [thread overview]
Message-ID: <20200915201201.GA2428103@bogus> (raw)
In-Reply-To: <20200910162055.614089-4-jacopo+renesas@jmondi.org>
On Thu, 10 Sep 2020 18:20:55 +0200, Jacopo Mondi wrote:
> Document endpoint properties for the parallel bus type and
> add them to the example.
>
> Specify a few constraints:
> - If the bus type is BT.656 no hsync or vsync polarities can be
> specified.
> - If the bus width is 10 bits, not data-shift can be applied.
>
> 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 | 44 +++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2020-09-15 20:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 16:20 [PATCH v5 0/3] dt-bindings: media: ov772x: Convert to json-schema Jacopo Mondi
2020-09-10 16:20 ` [PATCH v5 1/3] " Jacopo Mondi
2020-09-15 20:10 ` Rob Herring
2020-09-10 16:20 ` [PATCH v5 2/3] dt-bindings: media: ov772x: Make bus-type mandatory Jacopo Mondi
2020-09-11 5:37 ` Sakari Ailus
2020-09-11 8:58 ` Jacopo Mondi
2020-09-11 8:59 ` Prabhakar Mahadev Lad
2020-09-11 9:23 ` Sakari Ailus
2020-09-11 9:46 ` Jacopo Mondi
2020-09-10 16:20 ` [PATCH v5 3/3] dt-bindings: media: ov772x: Document endpoint props Jacopo Mondi
2020-09-15 20:12 ` Rob Herring [this message]
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=20200915201201.GA2428103@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo+renesas@jmondi.org \
--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=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;
as well as URLs for NNTP newsgroup(s).