From: Frank Li <Frank.li@nxp.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Rui Miguel Silva <rmfrfs@gmail.com>,
Martin Kepplinger <martink@posteo.de>,
Purism Kernel Team <kernel@puri.sm>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Eugen Hristev <eugen.hristev@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
Alice Yuan <alice.yuan@nxp.com>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org,
"Guoniu.zhou" <guoniu.zhou@nxp.com>
Subject: Re: [PATCH 5/7] media: nxp: add DesignWare MIPI CSI2 controller driver
Date: Wed, 2 Jul 2025 11:55:35 -0400 [thread overview]
Message-ID: <aGVWd/bo22pPeKVS@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250702093806.GF16835@pendragon.ideasonboard.com>
On Wed, Jul 02, 2025 at 12:38:06PM +0300, Laurent Pinchart wrote:
> Hi Frank,
>
> Thank you for the patch.
>
> On Tue, Jul 01, 2025 at 06:06:10PM -0400, Frank Li wrote:
> > From: "Guoniu.zhou" <guoniu.zhou@nxp.com>
> >
> > Add V4L2 subdev driver for DesignWare MIPI CSI2 controller.
>
> This seems to be at least the third instance of a driver for the CSI-2
> receiver, the first two being
when I read spec, I known it should be used at other SoC. But I just jump
to into this area, not easy to find who use it easily.
> drivers/media/platform/raspberrypi/rp1-cfe/dphy.c and the second one
I think this one is not good abstraction. it should be phy driver, which
use "test" interface to community MIPI phy. I think it'd better create
a bus driver, like test_if, DPHY should be child devices of this test_if.
like
csi2@000 {
...
phys = <&dphy>;
dphy: dphy {
compatible = "...";
}
}
The tough problem is that dwc phy have one kind of combo phy, which
under both dsi and csi controller's test_if.
CSI need config such combophy by DSI test_if. I still have not idea
how to descript this type hardware yet.
> drivers/media/platform/renesas/rcar-csi2.c (the latter seems to support
> multiple CSI-2 receivers).
This is one mixed PHY and controller to one drivers, which is not problem
when use one big MMIO space.
We can create dwc mipi csi common library, let each vendor driver to link
it (dwc pci/usb did this). The issue is that I have not their hardware to
test it.
> drivers/staging/media/imx/imx6-mipi-csi2.c
> seem related too, likely for an old version of the IP.
After we create common dw mipi csi library, we can move this to there.
Frank
>
> Could we please try to avoid code duplication ?
>
> > Signed-off-by: Guoniu.zhou <guoniu.zhou@nxp.com>
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> > MAINTAINERS | 1 +
> > drivers/media/platform/nxp/Kconfig | 11 +
> > drivers/media/platform/nxp/Makefile | 1 +
> > drivers/media/platform/nxp/dwc-mipi-csi2.c | 1675 ++++++++++++++++++++++++++++
>
> This should go to drivers/media/platform/synopsys/
>
> > 4 files changed, 1688 insertions(+)
>
> [snip]
>
> --
> Regards,
>
> Laurent Pinchart
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-07-02 16:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 22:06 [PATCH 0/7] media: add imx93 mipi/controller csi support Frank Li
2025-07-01 22:06 ` [PATCH 1/7] dt-bindings: media: add DW MIPI CSI-2 Host support Frank Li
2025-07-02 6:38 ` Krzysztof Kozlowski
2025-07-01 22:06 ` [PATCH 2/7] dt-bindings: soc: imx-blk-ctrl: add MIPI CSI2 dphy support Frank Li
2025-07-02 6:40 ` Krzysztof Kozlowski
2025-07-02 6:42 ` Krzysztof Kozlowski
2025-07-02 18:02 ` Frank Li
2025-07-02 20:12 ` Krzysztof Kozlowski
2025-07-01 22:06 ` [PATCH 3/7] pmdomain: imx93-blk-ctrl: populate child devices Frank Li
2025-07-02 5:15 ` Alexander Stein
2025-07-01 22:06 ` [PATCH 4/7] phy: freescale: add imx93 MIPI CSI2 DPHY support Frank Li
2025-07-02 5:50 ` Alexander Stein
2025-07-01 22:06 ` [PATCH 5/7] media: nxp: add DesignWare MIPI CSI2 controller driver Frank Li
2025-07-02 6:04 ` Alexander Stein
2025-07-02 6:35 ` Krzysztof Kozlowski
2025-07-02 9:38 ` Laurent Pinchart
2025-07-02 15:55 ` Frank Li [this message]
2025-07-04 2:04 ` Frank Li
2025-07-01 22:06 ` [PATCH NOT MERGE 6/7] arm64: dts: imx93-11x11-evk: add camera related nodes Frank Li
2025-07-01 22:06 ` [PATCH NOT MERGE 7/7] media: i2c: add AP1302 driver from community Frank Li
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=aGVWd/bo22pPeKVS@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alice.yuan@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@linaro.org \
--cc=festevam@gmail.com \
--cc=guoniu.zhou@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=martink@posteo.de \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=peng.fan@nxp.com \
--cc=rmfrfs@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vkoul@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