From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Jacopo Mondi <jacopo@jmondi.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Prabhakar <prabhakar.csengg@gmail.com>
Subject: Re: [PATCH v4 2/3] media: i2c: ov772x: Add support for BT656 mode
Date: Mon, 14 Sep 2020 10:55:48 +0300 [thread overview]
Message-ID: <bb9fcd11-21d9-1ce0-4247-a5f80d836da7@gmail.com> (raw)
In-Reply-To: <20200913184247.618-3-prabhakar.mahadev-lad.rj@bp.renesas.com>
Hello!
On 13.09.2020 21:42, Lad Prabhakar wrote:
> Add support to read the bus-type for V4L2_MBUS_BT656 and
> enable BT656 mode in the sensor if needed.
Isn't it called BT.656?
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Reviewed-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> drivers/media/i2c/ov772x.c | 27 +++++++++++++++++++++------
> 1 file changed, 21 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/media/i2c/ov772x.c b/drivers/media/i2c/ov772x.c
> index 551082aa7026..edd7c4c22225 100644
> --- a/drivers/media/i2c/ov772x.c
> +++ b/drivers/media/i2c/ov772x.c
[...]
> @@ -1427,16 +1434,24 @@ static int ov772x_probe(struct i2c_client *client)
> goto error_clk_put;
> }
>
> - bus_cfg.bus_type = V4L2_MBUS_PARALLEL;
> + bus_cfg = (struct v4l2_fwnode_endpoint)
> + { .bus_type = V4L2_MBUS_BT656 };
> ret = v4l2_fwnode_endpoint_alloc_parse(ep, &bus_cfg);
> priv->bus_type = bus_cfg.bus_type;
> v4l2_fwnode_endpoint_free(&bus_cfg);
> if (ret) {
> - /* For backward compatibility with the existing DT where
> - * bus-type isnt specified fallback to V4L2_MBUS_PARALLEL
> - */
> - priv->bus_type = V4L2_MBUS_PARALLEL;
> - dev_notice(&client->dev, "Falling back to V4L2_MBUS_PARALLEL mode\n");
> + bus_cfg.bus_type = V4L2_MBUS_PARALLEL;
> + ret = v4l2_fwnode_endpoint_alloc_parse(ep, &bus_cfg);
> + priv->bus_type = bus_cfg.bus_type;
> + v4l2_fwnode_endpoint_free(&bus_cfg);
> + if (ret) {
> + /* For backward compatibility with the existing DT where
> + * bus-type isnt specified fallback to V4L2_MBUS_PARALLEL
^^^^ isn't
Could be fixed, while at it?
> + */
> + priv->bus_type = V4L2_MBUS_PARALLEL;
> + dev_notice(&client->dev,
> + "Falling back to V4L2_MBUS_PARALLEL mode\n");
> + }
> }
>
> ret = ov772x_video_probe(priv);
MBR, Sergei
next prev parent reply other threads:[~2020-09-14 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 18:42 [PATCH v4 0/3] media: i2c: ov772x: Enable BT656 mode and test pattern support Lad Prabhakar
2020-09-13 18:42 ` [PATCH v4 1/3] media: i2c: ov772x: Parse endpoint properties Lad Prabhakar
2020-09-14 6:54 ` Sakari Ailus
2020-09-14 18:26 ` Lad, Prabhakar
2020-09-14 14:09 ` Jacopo Mondi
2020-09-13 18:42 ` [PATCH v4 2/3] media: i2c: ov772x: Add support for BT656 mode Lad Prabhakar
2020-09-14 7:55 ` Sergei Shtylyov [this message]
2020-09-13 18:42 ` [PATCH v4 3/3] media: i2c: ov772x: Add test pattern control Lad Prabhakar
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=bb9fcd11-21d9-1ce0-4247-a5f80d836da7@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=jacopo@jmondi.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®