From: Adam Ford <aford173@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Marco Felsch <m.felsch@pengutronix.de>,
Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-imx@nxp.com, kernel@pengutronix.de,
Shawn Guo <shawnguo@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Xavier Roumegue <xavier.roumegue@oss.nxp.com>
Subject: Re: [PATCH v1 1/2] arm64: dts: imx8mp: Add CSIS DT nodes
Date: Tue, 28 Nov 2023 21:17:51 -0600 [thread overview]
Message-ID: <CAHCN7x+kymRGO2kxvN2=zLiqRjfTc3hdf3VdNVkWjsW3La0bnA@mail.gmail.com> (raw)
In-Reply-To: <20230417055627.16482-2-laurent.pinchart@ideasonboard.com>
On Mon, Apr 17, 2023 at 1:01 AM Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
>
> Add DT nodes for the two CSI-2 receivers of the i.MX8MP.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
Laurent,
Sorry to dig up an old thread, but I have a concern about the clock
ratings and nominal mode vs overdrive mode. I started investigating
the different data sheets amongst the various imx8m[mnp] families to
make the default device trees run at nominal mode while also creating
a separate dtsi file with settings for overdrive so boards who use it
can include them without having to duplicate the clock settings for
everyone who supports overdrive.
> arch/arm64/boot/dts/freescale/imx8mp.dtsi | 60 +++++++++++++++++++++++
> 1 file changed, 60 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> index 2dd60e3252f3..2a374a4c14a2 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> @@ -1239,6 +1239,66 @@ ldb_lvds_ch1: endpoint {
> };
> };
>
> + mipi_csi_0: csi@32e40000 {
> + compatible = "fsl,imx8mp-mipi-csi2", "fsl,imx8mm-mipi-csi2";
> + reg = <0x32e40000 0x10000>;
> + interrupts = <GIC_SPI 17 IRQ_TYPE_LEVEL_HIGH>;
> + clock-frequency = <500000000>;
> + clocks = <&clk IMX8MP_CLK_MEDIA_APB_ROOT>,
> + <&clk IMX8MP_CLK_MEDIA_CAM1_PIX_ROOT>,
> + <&clk IMX8MP_CLK_MEDIA_MIPI_PHY1_REF_ROOT>,
> + <&clk IMX8MP_CLK_MEDIA_AXI_ROOT>;
> + clock-names = "pclk", "wrap", "phy", "axi";
> + assigned-clocks = <&clk IMX8MP_CLK_MEDIA_CAM1_PIX>;
> + assigned-clock-parents = <&clk IMX8MP_SYS_PLL2_1000M>;
> + assigned-clock-rates = <500000000>;
According to Rev 2.1 of the Data sheet (IMX8MPCEC), dated July 2023,
500MHz is listed as single-camera, overdrive mode. Single-camera,
nominal mode is 400MHz, but there is more...
If configured for dual cameras, both CSI can only support up to
266MHz, but we have partially configured both albeit without the
actual camera sensors connected.
> + power-domains = <&media_blk_ctrl IMX8MP_MEDIABLK_PD_MIPI_CSI2_1>;
> + status = "disabled";
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> + };
> +
> + port@1 {
> + reg = <1>;
> + };
> + };
> + };
> +
> + mipi_csi_1: csi@32e50000 {
> + compatible = "fsl,imx8mp-mipi-csi2", "fsl,imx8mm-mipi-csi2";
> + reg = <0x32e50000 0x10000>;
> + interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;
> + clock-frequency = <266000000>;
> + clocks = <&clk IMX8MP_CLK_MEDIA_APB_ROOT>,
> + <&clk IMX8MP_CLK_MEDIA_CAM2_PIX_ROOT>,
> + <&clk IMX8MP_CLK_MEDIA_MIPI_PHY1_REF_ROOT>,
> + <&clk IMX8MP_CLK_MEDIA_AXI_ROOT>;
> + clock-names = "pclk", "wrap", "phy", "axi";
> + assigned-clocks = <&clk IMX8MP_CLK_MEDIA_CAM2_PIX>;
> + assigned-clock-parents = <&clk IMX8MP_SYS_PLL2_1000M>;
> + assigned-clock-rates = <266000000>;
266MHz is correct for dual camera, but in single camera, the second
CSI is capable of 277MHz.
At a minimum, I'd like to fix the overdrive frequency to nominal, but
since we're plumbing in both cameras, I wonder if it would be better
to run both at 266MHz with a note on CSI0 that states it could run at
400 or 500 if the second CSI is disabled and a note on the second CSI
that it could run at 277 when the first one is disabled? What are your
thoughts?
> + power-domains = <&media_blk_ctrl IMX8MP_MEDIABLK_PD_MIPI_CSI2_2>;
> + status = "disabled";
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> + };
> +
> + port@1 {
> + reg = <1>;
> + };
> + };
> + };
> +
> pcie_phy: pcie-phy@32f00000 {
> compatible = "fsl,imx8mp-pcie-phy";
> reg = <0x32f00000 0x10000>;
> --
> Regards,
>
> Laurent Pinchart
>
next prev parent reply other threads:[~2023-11-29 3:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 5:56 [PATCH v1 0/2] arm64: dts: imx8mp: Enable CSIS and ISI in DT Laurent Pinchart
2023-04-17 5:56 ` [PATCH v1 1/2] arm64: dts: imx8mp: Add CSIS DT nodes Laurent Pinchart
2023-04-17 6:50 ` Marco Felsch
2023-04-17 7:41 ` Laurent Pinchart
2023-04-17 8:01 ` Marco Felsch
2023-04-17 8:15 ` Laurent Pinchart
2023-04-17 8:23 ` Marco Felsch
2023-04-17 9:59 ` Alexander Stein
2023-04-17 12:45 ` Adam Ford
2023-04-17 13:15 ` Marco Felsch
2023-07-07 23:55 ` Tim Harvey
2023-11-29 3:17 ` Adam Ford [this message]
2023-11-29 10:55 ` Laurent Pinchart
2023-11-29 20:14 ` Kieran Bingham
2023-11-29 20:55 ` Adam Ford
2023-04-17 5:56 ` [PATCH v1 2/2] arm64: dts: imx8mp: Add ISI DT node Laurent Pinchart
2023-04-17 6:13 ` Alexander Stein
2023-04-18 9:02 ` [PATCH v1 0/2] arm64: dts: imx8mp: Enable CSIS and ISI in DT Paul Elder
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='CAHCN7x+kymRGO2kxvN2=zLiqRjfTc3hdf3VdNVkWjsW3La0bnA@mail.gmail.com' \
--to=aford173@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-media@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=xavier.roumegue@oss.nxp.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;
as well as URLs for NNTP newsgroup(s).