linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, jacopo@jmondi.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: hook up camera on px30-evb
Date: Fri, 03 Sep 2021 15:13:44 +0200	[thread overview]
Message-ID: <2431927.xZuKtqe2JJ@diego> (raw)
In-Reply-To: <20210830141318.66744-2-heiko@sntech.de>

Am Montag, 30. August 2021, 16:13:18 CEST schrieb Heiko Stuebner:
> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>

Note to self: missing patch description, make it something like:

Enable the isp and csi phy on px30-evb and connect it to the board's
ov5695 camera.


> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> ---
>  arch/arm64/boot/dts/rockchip/px30-evb.dts | 52 +++++++++++++++++++++++
>  1 file changed, 52 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/rockchip/px30-evb.dts b/arch/arm64/boot/dts/rockchip/px30-evb.dts
> index c1ce9c295e5b..848bc39cf86a 100644
> --- a/arch/arm64/boot/dts/rockchip/px30-evb.dts
> +++ b/arch/arm64/boot/dts/rockchip/px30-evb.dts
> @@ -114,6 +114,10 @@ &cpu3 {
>  	cpu-supply = <&vdd_arm>;
>  };
>  
> +&csi_dphy {
> +	status = "okay";
> +};
> +
>  &display_subsystem {
>  	status = "okay";
>  };
> @@ -428,6 +432,36 @@ sensor@4c {
>  	};
>  };
>  
> +&i2c2 {
> +	status = "okay";
> +
> +	clock-frequency = <100000>;
> +
> +	/* These are relatively safe rise/fall times; TODO: measure */
> +	i2c-scl-falling-time-ns = <50>;
> +	i2c-scl-rising-time-ns = <300>;
> +
> +	ov5695: ov5695@36 {
> +		compatible = "ovti,ov5695";
> +		reg = <0x36>;
> +		avdd-supply = <&vcc2v8_dvp>;
> +		clocks = <&cru SCLK_CIF_OUT>;
> +		clock-names = "xvclk";
> +		dvdd-supply = <&vcc1v5_dvp>;
> +		dovdd-supply = <&vcc1v8_dvp>;
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&cif_clkout_m0>;
> +		reset-gpios = <&gpio2 14 GPIO_ACTIVE_LOW>;
> +
> +		port {
> +			ucam_out: endpoint {
> +				remote-endpoint = <&mipi_in_ucam>;
> +				data-lanes = <1 2>;
> +			};
> +		};
> +	};
> +};
> +
>  &i2s1_2ch {
>  	status = "okay";
>  };
> @@ -443,6 +477,24 @@ &io_domains {
>  	vccio6-supply = <&vccio_flash>;
>  };
>  
> +&isp {
> +	status = "okay";
> +
> +	ports {
> +		port@0 {
> +			mipi_in_ucam: endpoint@0 {
> +				reg = <0>;
> +				data-lanes = <1 2>;
> +				remote-endpoint = <&ucam_out>;
> +			};
> +		};
> +	};
> +};
> +
> +&isp_mmu {
> +	status = "okay";
> +};
> +
>  &pinctrl {
>  	headphone {
>  		hp_det: hp-det {
> 





  reply	other threads:[~2021-09-03 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 14:13 [PATCH 1/2] arm64: dts: rockchip: add isp node for px30 Heiko Stuebner
2021-08-30 14:13 ` [PATCH 2/2] arm64: dts: rockchip: hook up camera on px30-evb Heiko Stuebner
2021-09-03 13:13   ` Heiko Stübner [this message]
2021-09-20 14:28 ` [PATCH 1/2] arm64: dts: rockchip: add isp node for px30 Heiko Stuebner

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=2431927.xZuKtqe2JJ@diego \
    --to=heiko@sntech.de \
    --cc=jacopo@jmondi.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.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).