From: Dongchun Zhu <dongchun.zhu@mediatek.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: <mchehab@kernel.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <matthias.bgg@gmail.com>,
<bingbu.cao@intel.com>, <srv_heupstream@mediatek.com>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>, <sj.huang@mediatek.com>,
<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<louis.kuo@mediatek.com>, <shengnan.wang@mediatek.com>,
<tfiga@google.com>, <drinkcat@chromium.org>
Subject: Re: [RFC,V2,1/2] media: dt-bindings: media: i2c: Add bindings for OV02A10
Date: Mon, 19 Aug 2019 13:39:30 +0800 [thread overview]
Message-ID: <1566193170.21623.46.camel@mhfsdcap03> (raw)
In-Reply-To: <20190817213207.GC3504@valkosipuli.retiisi.org.uk>
Hi Sakari,
On Sun, 2019-08-18 at 00:32 +0300, Sakari Ailus wrote:
> Hi Dongchun,
>
> On Sat, Aug 17, 2019 at 11:53:05AM +0800, Dongchun Zhu wrote:
> ...
> > > > +
> > > > +The device node shall contain one 'port' child node with an
> > > > +'endpoint' subnode for its digital output video port, in accordance
> > > > +with the video interface bindings defined in
> > > > +Documentation/devicetree/bindings/media/video-interfaces.txt.
> > > > +The endpoint optional property 'data-lanes' shall be "<1>".
> > >
> > > How many lanes does the module (or the sensor) have?
> > >
> >
> > From sensor datasheet, OV02A10 supports 1-lane MIPI interface.
>
> If only one lane is supported, the property should be omitted: there's
> nothing that the driver needs to know here.
>
Thanks for the suggestion.
But sorry that I didn't read this message this morning, so this issue
still remains unsettled in v3.
https://patchwork.kernel.org/patch/11100219/
I would fix this point in v4.
next prev parent reply other threads:[~2019-08-19 5:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 8:46 [RFC,V2,0/2] media: add support for OV02A10 sensor dongchun.zhu
2019-07-04 8:46 ` [RFC,V2,1/2] media: dt-bindings: media: i2c: Add bindings for OV02A10 dongchun.zhu
2019-07-22 23:49 ` Rob Herring
[not found] ` <5d5d644af9334609bb7c3ff745b2e754@mtkmbs02n1.mediatek.inc>
2019-08-17 5:03 ` Dongchun Zhu
2019-07-23 7:41 ` Sakari Ailus
[not found] ` <ef65288c523f405396991bd6d757bba0@mtkmbs02n1.mediatek.inc>
2019-08-17 3:53 ` Dongchun Zhu
2019-08-17 21:32 ` Sakari Ailus
2019-08-19 5:39 ` Dongchun Zhu [this message]
2019-07-04 8:46 ` [RFC,V2,2/2] media: i2c: Add Omnivision OV02A10 camera sensor driver dongchun.zhu
2019-07-08 7:52 ` Bingbu Cao
[not found] ` <8639e67ad6db40b78e48b00c875187dc@mtkmbs02n1.mediatek.inc>
2019-08-17 5:35 ` Dongchun Zhu
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=1566193170.21623.46.camel@mhfsdcap03 \
--to=dongchun.zhu@mediatek.com \
--cc=bingbu.cao@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louis.kuo@mediatek.com \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=shengnan.wang@mediatek.com \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@google.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).