From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] media: staging: max96712: Add support for 3-lane C-PHY
Date: Thu, 30 Mar 2023 16:21:41 +0200 [thread overview]
Message-ID: <ZCWa9XbK5qlm67rz@oden.dyn.berto.se> (raw)
In-Reply-To: <20230211144614.3816247-1-niklas.soderlund+renesas@ragnatech.se>
Hi Mauro,
Gentle ping on this patch.
On 2023-02-11 15:46:14 +0100, Niklas Söderlund wrote:
> Add basic support for outputting the test patterns on a 3-lane CSI-2
> C-PHY bus. As the driver only can output frames form its internal test
> pattern generator, enabling C-PHY output is as simple as setting the
> output mode to C-PHY instead of D-PHY.
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> drivers/staging/media/max96712/max96712.c | 36 +++++++++++++++++++----
> 1 file changed, 30 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/media/max96712/max96712.c b/drivers/staging/media/max96712/max96712.c
> index 99b333b68198..d93dd985fb27 100644
> --- a/drivers/staging/media/max96712/max96712.c
> +++ b/drivers/staging/media/max96712/max96712.c
> @@ -30,6 +30,7 @@ struct max96712_priv {
> struct regmap *regmap;
> struct gpio_desc *gpiod_pwdn;
>
> + bool cphy;
> struct v4l2_mbus_config_mipi_csi2 mipi;
>
> struct v4l2_subdev sd;
> @@ -127,10 +128,18 @@ static void max96712_mipi_configure(struct max96712_priv *priv)
> /* Select 2x4 mode. */
> max96712_write(priv, 0x8a0, 0x04);
>
> - /* Configure a 4-lane DPHY using PHY0 and PHY1. */
> /* TODO: Add support for 2-lane and 1-lane configurations. */
> - /* TODO: Add support CPHY mode. */
> - max96712_write(priv, 0x94a, 0xc0);
> + if (priv->cphy) {
> + /* Configure a 3-lane C-PHY using PHY0 and PHY1. */
> + max96712_write(priv, 0x94a, 0xa0);
> +
> + /* Configure C-PHY timings. */
> + max96712_write(priv, 0x8ad, 0x3f);
> + max96712_write(priv, 0x8ae, 0x7d);
> + } else {
> + /* Configure a 4-lane D-PHY using PHY0 and PHY1. */
> + max96712_write(priv, 0x94a, 0xc0);
> + }
>
> /* Configure lane mapping for PHY0 and PHY1. */
> /* TODO: Add support for lane swapping. */
> @@ -332,8 +341,9 @@ static int max96712_parse_dt(struct max96712_priv *priv)
> {
> struct fwnode_handle *ep;
> struct v4l2_fwnode_endpoint v4l2_ep = {
> - .bus_type = V4L2_MBUS_CSI2_DPHY
> + .bus_type = V4L2_MBUS_UNKNOWN,
> };
> + unsigned int supported_lanes;
> int ret;
>
> ep = fwnode_graph_get_endpoint_by_id(dev_fwnode(&priv->client->dev), 4,
> @@ -350,8 +360,22 @@ static int max96712_parse_dt(struct max96712_priv *priv)
> return -EINVAL;
> }
>
> - if (v4l2_ep.bus.mipi_csi2.num_data_lanes != 4) {
> - dev_err(&priv->client->dev, "Only 4 data lanes supported\n");
> + switch (v4l2_ep.bus_type) {
> + case V4L2_MBUS_CSI2_DPHY:
> + supported_lanes = 4;
> + priv->cphy = false;
> + break;
> + case V4L2_MBUS_CSI2_CPHY:
> + supported_lanes = 3;
> + priv->cphy = true;
> + break;
> + default:
> + dev_err(&priv->client->dev, "Unsupported bus-type %u\n", v4l2_ep.bus_type);
> + return -EINVAL;
> + }
> +
> + if (v4l2_ep.bus.mipi_csi2.num_data_lanes != supported_lanes) {
> + dev_err(&priv->client->dev, "Only %u data lanes supported\n", supported_lanes);
> return -EINVAL;
> }
>
> --
> 2.39.1
>
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2023-03-30 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 14:46 [PATCH] media: staging: max96712: Add support for 3-lane C-PHY Niklas Söderlund
2023-03-30 14:21 ` Niklas Söderlund [this message]
2023-03-31 12:21 ` Sakari Ailus
2023-03-31 13:24 ` Niklas Söderlund
2023-03-31 14:08 ` Sakari Ailus
2023-03-31 14:19 ` Niklas Söderlund
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=ZCWa9XbK5qlm67rz@oden.dyn.berto.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=gregkh@linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.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