From: Sakari Ailus <sakari.ailus@iki.fi>
To: Luca Weiss <luca@z3ntu.xyz>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shunqian Zheng <zhengsq@rock-chips.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v4 2/3] media: dt-bindings: ov2685: convert to dtschema
Date: Fri, 31 Mar 2023 12:39:56 +0300 [thread overview]
Message-ID: <ZCaqbL4plknXYPCT@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <9AF47749-12CB-40D5-A300-170A35390CFD@z3ntu.xyz>
Hi Luca,
On Fri, Mar 31, 2023 at 11:18:29AM +0200, Luca Weiss wrote:
> >> + properties:
> >> + data-lanes:
> >> + maxItems: 1
> >
> >This should be 2 --- the sensor supports two lanes (even if the driver
> >doesn't).
>
> Right, for some reason the product brief mentions that it features "a
> single-lane MIPI interface" but the datasheet I have writes that it has a
> 2-lane MIPI serial output, so I guess it does support two lanes?
I suppose the datasheet is right. Well, if someone proves otherwise, we can
always change this.
>
> >
> >I can address this when applying if that's ok.
>
> That would be nice, thanks!
Done, thanks!
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2023-03-31 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 17:57 [PATCH v4 0/3] Improvements for OmniVision OV2685 Luca Weiss
2023-03-23 17:57 ` [PATCH v4 1/3] media: dt-bindings: media: rkisp1: complete ov2685 example Luca Weiss
2023-03-23 17:57 ` [PATCH v4 2/3] media: dt-bindings: ov2685: convert to dtschema Luca Weiss
2023-03-31 8:39 ` Sakari Ailus
2023-03-31 9:18 ` Luca Weiss
2023-03-31 9:39 ` Sakari Ailus [this message]
2023-04-18 23:54 ` Rob Herring
2023-04-19 15:54 ` Luca Weiss
2023-03-23 17:57 ` [PATCH v4 3/3] media: i2c: ov2685: Make reset gpio optional Luca Weiss
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=ZCaqbL4plknXYPCT@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=devicetree@vger.kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=zhengsq@rock-chips.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
all inboxes | Powered by JetHome®