From: Julien Massot <julien.massot@collabora.com>
To: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 5/5] media/i2c: max96717: allow user to override operation mode from DT
Date: Tue, 18 Feb 2025 16:21:36 +0100 [thread overview]
Message-ID: <3c46bbb64e6e9c7b836c3ca82d678e550d1b2ddf.camel@collabora.com> (raw)
In-Reply-To: <20250207112958.2571600-6-laurentiu.palcu@oss.nxp.com>
Hi Laurentiu,
On Fri, 2025-02-07 at 13:29 +0200, Laurentiu Palcu wrote:
> There are situations when the CFG pins set the chip up for a certain
> mode of operation (ie: pixel mode or tunneling mode), because the HW
> designers decided this way, and we, the users, want to change that. For
> that, add an optional DT property that would allow toggling the
> operation mode from the configured one to the other one.
>
> The driver still only supports tunneling mode, that didn't change.
>
> Signed-off-by: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
> ---
> drivers/media/i2c/max96717.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/media/i2c/max96717.c b/drivers/media/i2c/max96717.c
> index 47a3be195a971..a591ca5d5f44f 100644
> --- a/drivers/media/i2c/max96717.c
> +++ b/drivers/media/i2c/max96717.c
enum gmsl2_mode {
GMSL2_PIXEL_MODE,
GMSL2_MODE_TUNNEL,
};
> @@ -161,6 +161,7 @@ struct max96717_priv {
> struct clk_hw clk_hw;
> struct gpio_chip gpio_chip;
> enum max96717_vpg_mode pattern;
> + bool mode_override;
enum gmsl2_mode mode;
I would prefer to set the mode in an explicit way instead of toggling
the bit in the register.
> struct max96717_fsync_desc fsync;
> };
>
> @@ -1066,6 +1067,14 @@ static int max96717_hw_init(struct max96717_priv *priv)
> return dev_err_probe(dev, ret,
> "Fail to read mipi rx extension");
>
> + if (priv->mode_override) {
if (priv->mode_override && priv->mode == GMSL2_MODE_TUNNEL) {
> +
> +
> + ret = cci_write(priv->regmap, MAX96717_MIPI_RX_EXT11, val, NULL);
ret = cci_update_bits(priv->regmap, MAX96717_MIPI_RX_EXT11, MAX96717_TUN_MODE,
MAX96717_TUN_MODE, NULL);
> + if (ret)
> + return dev_err_probe(dev, ret, "Unable to update operation mode\n");
> + }
> +
In case we are overwriting the mode to tunnel mode then no need to read the EXT11 register.
> if (!(val & MAX96717_TUN_MODE))
> return dev_err_probe(dev, -EOPNOTSUPP,
> "Only supporting tunnel mode");
In fact the driver can works in pixel mode, but since we don't set the "stream id" the
deserializer have to configured with the right one :)
> @@ -1101,6 +1110,9 @@ static int max96717_parse_dt(struct max96717_priv *priv)
>
> priv->mipi_csi2 = vep.bus.mipi_csi2;
>
> + if (fwnode_property_present(dev_fwnode(dev), "maxim,cfg-mode-override"))
> + priv->mode_override = true;
> +
source_fwnode = fwnode_graph_get_endpoint_by_id(dev_fwnode(dev),
MAX96717_PAD_SOURCE, 0, 0);
if (fwnode_property_present(source_fwnode, "maxim,tunnel-mode")) {
priv->mode_override = true;
priv->mode = GMSL2_MODE_TUNNEL;
}
So we can parse the tunnel property from the GMSL port.
> priv->fsync.pin = -1;
> count = fwnode_property_present(dev_fwnode(dev), "maxim,fsync-config");
> if (count > 0) {
Best Regards,
--
Julien
next prev parent reply other threads:[~2025-02-18 15:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 11:29 [PATCH 0/5] media/i2c: max96717: a few changes Laurentiu Palcu
2025-02-07 11:29 ` [PATCH 1/5] media/i2c: max96717: change internal regulator voltage Laurentiu Palcu
2025-02-18 13:14 ` Julien Massot
2025-03-06 8:11 ` Laurentiu Palcu
2025-02-07 11:29 ` [PATCH 2/5] media/i2c: max96717: implement the .get_frame_desc() operation Laurentiu Palcu
2025-02-18 13:29 ` Julien Massot
2025-03-06 8:14 ` Laurentiu Palcu
2025-02-07 11:29 ` [PATCH 3/5] dt-bindings: i2c: maxim,max96717: add new properties Laurentiu Palcu
2025-02-11 18:46 ` Conor Dooley
2025-02-12 17:42 ` Rob Herring
2025-02-12 20:11 ` Conor Dooley
2025-02-12 17:42 ` Rob Herring (Arm)
2025-02-18 13:54 ` Julien Massot
2025-03-06 8:24 ` Laurentiu Palcu
2025-03-13 7:41 ` Julien Massot
2025-02-07 11:29 ` [PATCH 4/5] media/i2c: max96717: add FSYNC support Laurentiu Palcu
2025-02-18 14:46 ` Julien Massot
2025-03-06 8:30 ` Laurentiu Palcu
2025-02-07 11:29 ` [PATCH 5/5] media/i2c: max96717: allow user to override operation mode from DT Laurentiu Palcu
2025-02-18 15:21 ` Julien Massot [this message]
2025-03-06 8:42 ` Laurentiu Palcu
2025-03-13 7:46 ` 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=3c46bbb64e6e9c7b836c3ca82d678e550d1b2ddf.camel@collabora.com \
--to=julien.massot@collabora.com \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--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
all inboxes | Powered by JetHome®