From: Marco Felsch <m.felsch@pengutronix.de>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Rob Herring <robh@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Robert Foss <robert.foss@linaro.org>,
Tomasz Figa <tfiga@chromium.org>,
Sakari Ailus <sakari.ailus@iki.fi>,
Dongchun Zhu <dongchun.zhu@mediatek.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Fabio Estevam <festevam@gmail.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH v7 1/3] media: dt-bindings: ov8856: Document YAML bindings
Date: Tue, 28 Apr 2020 10:25:05 +0200 [thread overview]
Message-ID: <20200428082505.GA22489@pengutronix.de> (raw)
In-Reply-To: <20200428075504.ovzugt2mbgan7z3k@gilmour.lan>
On 20-04-28 09:55, Maxime Ripard wrote:
> On Mon, Apr 27, 2020 at 05:13:42PM +0200, Robert Foss wrote:
> > On Wed, 15 Apr 2020 at 18:21, Marco Felsch <m.felsch@pengutronix.de> wrote:
> > >
> > > On 20-04-15 11:07, Rob Herring wrote:
> > > > On Wed, Apr 08, 2020 at 01:08:14PM +0200, Robert Foss wrote:
> > > > > From: Dongchun Zhu <dongchun.zhu@mediatek.com>
...
> > > > > + clock-names:
> > > > > + description:
> > > > > + Input clock for the sensor.
> > > > > + items:
> > > > > + - const: xvclk
> > > > > +
> > > > > + assigned-clocks:
> > > > > + description:
> > > > > + Input clock for the sensor.
> > > > > +
> > > > > + assigned-clock-rates:
> > > > > + description:
> > > > > + Frequency of the xvclk clock in Hertz.
> > > >
> > > > These 2 should have a 'maxItems: 1'
> > >
> > > Don't know why those properties are needed here.. IMHO this shouldn't be
> > > part of the binding or at least it should be optional and not required.
> > > All we need is the clocks and the clock-names property.
> >
> > Thanks Marco, I'll make it optional for the next revision.
>
> Well, the whole discussion we had was about removing them entirely?
+1 from my side. It is part of the system integration and not part of
this device.
Regards,
Marco
> Maxime
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-28 8:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 11:08 [PATCH v4 0/3] media: ov8856: Add devicetree support Robert Foss
2020-04-08 11:08 ` [PATCH v7 1/3] media: dt-bindings: ov8856: Document YAML bindings Robert Foss
2020-04-15 16:07 ` Rob Herring
2020-04-15 16:21 ` Marco Felsch
2020-04-27 15:13 ` Robert Foss
2020-04-28 7:55 ` Maxime Ripard
2020-04-28 8:25 ` Marco Felsch [this message]
2020-04-28 11:51 ` Robert Foss
2020-04-27 15:12 ` Robert Foss
2020-04-08 11:08 ` [PATCH v4 2/3] media: ov8856: Add devicetree support Robert Foss
2020-04-08 11:08 ` [PATCH v4 3/3] media: ov8856: Implement sensor module revision identification Robert Foss
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=20200428082505.GA22489@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dongchun.zhu@mediatek.com \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=robert.foss@linaro.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=tfiga@chromium.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;
as well as URLs for NNTP newsgroup(s).