From: jacopo mondi <jacopo@jmondi.org>
To: Rob Herring <robh@kernel.org>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
corbet@lwn.net, mchehab@kernel.org, sakari.ailus@iki.fi,
mark.rutland@arm.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] media: dt-bindings: Add OF properties to ov7670
Date: Tue, 9 Jan 2018 09:01:11 +0100 [thread overview]
Message-ID: <20180109080111.GD25666@w540> (raw)
In-Reply-To: <20180109033555.vgofzbnpx37iqaon@rob-hp-laptop>
Hi Rob,
thanks for comments
On Mon, Jan 08, 2018 at 09:35:55PM -0600, Rob Herring wrote:
> On Thu, Jan 04, 2018 at 10:52:33AM +0100, Jacopo Mondi wrote:
> > Describe newly introduced OF properties for ov7670 image sensor.
> > The driver supports two standard properties to configure synchronism
> > signals polarities and two custom properties already supported as
> > platform data options by the driver.
>
> Missing S-o-b.
>
Ups, that was trivial, sorry about that
> > ---
> > Documentation/devicetree/bindings/media/i2c/ov7670.txt | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/media/i2c/ov7670.txt b/Documentation/devicetree/bindings/media/i2c/ov7670.txt
> > index 826b656..57ded18 100644
> > --- a/Documentation/devicetree/bindings/media/i2c/ov7670.txt
> > +++ b/Documentation/devicetree/bindings/media/i2c/ov7670.txt
> > @@ -9,11 +9,22 @@ Required Properties:
> > - clocks: reference to the xclk input clock.
> > - clock-names: should be "xclk".
> >
> > +The following properties, as defined by video interfaces OF bindings
> > +"Documentation/devicetree/bindings/media/video-interfaces.txt" are supported:
> > +
> > +- hsync-active: active state of the HSYNC signal, 0/1 for LOW/HIGH respectively.
> > +- vsync-active: active state of the VSYNC signal, 0/1 for LOW/HIGH respectively.
>
> Don't these go in the endpoint? Not sure offhand.
>
Yes they do. I will list them as "Optional endpoint properties", and
> > +
> > +Default is high active state for both vsync and hsync signals.
> > +
> > Optional Properties:
> > - reset-gpios: reference to the GPIO connected to the resetb pin, if any.
> > Active is low.
> > - powerdown-gpios: reference to the GPIO connected to the pwdn pin, if any.
> > Active is high.
> > +- ov7670,pll-bypass: set to 1 to bypass PLL for pixel clock generation.
>
> Boolean instead?
>
Do we have booleans? I had a look at device tree specs and grep for
"true"/"false" in arch/arm*/boot/dts, and didn't find that much.
Seems like they're actually strings, am I wrong?
Thanks
j
> > +- ov7670,pclk-hb-disable: set to 1 to suppress pixel clock output signal during
> > + horizontal blankings.
>
> ditto
>
> >
> > The device node must contain one 'port' child node for its digital output
> > video port, in accordance with the video interface bindings defined in
> > @@ -34,6 +45,9 @@ Example:
> > assigned-clocks = <&pck0>;
> > assigned-clock-rates = <25000000>;
> >
> > + vsync-active = <0>;
> > + ov7670,pclk-hb-disable = <1>;
> > +
> > port {
> > ov7670_0: endpoint {
> > remote-endpoint = <&isi_0>;
> > --
> > 2.7.4
> >
next prev parent reply other threads:[~2018-01-09 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 9:52 [PATCH v2 0/2] media: ov7670: Implement mbus configuration Jacopo Mondi
2018-01-04 9:52 ` [PATCH v2 1/2] v4l2: i2c: ov7670: Implement OF " Jacopo Mondi
2018-01-04 9:52 ` [PATCH v2 2/2] media: dt-bindings: Add OF properties to ov7670 Jacopo Mondi
[not found] ` <1515059553-10219-3-git-send-email-jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org>
2018-01-09 3:35 ` Rob Herring
2018-01-09 8:01 ` jacopo mondi [this message]
2018-01-11 14:45 ` Rob Herring
2018-01-11 11:22 ` Sakari Ailus
2018-01-11 11:19 ` [PATCH v2 0/2] media: ov7670: Implement mbus configuration Sakari Ailus
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=20180109080111.GD25666@w540 \
--to=jacopo@jmondi.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@iki.fi \
/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).