From: Rob Herring <robh@kernel.org>
To: Benoit Parrot <bparrot@ti.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Patch v4 2/2] media: v4l: ti-vpe: Document CAL driver
Date: Tue, 17 Nov 2015 15:22:12 -0600 [thread overview]
Message-ID: <20151117212212.GA20622@rob-hp-laptop> (raw)
In-Reply-To: <20151116225249.GQ3999@ti.com>
On Mon, Nov 16, 2015 at 04:52:49PM -0600, Benoit Parrot wrote:
> Rob Herring <robh@kernel.org> wrote on Mon [2015-Nov-16 09:26:16 -0600]:
> > On Sun, Nov 15, 2015 at 05:53:48PM -0600, Benoit Parrot wrote:
> > > Device Tree bindings for the Camera Adaptation Layer (CAL) driver
> >
> > Bindings are for h/w blocks, not drivers...
>
> OK I'll fix that.
>
> >
> > >
> > > Signed-off-by: Benoit Parrot <bparrot@ti.com>
> > > ---
> > > Documentation/devicetree/bindings/media/ti-cal.txt | 70 ++++++++++++++++++++++
> > > 1 file changed, 70 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/media/ti-cal.txt
> > >
> > > diff --git a/Documentation/devicetree/bindings/media/ti-cal.txt b/Documentation/devicetree/bindings/media/ti-cal.txt
> > > new file mode 100644
> > > index 000000000000..680efadb6208
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/media/ti-cal.txt
> > > @@ -0,0 +1,70 @@
> > > +Texas Instruments DRA72x CAMERA ADAPTATION LAYER (CAL)
> > > +------------------------------------------------------
> > > +
> > > +The Camera Adaptation Layer (CAL) is a key component for image capture
> > > +applications. The capture module provides the system interface and the
> > > +processing capability to connect CSI2 image-sensor modules to the
> > > +DRA72x device.
> > > +
> > > +Required properties:
> > > +- compatible: must be "ti,cal"
> >
> > Needs to be more specific.
>
> See potential patch below.
Looks fine.
> > > +
> > > + csi2_0: port@0 {
> >
> > Multiple ports should be under a ports node.
>
> The video-interfaces.txt bindings doc state:
> "All 'port' nodes can be grouped under optional 'ports' node"
> Doesn't that mean that 'ports' is then optional has show in the csi2
> example provide in the same documents?
Yes, but we may want to change that or at least what is recommended.
Often when we don't group things, and we latter decide we want to. It
makes things easier if you have other child nodes that are not port
nodes.
Rob
prev parent reply other threads:[~2015-11-17 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 23:53 [Patch v4 0/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver Benoit Parrot
2015-11-15 23:53 ` [Patch v4 1/2] " Benoit Parrot
2015-11-15 23:53 ` [Patch v4 2/2] media: v4l: ti-vpe: Document CAL driver Benoit Parrot
2015-11-16 15:26 ` Rob Herring
2015-11-16 22:52 ` Benoit Parrot
2015-11-17 21:22 ` 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=20151117212212.GA20622@rob-hp-laptop \
--to=robh@kernel.org \
--cc=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.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