From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Jason Chen <jason.z.chen@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/4] media: dt-bindings: Add OmniVision OV08X40
Date: Thu, 3 Oct 2024 12:17:18 +0200 [thread overview]
Message-ID: <e8142566-aef5-498e-9d2d-8ac187ce8524@kernel.org> (raw)
In-Reply-To: <8554d372-18cb-4351-a5ab-894be09c613b@linaro.org>
On 03/10/2024 10:38, Bryan O'Donoghue wrote:
> On 03/10/2024 09:33, Bryan O'Donoghue wrote:
>> On 03/10/2024 09:29, Krzysztof Kozlowski wrote:
>>> On Wed, Oct 02, 2024 at 02:58:44PM +0100, Bryan O'Donoghue wrote:
>>>> + properties:
>>>> + data-lanes:
>>>> + oneOf:
>>>> + - items:
>>>> + - const: 1
>>>> + - const: 2
>>>> + - items:
>>>> + - const: 1
>>>> + - const: 2
>>>> + - const: 3
>>>> + - const: 4
>>>> +
>>>> + link-frequencies: true
>>>
>>> Not much changed here and you did not continued discussion about it.
>>>
>>> Best regards,
>>> Krzysztof
>>>
>>
>> Ah my mistake, I didn't read the bit at the bottom of your email
>
> I'll do this
>
> Documentation/devicetree/bindings/media/i2c/thine,thp7312.yaml
>
> data-lanes:
> description:
> This property is for lane reordering between the THP7312
> and the SoC. The sensor supports either two-lane, or
> four-lane operation.
> If this property is omitted four-lane operation is
> assumed. For two-lane operation the property must be
> set to <1 2>.
> minItems: 2
> maxItems: 4
> items:
> maximum: 4
>
> This captures what I'm after.
I commented on link-frequencies.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-03 10:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 13:58 [PATCH v3 0/4] ov08x40: Enable use of ov08x40 on Qualcomm X1E80100 CRD Bryan O'Donoghue
2024-10-02 13:58 ` [PATCH v3 1/4] media: ov08x40: Fix burst write sequence Bryan O'Donoghue
2024-10-02 13:58 ` [PATCH v3 2/4] media: dt-bindings: Add OmniVision OV08X40 Bryan O'Donoghue
2024-10-03 8:29 ` Krzysztof Kozlowski
2024-10-03 8:33 ` Bryan O'Donoghue
2024-10-03 8:36 ` Krzysztof Kozlowski
2024-10-03 8:38 ` Bryan O'Donoghue
2024-10-03 10:17 ` Krzysztof Kozlowski [this message]
2024-10-03 11:54 ` Bryan O'Donoghue
2024-10-03 12:17 ` Sakari Ailus
2024-10-03 12:31 ` Krzysztof Kozlowski
2024-10-03 12:40 ` Bryan O'Donoghue
2024-10-03 12:47 ` Sakari Ailus
2024-10-03 12:48 ` Bryan O'Donoghue
2024-10-03 12:46 ` Sakari Ailus
2024-10-02 13:58 ` [PATCH v3 3/4] media: ov08x40: Rename ext_clk to xvclk Bryan O'Donoghue
2024-10-02 13:58 ` [PATCH v3 4/4] media: ov08x40: Add OF probe support Bryan O'Donoghue
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=e8142566-aef5-498e-9d2d-8ac187ce8524@kernel.org \
--to=krzk@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jason.z.chen@intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=senozhatsky@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).