From: Mathis Foerst <mathis.foerst@mt.com>
To: linux-kernel@vger.kernel.org
Cc: Mathis Foerst <mathis.foerst@mt.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
manuel.traut@mt.com, mathis.foerst@zuehlke.com
Subject: [PATCH v1 0/1] media: imx: csi: Parse link configuration from fw_node
Date: Wed, 5 Mar 2025 12:38:01 +0100 [thread overview]
Message-ID: <20250305113802.897087-1-mathis.foerst@mt.com> (raw)
Hi,
this patch fixes the imx-media-csi driver to work with camera drivers that
do not implement the subdev-pad-operation "get_mbus_format".
It's the follow up of this discussion:
https://lore.kernel.org/linux-media/Z8AoA6WjbXQufqR6@kekkonen.localdomain/
I tested the changes successfully on an i.MX6DL with an MT9M114 and an
MT9V032 camera. They both use the parallel camera interface.
Sadly, I don't have the hardware to test with a MIPI CSI-2 camera.
Best regards,
Mathis Foerst
Mathis Foerst (1):
media: imx: csi: Parse link configuration from fw_node
drivers/staging/media/imx/imx-media-csi.c | 36 ++++++++++++++++++++---
1 file changed, 32 insertions(+), 4 deletions(-)
base-commit: ac9c34d1e45a4c25174ced4fc0cfc33ff3ed08c7
--
2.34.1
next reply other threads:[~2025-03-05 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 11:38 Mathis Foerst [this message]
2025-03-05 11:38 ` [PATCH v1 1/1] media: imx: csi: Parse link configuration from fw_node Mathis Foerst
2025-03-06 16:33 ` Sakari Ailus
2025-03-06 19:07 ` Dan Carpenter
2025-03-06 21:13 ` Sakari Ailus
2025-03-07 13:38 ` Mathis Foerst
2025-03-10 10:25 ` Sakari Ailus
2025-03-14 15:26 ` Mathis Foerst
2025-03-14 15:48 ` Sakari Ailus
2025-03-21 15:28 ` 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=20250305113802.897087-1-mathis.foerst@mt.com \
--to=mathis.foerst@mt.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manuel.traut@mt.com \
--cc=mathis.foerst@zuehlke.com \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=slongerbeam@gmail.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