From: Mathis Foerst <mathis.foerst@mt.com>
To: linux-kernel@vger.kernel.org
Cc: Mathis Foerst <mathis.foerst@mt.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
manuel.traut@mt.com, mathis.foerst@zuehlke.com
Subject: [PATCH v2 2/7] media: mt9m114: Add get_mbus_config
Date: Tue, 4 Mar 2025 11:36:42 +0100 [thread overview]
Message-ID: <20250304103647.34235-3-mathis.foerst@mt.com> (raw)
In-Reply-To: <20250304103647.34235-1-mathis.foerst@mt.com>
The i.MX6 camera frameworks requires get_mbus_config to be implemented.
See [0].
[0] drivers/staging/media/imx/imx-media-csi.c - line 211..216
Signed-off-by: Mathis Foerst <mathis.foerst@mt.com>
---
drivers/media/i2c/mt9m114.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/drivers/media/i2c/mt9m114.c b/drivers/media/i2c/mt9m114.c
index 5f0b0ad8f885..fa64d6d315a1 100644
--- a/drivers/media/i2c/mt9m114.c
+++ b/drivers/media/i2c/mt9m114.c
@@ -1977,6 +1977,24 @@ static int mt9m114_ifp_registered(struct v4l2_subdev *sd)
v4l2_device_unregister_subdev(&sensor->pa.sd);
return ret;
}
+ return 0;
+}
+
+static int mt9m114_ifp_get_mbus_config(struct v4l2_subdev *sd,
+ unsigned int pad,
+ struct v4l2_mbus_config *cfg)
+{
+ struct mt9m114 *sensor = ifp_to_mt9m114(sd);
+
+ if (sensor->bus_cfg.bus_type == V4L2_MBUS_CSI2_DPHY) {
+ cfg->type = V4L2_MBUS_CSI2_DPHY;
+ } else {
+ cfg->type = V4L2_MBUS_PARALLEL;
+ cfg->bus.parallel.flags = V4L2_MBUS_MASTER |
+ V4L2_MBUS_PCLK_SAMPLE_RISING |
+ V4L2_MBUS_DATA_ACTIVE_HIGH;
+ cfg->bus.parallel.bus_width = 8;
+ }
return 0;
}
@@ -1993,6 +2011,7 @@ static const struct v4l2_subdev_pad_ops mt9m114_ifp_pad_ops = {
.set_fmt = mt9m114_ifp_set_fmt,
.get_selection = mt9m114_ifp_get_selection,
.set_selection = mt9m114_ifp_set_selection,
+ .get_mbus_config = mt9m114_ifp_get_mbus_config,
.get_frame_interval = mt9m114_ifp_get_frame_interval,
.set_frame_interval = mt9m114_ifp_set_frame_interval,
};
--
2.34.1
next prev parent reply other threads:[~2025-03-04 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 10:36 [PATCH v2 0/7] MT9M114 driver bugfix and improvements Mathis Foerst
2025-03-04 10:36 ` [PATCH v2 1/7] media: dt-bindings: mt9m114: Add pad-slew-rate DT-binding Mathis Foerst
2025-03-05 7:21 ` Krzysztof Kozlowski
2025-03-04 10:36 ` Mathis Foerst [this message]
2025-03-04 10:36 ` [PATCH v2 3/7] media: mt9m114: Bypass PLL if required Mathis Foerst
2025-03-04 10:36 ` [PATCH v2 4/7] media: mt9m114: Factor out mt9m114_configure_pa Mathis Foerst
2025-03-04 10:36 ` [PATCH v2 5/7] media: mt9m114: Allow set_selection while streaming Mathis Foerst
2025-03-04 10:36 ` [PATCH v2 6/7] media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval Mathis Foerst
2025-03-04 10:36 ` [PATCH v2 7/7] media: mt9m114: Set pad-slew-rate Mathis Foerst
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=20250304103647.34235-3-mathis.foerst@mt.com \
--to=mathis.foerst@mt.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manuel.traut@mt.com \
--cc=mathis.foerst@zuehlke.com \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--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