From: Benoit Parrot <bparrot@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>, <linux-media@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 02/19] dt-bindings: media: cal: update binding example
Date: Wed, 30 Oct 2019 08:41:18 -0500 [thread overview]
Message-ID: <20191030134118.5uc4xttzh7wzpucd@ti.com> (raw)
In-Reply-To: <20191029132157.GA27757@bogus>
Rob Herring <robh@kernel.org> wrote on Tue [2019-Oct-29 08:21:57 -0500]:
> On Fri, Oct 18, 2019 at 10:34:20AM -0500, Benoit Parrot wrote:
> > Update binding example to show proper endpoint properties and linkage.
> >
> > Signed-off-by: Benoit Parrot <bparrot@ti.com>
> > ---
> > .../devicetree/bindings/media/ti-cal.txt | 32 ++++++++++---------
> > 1 file changed, 17 insertions(+), 15 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/media/ti-cal.txt b/Documentation/devicetree/bindings/media/ti-cal.txt
> > index 782f801b12a9..6b56fddcfc4a 100644
> > --- a/Documentation/devicetree/bindings/media/ti-cal.txt
> > +++ b/Documentation/devicetree/bindings/media/ti-cal.txt
> > @@ -27,7 +27,6 @@ Documentation/devicetree/bindings/media/video-interfaces.txt.
> > Example:
> > cal: cal@4845b000 {
> > compatible = "ti,dra72-cal";
> > - ti,hwmods = "cal";
> > reg = <0x4845B000 0x400>,
> > <0x4845B800 0x40>,
> > <0x4845B900 0x40>;
> > @@ -45,9 +44,10 @@ Example:
> >
> > csi2_0: port@0 {
> > reg = <0>;
> > - endpoint {
> > - slave-mode;
> > - remote-endpoint = <&ar0330_1>;
> > + csi2_phy0: endpoint@0 {
>
> Unit address without 'reg' is not correct.
Ok so just "endpoint" then?
>
> > + remote-endpoint = <&csi2_cam0>;
> > + clock-lanes = <0>;
> > + data-lanes = <1 2>;
> > };
> > };
> > csi2_1: port@1 {
> > @@ -57,19 +57,21 @@ Example:
> > };
> >
> > i2c5: i2c@4807c000 {
> > - ar0330@10 {
> > - compatible = "ti,ar0330";
> > - reg = <0x10>;
> > + status = "okay";
>
> Don't show status in examples.
Ok.
>
> > + clock-frequency = <400000>;
> >
> > - port {
> > - #address-cells = <1>;
> > - #size-cells = <0>;
> > + ov5640@3c {
>
> camera-sensor@3c
Ok.
>
> > + compatible = "ovti,ov5640";
> > + reg = <0x3c>;
> > +
> > + clocks = <&clk_ov5640_fixed>;
> > + clock-names = "xclk";
> >
> > - ar0330_1: endpoint {
> > - reg = <0>;
> > - clock-lanes = <1>;
> > - data-lanes = <0 2 3 4>;
> > - remote-endpoint = <&csi2_0>;
> > + port {
> > + csi2_cam0: endpoint {
> > + remote-endpoint = <&csi2_phy0>;
> > + clock-lanes = <0>;
> > + data-lanes = <1 2>;
> > };
> > };
> > };
> > --
> > 2.17.1
> >
next prev parent reply other threads:[~2019-10-30 13:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 15:34 [Patch 00/19] media: ti-vpe: cal: maintenance Benoit Parrot
2019-10-18 15:34 ` [Patch 01/19] dt-bindings: media: cal: update binding to use syscon Benoit Parrot
2019-10-29 13:20 ` Rob Herring
2019-10-30 13:39 ` Benoit Parrot
2019-10-18 15:34 ` [Patch 02/19] dt-bindings: media: cal: update binding example Benoit Parrot
2019-10-29 13:21 ` Rob Herring
2019-10-30 13:41 ` Benoit Parrot [this message]
2019-10-18 15:34 ` [Patch 03/19] media: ti-vpe: cal: Add per platform data support Benoit Parrot
2019-10-29 13:18 ` Rob Herring
2019-10-30 13:34 ` Benoit Parrot
2019-10-18 15:34 ` [Patch 04/19] media: ti-vpe: cal: Enable DMABUF export Benoit Parrot
2019-10-18 15:34 ` [Patch 05/19] media: ti-vpe: cal: Restrict DMA to avoid memory corruption Benoit Parrot
2019-10-18 15:34 ` [Patch 06/19] dt-bindings: media: cal: update binding to add PHY LDO errata support Benoit Parrot
2019-10-29 13:23 ` Rob Herring
2019-10-18 15:34 ` [Patch 07/19] media: ti-vpe: cal: add CSI2 " Benoit Parrot
2019-10-21 10:38 ` Hans Verkuil
2019-10-23 16:03 ` Benoit Parrot
2019-10-18 15:34 ` [Patch 08/19] media: ti-vpe: cal: Fix ths_term/ths_settle parameters Benoit Parrot
2019-10-18 15:34 ` [Patch 09/19] media: ti-vpe: cal: Fix pixel processing parameters Benoit Parrot
2019-10-18 15:34 ` [Patch 10/19] media: ti-vpe: cal: Align DPHY init sequence with docs Benoit Parrot
2019-10-18 15:34 ` [Patch 11/19] dt-bindings: media: cal: update binding to add DRA76x support Benoit Parrot
2019-10-29 13:24 ` Rob Herring
2019-10-18 15:34 ` [Patch 12/19] media: ti-vpe: cal: Add " Benoit Parrot
2019-10-18 15:34 ` [Patch 13/19] dt-bindings: media: cal: update binding to add AM654 support Benoit Parrot
2019-10-29 13:24 ` Rob Herring
2019-10-18 15:34 ` [Patch 14/19] media: ti-vpe: cal: Add " Benoit Parrot
2019-10-18 15:34 ` [Patch 15/19] media: ti-vpe: cal: Add subdev s_power hooks Benoit Parrot
2019-10-18 15:34 ` [Patch 16/19] media: ti-vpe: cal: Properly calculate max resolution boundary Benoit Parrot
2019-10-18 15:34 ` [Patch 17/19] media: ti-vpe: cal: Fix a WARN issued when start streaming fails Benoit Parrot
2019-10-18 15:34 ` [Patch 18/19] media: ti-vpe: cal: fix enum_mbus_code/frame_size subdev arguments Benoit Parrot
2019-10-18 15:34 ` [Patch 19/19] dt-bindings: media: cal: convert binding to yaml Benoit Parrot
2019-10-21 10:49 ` Hans Verkuil
2019-10-23 16:06 ` Benoit Parrot
2019-10-22 7:46 ` Sakari Ailus
2019-10-23 16:18 ` Benoit Parrot
2019-10-24 6:13 ` Sakari Ailus
2019-10-29 14:22 ` Rob Herring
2019-10-30 13:54 ` Benoit Parrot
2019-10-21 10:50 ` [Patch 00/19] media: ti-vpe: cal: maintenance Hans Verkuil
2019-10-23 16:05 ` Benoit Parrot
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=20191030134118.5uc4xttzh7wzpucd@ti.com \
--to=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=robh@kernel.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