linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Inbaraj E <inbaraj.e@samsung.com>,
	mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, s.nawrocki@samsung.com,
	s.hauer@pengutronix.de, shawnguo@kernel.org,
	cw00.choi@samsung.com, rmfrfs@gmail.com,
	laurent.pinchart@ideasonboard.com, martink@posteo.de,
	mchehab@kernel.org, linux-fsd@tesla.com, will@kernel.org,
	catalin.marinas@arm.com, pankaj.dubey@samsung.com,
	shradha.t@samsung.com, ravi.patel@samsung.com
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, alim.akhtar@samsung.com,
	linux-samsung-soc@vger.kernel.org, kernel@puri.sm,
	kernel@pengutronix.de, festevam@gmail.com,
	linux-media@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 04/12] arm64: dts: fsd: Add CSI nodes
Date: Mon, 18 Aug 2025 10:26:34 +0200	[thread overview]
Message-ID: <1919de68-99ea-47f7-b3d2-cae4611f9c52@kernel.org> (raw)
In-Reply-To: <20250814140943.22531-5-inbaraj.e@samsung.com>

On 14/08/2025 16:09, Inbaraj E wrote:
> There is a csi dma and csis interface that bundles together to allow

CSI DMA?
What is CSIS?

> csi2 capture.

CSI2?

