From: Conor Dooley <conor@kernel.org>
To: Julien Massot <julien.massot@collabora.com>
Cc: benjamin.mugnier@foss.st.com, sylvain.petinot@foss.st.com,
mchehab@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
kernel@collabora.com, devicetree@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH] media: dt-bindings: st-vgxy61: relax data-lanes restriction
Date: Wed, 13 Dec 2023 16:30:18 +0000 [thread overview]
Message-ID: <20231213-chest-turf-8e9c4fb0a3db@spud> (raw)
In-Reply-To: <20231213071737.1070162-1-julien.massot@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On Wed, Dec 13, 2023 at 08:17:37AM +0100, Julien Massot wrote:
> The ST VGXY61 sensors support multiple lane number, as
> well as lane mapping.
>
> Signed-off-by: Julien Massot <julien.massot@collabora.com>
> ---
> .../devicetree/bindings/media/i2c/st,st-vgxy61.yaml | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/st,st-vgxy61.yaml b/Documentation/devicetree/bindings/media/i2c/st,st-vgxy61.yaml
> index 8c28848b226a..733fac85a20f 100644
> --- a/Documentation/devicetree/bindings/media/i2c/st,st-vgxy61.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/st,st-vgxy61.yaml
> @@ -67,11 +67,8 @@ properties:
> data-lanes:
> description:
> CSI lanes to use
> - items:
> - - const: 1
> - - const: 2
> - - const: 3
> - - const: 4
> + minItems: 1
> + maxItems: 4
So, it is now valid to have "data-lanes = <6 7 8>;" now?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-13 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 7:17 [PATCH] media: dt-bindings: st-vgxy61: relax data-lanes restriction Julien Massot
2023-12-13 16:30 ` Conor Dooley [this message]
2024-01-05 9:36 ` Julien Massot
2024-02-09 9:24 ` Benjamin Mugnier
2024-03-15 9:06 ` Julien Massot
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=20231213-chest-turf-8e9c4fb0a3db@spud \
--to=conor@kernel.org \
--cc=benjamin.mugnier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=julien.massot@collabora.com \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sylvain.petinot@foss.st.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