From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Tarang Raval <tarang.raval@siliconsignals.io>,
sakari.ailus@linux.intel.com, mehdi.djait@linux.intel.com
Cc: Himanshu Bhavani <himanshu.bhavani@siliconsignals.io>,
Elgin Perumbilly <elgin.perumbilly@siliconsignals.io>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 14/17] media: i2c: os05b10: add 2-lane support
Date: Sat, 25 Jul 2026 10:38:49 +0300 [thread overview]
Message-ID: <a0deed4a-bcee-467c-8160-e71d8775df8d@linaro.org> (raw)
In-Reply-To: <20260718200912.16001-15-tarang.raval@siliconsignals.io>
On 7/18/26 23:09, Tarang Raval wrote:
> Add support for 2-lane.
>
> Update link-frequency handling to select 750 MHz for 2-lane and 600 MHz for
> 4-lane, and adjust pixel rate computation accordingly. Extend endpoint
> parsing to accept 2 or 4 data lanes.
>
> Signed-off-by: Tarang Raval <tarang.raval@siliconsignals.io>
> ---
> drivers/media/i2c/os05b10.c | 94 ++++++++++++++++++++++++++++---------
> 1 file changed, 71 insertions(+), 23 deletions(-)
>
> diff --git a/drivers/media/i2c/os05b10.c b/drivers/media/i2c/os05b10.c
> index 876186b22f5f..6d91a9660660 100644
> --- a/drivers/media/i2c/os05b10.c
> +++ b/drivers/media/i2c/os05b10.c
> @@ -113,7 +113,8 @@
> #define OS05B10_TRANSPARENT_EFFECT 0xa0
> #define OS05B10_ROLLING_BAR_EFFECT 0xc0
>
> -#define OS05B10_LINK_FREQ_600MHZ (600 * HZ_PER_MHZ)
> +#define OS05B10_LINK_FREQ_4LANE (600 * HZ_PER_MHZ)
> +#define OS05B10_LINK_FREQ_2LANE (750 * HZ_PER_MHZ)
I believe the macro name shall be kept as is, frequency is not specific
to the number of lanes, it's driver implementation/limitation specifics.
>
> static const struct v4l2_rect os05b10_native_area = {
> .top = 0,
> @@ -136,13 +137,7 @@ static const char * const os05b10_supply_name[] = {
> };
>
> static const struct cci_reg_sequence os05b10_common_regs[] = {
> - { OS05B10_REG_PLL_CTRL_01, 0x44 },
> - { OS05B10_REG_PLL_CTRL_03, 0x02 },
> - { OS05B10_REG_PLL_CTRL_05, 0x32 },
> - { OS05B10_REG_PLL_CTRL_06, 0x00 },
> - { OS05B10_REG_PLL_CTRL_25, 0x3b },
> { CCI_REG8(0x3002), 0x21 },
> - { OS05B10_REG_MIPI_SC_CTRL, 0x72 },
> { CCI_REG8(0x301e), 0xb4 },
> { CCI_REG8(0x301f), 0xd0 },
> { CCI_REG8(0x3021), 0x03 },
> @@ -532,6 +527,24 @@ static const struct cci_reg_sequence mode_1280_720_regs[] = {
> { CCI_REG8(0x4837), 0x0d },
> };
>
> +static const struct cci_reg_sequence os05b10_2lane_regs[] = {
> + { OS05B10_REG_PLL_CTRL_01, 0x44 },
> + { OS05B10_REG_PLL_CTRL_03, 0x02 },
> + { OS05B10_REG_PLL_CTRL_05, 0x64 },
> + { OS05B10_REG_PLL_CTRL_06, 0x00 },
> + { OS05B10_REG_PLL_CTRL_25, 0x3b },
> + { OS05B10_REG_MIPI_SC_CTRL, OS05B10_2_LANE_MODE },
> +};
> +
> +static const struct cci_reg_sequence os05b10_4lane_regs[] = {
> + { OS05B10_REG_PLL_CTRL_01, 0x44 },
> + { OS05B10_REG_PLL_CTRL_03, 0x02 },
> + { OS05B10_REG_PLL_CTRL_05, 0x32 },
> + { OS05B10_REG_PLL_CTRL_06, 0x00 },
> + { OS05B10_REG_PLL_CTRL_25, 0x3b },
> + { OS05B10_REG_MIPI_SC_CTRL, OS05B10_4_LANE_MODE },
> +};
> +
> struct os05b10 {
> struct device *dev;
> struct regmap *cci;
> @@ -650,8 +663,12 @@ static const struct os05b10_mode supported_modes_10bit[] = {
> },
> };
>
> -static const s64 link_frequencies[] = {
> - OS05B10_LINK_FREQ_600MHZ,
> +static const s64 link_frequencies_4lane[] = {
> + OS05B10_LINK_FREQ_4LANE,
> +};
> +
> +static const s64 link_frequencies_2lane[] = {
> + OS05B10_LINK_FREQ_2LANE,
> };
Please just use macro with frequency in its name, or plainly use the intended
frequencies here.
>
> static const u32 os05b10_mbus_codes[] = {
> @@ -838,7 +855,9 @@ static int os05b10_enum_mbus_code(struct v4l2_subdev *sd,
> static u64 os05b10_pixel_rate(struct os05b10 *os05b10,
> const struct os05b10_mode *mode)
> {
> - u64 link_freq = link_frequencies[os05b10->link_freq_index];
> + u64 link_freq = (os05b10->data_lanes == 2) ?
> + link_frequencies_2lane[os05b10->link_freq_index] :
> + link_frequencies_4lane[os05b10->link_freq_index];
> u64 pixel_rate = div_u64(link_freq * 2 * os05b10->data_lanes, mode->bpp);
>
> dev_dbg(os05b10->dev,
> @@ -983,6 +1002,17 @@ static int os05b10_enable_streams(struct v4l2_subdev *sd,
> ret = pm_runtime_resume_and_get(os05b10->dev);
> if (ret < 0)
> return ret;
> + /* Set pll & mipi lane configuration */
> + if (os05b10->data_lanes == 2)
> + cci_multi_reg_write(os05b10->cci, os05b10_2lane_regs,
> + ARRAY_SIZE(os05b10_2lane_regs), &ret);
> + else
> + cci_multi_reg_write(os05b10->cci, os05b10_4lane_regs,
> + ARRAY_SIZE(os05b10_4lane_regs), &ret);
> + if (ret) {
> + dev_err(os05b10->dev, "failed to write pll & mipi lane registers\n");
> + goto err_rpm_put;
> + }
>
> /* Write common registers */
> ret = cci_multi_reg_write(os05b10->cci, os05b10_common_regs,
> @@ -1195,22 +1225,39 @@ static int os05b10_parse_endpoint(struct os05b10 *os05b10)
> if (ret)
> return ret;
>
> - if (bus_cfg.bus.mipi_csi2.num_data_lanes != 4) {
> + if (bus_cfg.bus.mipi_csi2.num_data_lanes != 4 &&
> + bus_cfg.bus.mipi_csi2.num_data_lanes != 2) {
> ret = dev_err_probe(os05b10->dev, -EINVAL,
> - "only 4 data lanes are supported\n");
> + "4 and 2 data lanes are supported\n");
> goto error_out;
> }
>
> os05b10->data_lanes = bus_cfg.bus.mipi_csi2.num_data_lanes;
>
> - ret = v4l2_link_freq_to_bitmap(os05b10->dev, bus_cfg.link_frequencies,
> - bus_cfg.nr_of_link_frequencies,
> - link_frequencies,
> - ARRAY_SIZE(link_frequencies),
> - &link_freq_bitmap);
> - if (ret) {
> - dev_err(os05b10->dev, "only 600MHz frequency is available\n");
> - goto error_out;
> + if (os05b10->data_lanes == 2) {
> + ret = v4l2_link_freq_to_bitmap(os05b10->dev,
> + bus_cfg.link_frequencies,
> + bus_cfg.nr_of_link_frequencies,
> + link_frequencies_2lane,
> + ARRAY_SIZE(link_frequencies_2lane),
> + &link_freq_bitmap);
> + if (ret) {
> + dev_err(os05b10->dev,
> + "For 2 lane 750MHz frequency is available\n");
> + goto error_out;
> + }
> + } else {
> + ret = v4l2_link_freq_to_bitmap(os05b10->dev,
> + bus_cfg.link_frequencies,
> + bus_cfg.nr_of_link_frequencies,
> + link_frequencies_4lane,
> + ARRAY_SIZE(link_frequencies_4lane),
> + &link_freq_bitmap);
> + if (ret) {
> + dev_err(os05b10->dev,
> + "For 4 lane 600MHz frequency is available\n");
> + goto error_out;
> + }
> }
>
> os05b10->link_freq_index = __ffs(link_freq_bitmap);
> @@ -1240,10 +1287,11 @@ static int os05b10_init_controls(struct os05b10 *os05b10)
>
> os05b10->link_freq = v4l2_ctrl_new_int_menu(ctrl_hdlr, &os05b10_ctrl_ops,
> V4L2_CID_LINK_FREQ,
> - ARRAY_SIZE(link_frequencies) - 1,
> + ARRAY_SIZE(link_frequencies_4lane) - 1,
> os05b10->link_freq_index,
> - link_frequencies);
> -
> + (os05b10->data_lanes == 2) ?
> + link_frequencies_2lane :
> + link_frequencies_4lane);
> if (os05b10->link_freq)
> os05b10->link_freq->flags |= V4L2_CTRL_FLAG_READ_ONLY;
>
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2026-07-25 7:38 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 20:08 [PATCH v3 00/17] media: i2c: os05b10: Refactor driver and Add new features Tarang Raval
2026-07-18 20:08 ` [PATCH v3 01/17] media: i2c: os05b10: Use pm_runtime_get_if_active() when applying controls Tarang Raval
2026-07-22 5:58 ` Jai Luthra
2026-07-24 6:47 ` Tarang Raval
2026-07-18 20:08 ` [PATCH v3 02/17] media: i2c: os05b10: drop unused group-hold programming Tarang Raval
2026-07-18 20:08 ` [PATCH v3 03/17] media: i2c: os05b10: add register definitions and use them in init table Tarang Raval
2026-07-21 17:25 ` Mehdi Djait
2026-07-24 13:09 ` Vladimir Zapolskiy
2026-07-18 20:08 ` [PATCH v3 04/17] media: i2c: os05b10: split common and mode-specific init registers Tarang Raval
2026-07-21 17:40 ` Mehdi Djait
2026-07-24 13:15 ` Vladimir Zapolskiy
2026-07-18 20:08 ` [PATCH v3 05/17] media: i2c: os05b10: add V4L2 digital gain control Tarang Raval
2026-07-24 13:19 ` Vladimir Zapolskiy
2026-07-24 14:15 ` Tarang Raval
2026-07-18 20:08 ` [PATCH v3 06/17] media: i2c: os05b10: Add H/V flip support Tarang Raval
2026-07-21 17:43 ` Mehdi Djait
2026-07-22 5:51 ` Jai Luthra
2026-07-24 7:01 ` Tarang Raval
2026-07-24 13:27 ` Vladimir Zapolskiy
2026-07-18 20:08 ` [PATCH v3 07/17] media: i2c: os05b10: Add test pattern options Tarang Raval
2026-07-21 17:50 ` Mehdi Djait
2026-07-24 13:43 ` Vladimir Zapolskiy
2026-07-18 20:08 ` [PATCH v3 08/17] media: i2c: os05b10: add 12-bit RAW mode support Tarang Raval
2026-07-24 14:08 ` Vladimir Zapolskiy
2026-07-24 14:30 ` Tarang Raval
2026-07-24 15:03 ` Vladimir Zapolskiy
2026-07-18 20:09 ` [PATCH v3 09/17] media: i2c: os05b10: update pixel rate on 10/12-bit mode switch Tarang Raval
2026-07-22 6:17 ` Jai Luthra
2026-07-22 6:19 ` Jai Luthra
2026-07-24 9:08 ` Tarang Raval
2026-07-25 7:26 ` Vladimir Zapolskiy
2026-07-18 20:09 ` [PATCH v3 10/17] media: i2c: os05b10: Add 1080p and 2x2 binning 720p modes Tarang Raval
2026-07-22 6:05 ` Jai Luthra
2026-07-24 6:44 ` Tarang Raval
2026-07-18 20:09 ` [PATCH v3 11/17] media: i2c: os05b10: keep vblank and exposure range in sync on mode switch Tarang Raval
2026-07-25 7:30 ` Vladimir Zapolskiy
2026-07-18 20:09 ` [PATCH v3 12/17] media: i2c: os05b10: Update active format before adjusting framing controls Tarang Raval
2026-07-25 7:32 ` Vladimir Zapolskiy
2026-07-18 20:09 ` [PATCH v3 13/17] media: i2c: os05b10: Rename vmax variable in VBLANK control Tarang Raval
2026-07-25 7:33 ` Vladimir Zapolskiy
2026-07-18 20:09 ` [PATCH v3 14/17] media: i2c: os05b10: add 2-lane support Tarang Raval
2026-07-25 7:38 ` Vladimir Zapolskiy [this message]
2026-07-18 20:09 ` [PATCH v3 15/17] media: i2c: os05b10: fix negative hblank calculation Tarang Raval
2026-07-22 6:14 ` Jai Luthra
2026-07-24 8:14 ` Tarang Raval
2026-07-18 20:09 ` [PATCH v3 16/17] media: i2c: os05b10: Enable runtime PM autosuspend Tarang Raval
2026-07-22 6:08 ` Jai Luthra
2026-07-24 7:02 ` Tarang Raval
2026-07-24 9:58 ` Jai Luthra
2026-07-18 20:09 ` [PATCH v3 17/17] media: i2c: os05b10: remove unused control fields, simplify error handling Tarang Raval
2026-07-25 11:33 ` Vladimir Zapolskiy
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=a0deed4a-bcee-467c-8160-e71d8775df8d@linaro.org \
--to=vladimir.zapolskiy@linaro.org \
--cc=elgin.perumbilly@siliconsignals.io \
--cc=himanshu.bhavani@siliconsignals.io \
--cc=hverkuil+cisco@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tarang.raval@siliconsignals.io \
/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®