> 
> Signed-off-by: Inbaraj E <inbaraj.e@samsung.com>
> ---
>  arch/arm64/boot/dts/tesla/fsd-evb.dts |  96 +++++
>  arch/arm64/boot/dts/tesla/fsd.dtsi    | 552 ++++++++++++++++++++++++++
>  2 files changed, 648 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/tesla/fsd-evb.dts b/arch/arm64/boot/dts/tesla/fsd-evb.dts
> index 9ff22e1c8723..dcc9a138cdb9 100644
> --- a/arch/arm64/boot/dts/tesla/fsd-evb.dts
> +++ b/arch/arm64/boot/dts/tesla/fsd-evb.dts
> @@ -130,3 +130,99 @@ &serial_0 {
>  &ufs {
>  	status = "okay";
>  };
> +
> +&mipicsis0 {
> +	status = "okay";
> +};
> +
> +&mipicsis1 {
> +	status = "okay";
> +};
> +
> +&mipicsis2 {
> +	status = "okay";
> +};
> +
> +&mipicsis3 {
> +	status = "okay";
> +};
> +
> +&mipicsis4 {
> +	status = "okay";
> +};
> +
> +&mipicsis5 {
> +	status = "okay";
> +};
> +
> +&mipicsis6 {
> +	status = "okay";
> +};
> +
> +&mipicsis7 {
> +	status = "okay";
> +};
> +
> +&mipicsis8 {
> +	status = "okay";
> +};
> +
> +&mipicsis9 {
> +	status = "okay";
> +};
> +
> +&mipicsis10 {
> +	status = "okay";
> +};
> +
> +&mipicsis11 {
> +	status = "okay";
> +};
> +
> +&csis0 {
> +	status = "okay";
> +};
> +
> +&csis1 {
> +	status = "okay";
> +};
> +
> +&csis2 {
> +	status = "okay";
> +};
> +
> +&csis3 {
> +	status = "okay";
> +};
> +
> +&csis4 {
> +	status = "okay";
> +};
> +
> +&csis5 {
> +	status = "okay";
> +};
> +
> +&csis6 {
> +	status = "okay";
> +};
> +
> +&csis7 {
> +	status = "okay";
> +};
> +
> +&csis8 {
> +	status = "okay";
> +};
> +
> +&csis9 {
> +	status = "okay";
> +};
> +
> +&csis10 {
> +	status = "okay";
> +};
> +
> +&csis11 {
> +	status = "okay";
> +};
> diff --git a/arch/arm64/boot/dts/tesla/fsd.dtsi b/arch/arm64/boot/dts/tesla/fsd.dtsi
> index a5ebb3f9b18f..a83503e9c502 100644
> --- a/arch/arm64/boot/dts/tesla/fsd.dtsi
> +++ b/arch/arm64/boot/dts/tesla/fsd.dtsi
> @@ -493,6 +493,558 @@ clock_mfc: clock-controller@12810000 {
>  			clock-names = "fin_pll";
>  		};
>  
> +		mipicsis0: mipi-csis@12640000 {

Messed ordering. See DTS coding style.

Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation

What is csis?

> +			compatible = "tesla,fsd-mipi-csi2";
> +			reg = <0x0 0x12640000 0x0 0x124>;
> +			interrupts = <GIC_SPI 6 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clock_csi CAM_CSI0_0_IPCLKPORT_I_ACLK>,
> +				<&clock_csi CAM_CSI0_0_IPCLKPORT_I_PCLK>;
> +			clock-names = "aclk", "pclk";
> +			samsung,syscon-csis = <&sysreg_cam 0x40c>;
> +			status = "disabled";
> +
> +			ports {
> +				#address-cells = <1>;
> +				#size-cells = <0>;
> +
> +				port@0 {
> +					reg = <0>;
> +				};
> +
> +				port@1 {
> +					reg = <1>;
> +
> +					mipi_csis_0_out: endpoint {
> +						remote-endpoint = <&csis_in_0>;
> +					};
> +				};
> +			};
> +		};
> +
> +		csis0: csis@12641000 {
> +			compatible = "tesla,fsd-csis-media";
> +			reg = <0x0 0x12641000 0x0 0x44c>;
> +			interrupts = <GIC_SPI 6 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clock_csi CAM_CSI0_0_IPCLKPORT_I_ACLK>,
> +				<&clock_csi CAM_CSI0_0_IPCLKPORT_I_PCLK>,
> +				<&clock_csi CAM_CSI_PLL>;
> +			clock-names = "aclk", "pclk", "pll";
> +			iommus = <&smmu_isp 0x0 0x0>;
> +			status = "disabled";
> +
> +			port {
> +				csis_in_0: endpoint {
> +					remote-endpoint = <&mipi_csis_0_out>;
> +				};
> +			};
> +		};
> +
> +		mipicsis1: mipi-csis@12650000 {
> +			compatible = "tesla,fsd-mipi-csi2";
> +			reg = <0x0 0x12650000 0x0 0x124>;
> +			interrupts = <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clock_csi CAM_CSI0_1_IPCLKPORT_I_ACLK>,
> +				<&clock_csi CAM_CSI0_1_IPCLKPORT_I_PCLK>;
> +			clock-names = "aclk", "pclk";
> +			samsung,syscon-csis = <&sysreg_cam 0x40c>;
> +			status = "disabled";
> +
> +			ports {
> +				#address-cells = <1>;
> +				#size-cells = <0>;
> +
> +				port@0 {
> +					reg = <0>;
> +				};
> +
> +				port@1 {
> +					reg = <1>;
> +
> +					mipi_csis_1_out: endpoint {
> +						remote-endpoint = <&csis_in_1>;
> +					};
> +				};
> +			};
> +		};
> +
> +		csis1: csis@12651000 {
> +			compatible = "tesla,fsd-csis-media";
> +			reg = <0x0 0x12651000 0x0 0x44c>;
> +			interrupts = <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clock_csi CAM_CSI0_1_IPCLKPORT_I_ACLK>,
> +				<&clock_csi CAM_CSI0_1_IPCLKPORT_I_PCLK>,
> +				<&clock_csi CAM_CSI_PLL>;
> +			clock-names = "aclk", "pclk", "pll";
> +			iommus = <&smmu_isp 0x0 0x0>;
> +			status = "disabled";
> +
> +			port {
> +				csis_in_1: endpoint {
> +					remote-endpoint = <&mipi_csis_1_out>;
> +				};
> +			};
> +		};
> +
> +		mipicsis2: mipi-csis@12660000 {
> +			compatible = "tesla,fsd-mipi-csi2";
> +			reg = <0x0 0x12660000 0x0 0x124>;
> +			interrupts = <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clock_csi CAM_CSI0_2_IPCLKPORT_I_ACLK>,
> +				<&clock_csi CAM_CSI0_2_IPCLKPORT_I_PCLK>;
> +			clock-names = "aclk", "pclk";
> +			samsung,syscon-csis = <&sysreg_cam 0x40c>;
> +			status = "disabled";
> +
> +			ports {
> +				#address-cells = <1>;
> +				#size-cells = <0>;
> +
> +				port@0 {
> +					reg = <0>;
> +				};
> +
> +				port@1 {
> +					reg = <1>;
> +
> +					mipi_csis_2_out: endpoint {
> +						remote-endpoint = <&csis_in_2>;
> +					};
> +				};
> +			};
> +		};
> +
> +		csis2: csis@12661000 {


What is CSIS? Seems like copy paste from other Samsung code, but isn't
this just CSI?

What is the meaning of this CSIS acronym?


Best regards,
Krzysztof

  reply	other threads:[~2025-08-18  8:26 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250814140956epcas5p480aa24441933523484da5c241a201d3c@epcas5p4.samsung.com>
2025-08-14 14:09 ` [PATCH v2 00/12] Add FSD CSI support Inbaraj E
     [not found]   ` <CGME20250814141003epcas5p167e0a3d0ecc52fd8af17151cdddd031a@epcas5p1.samsung.com>
2025-08-14 14:09     ` [PATCH v2 01/12] dt-bindings: clock: Add CAM_CSI clock macro for FSD Inbaraj E
2025-08-18  8:47       ` (subset) " Krzysztof Kozlowski
     [not found]   ` <CGME20250814141009epcas5p153e4aacfc1ead3db8c9bb647c6e5c7c4@epcas5p1.samsung.com>
2025-08-14 14:09     ` [PATCH v2 02/12] clk: samsung: fsd: Add clk id for PCLK and PLL in CAM_CSI block Inbaraj E
2025-08-18  8:47       ` (subset) " Krzysztof Kozlowski
     [not found]   ` <CGME20250814141014epcas5p410d41ede7e8ae4f3cf8db6d041d03946@epcas5p4.samsung.com>
2025-08-14 14:09     ` [PATCH v2 03/12] dt-bindings: media: nxp: Add support for FSD SoC Inbaraj E
2025-08-18  8:24       ` Krzysztof Kozlowski
2025-08-22 13:39         ` Inbaraj E
2025-08-22 13:50           ` Krzysztof Kozlowski
2025-08-22 14:00             ` Inbaraj E
2025-08-23 15:37               ` Krzysztof Kozlowski
2025-08-25 12:50                 ` Inbaraj E
     [not found]   ` <CGME20250814141019epcas5p2f957b934d5b60d4649cf9c6abd6969d5@epcas5p2.samsung.com>
2025-08-14 14:09     ` [PATCH v2 04/12] arm64: dts: fsd: Add CSI nodes Inbaraj E
2025-08-18  8:26       ` Krzysztof Kozlowski [this message]
2025-08-22 13:57         ` Inbaraj E
2025-08-23 15:39           ` Krzysztof Kozlowski
2025-08-25 13:05             ` Inbaraj E
2025-08-26  8:36               ` Krzysztof Kozlowski
2025-08-26 10:08                 ` Inbaraj E
2025-08-26 11:43                 ` Laurent Pinchart
     [not found]   ` <CGME20250814141025epcas5p2b226c4eaab5d60d0e95f684e2ef930f2@epcas5p2.samsung.com>
2025-08-14 14:09     ` [PATCH v2 05/12] media: imx-mipi-csis: Move clk to mipi_csis_info structure Inbaraj E
2025-08-18  9:21       ` Laurent Pinchart
2025-08-23 13:11         ` Inbaraj E
     [not found]   ` <CGME20250814141030epcas5p45a75274697463bbca9cab12f776a4e8c@epcas5p4.samsung.com>
2025-08-14 14:09     ` [PATCH v2 06/12] media: imx-mipi-csis: Move irq flag and handler " Inbaraj E
     [not found]   ` <CGME20250814141036epcas5p1fc02cea3f97534303673eb8453b6a18f@epcas5p1.samsung.com>
2025-08-14 14:09     ` [PATCH v2 07/12] media: imx-mipi-csis: Add support to configure specific vc Inbaraj E
2025-08-18  9:33       ` Laurent Pinchart
2025-08-23 13:29         ` Inbaraj E
     [not found]   ` <CGME20250814141041epcas5p2b281659391a8e45c95e8db21d9867f98@epcas5p2.samsung.com>
2025-08-14 14:09     ` [PATCH v2 08/12] media: imx-mipi-csis: Add support to dump all vc regs Inbaraj E
2025-08-18  9:30       ` Laurent Pinchart
2025-08-23 13:15         ` Inbaraj E
     [not found]   ` <CGME20250814141046epcas5p3fd09b7e4ab34f521cf5ab548c41fb1d2@epcas5p3.samsung.com>
2025-08-14 14:09     ` [PATCH v2 09/12] media: imx-mipi-csis: Add support for FSD CSI Rx Inbaraj E
     [not found]   ` <CGME20250814141051epcas5p14dccee388087372973988aeebcb872cf@epcas5p1.samsung.com>
2025-08-14 14:09     ` [PATCH v2 10/12] dt-bindings: media: fsd: Document CSIS DMA controller Inbaraj E
2025-08-18  8:29       ` Krzysztof Kozlowski
2025-08-23  1:54         ` Inbaraj E
2025-08-18  8:45       ` Krzysztof Kozlowski
2025-08-23  2:39         ` Inbaraj E
2025-08-23 15:32           ` Krzysztof Kozlowski
2025-08-25 12:01             ` Inbaraj E
2025-08-25 12:25               ` Krzysztof Kozlowski
2025-08-24 21:15         ` Laurent Pinchart
2025-08-25  7:34           ` Krzysztof Kozlowski
     [not found]   ` <CGME20250814141057epcas5p21ca33641e42164886dc1bf404237876d@epcas5p2.samsung.com>
2025-08-14 14:09     ` [PATCH v2 11/12] arm64: defconfig: Enable FSD CSIS DMA driver Inbaraj E
2025-08-18  8:32       ` Krzysztof Kozlowski
2025-08-23  2:05         ` Inbaraj E
2025-08-23 15:31           ` Krzysztof Kozlowski
2025-08-25 11:54             ` Inbaraj E
     [not found]   ` <CGME20250814141103epcas5p14516cbe45c21d28ba9e231da99940aa1@epcas5p1.samsung.com>
2025-08-14 14:09     ` [PATCH v2 12/12] media: fsd-csis: Add support for FSD CSIS DMA Inbaraj E
2025-08-18  8:49       ` Krzysztof Kozlowski
2025-08-23 11:49         ` Inbaraj E
2025-08-23 15:34           ` Krzysztof Kozlowski
2025-08-25 12:46             ` Inbaraj E
2025-08-23 11:59         ` Inbaraj E
2025-08-18  8:22   ` [PATCH v2 00/12] Add FSD CSI support Krzysztof Kozlowski
2025-08-22 13:16     ` Inbaraj E

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=1919de68-99ea-47f7-b3d2-cae4611f9c52@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=inbaraj.e@samsung.com \
    --cc=kernel@pengutronix.de \
    --cc=kernel@puri.sm \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-fsd@tesla.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=martink@posteo.de \
    --cc=mchehab@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=pankaj.dubey@samsung.com \
    --cc=ravi.patel@samsung.com \
    --cc=rmfrfs@gmail.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=s.nawrocki@samsung.com \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=shradha.t@samsung.com \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).