mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Prahlad Valluru <quic_vvalluru@quicinc.com>, <robh@kernel.org>
Cc: <andersson@kernel.org>, <conor+dt@kernel.org>,
	<devicetree@vger.kernel.org>, <konrad.dybcio@linaro.org>,
	<krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<quic_nankam@quicinc.com>
Subject: Re: [PATCH v2] arm64: dts: qcom: qcs6490-rb3gen2: enable hdmi bridge
Date: Mon, 6 May 2024 12:54:29 -0700	[thread overview]
Message-ID: <55ee8e86-e2eb-4c69-9692-df790454b8d6@quicinc.com> (raw)
In-Reply-To: <20240426142442.7769-1-quic_vvalluru@quicinc.com>



On 4/26/2024 7:24 AM, Prahlad Valluru wrote:
> From: Venkata Prahlad Valluru <quic_vvalluru@quicinc.com>
> 
> Enable lt9611uxc bridge for qcs6490 rb3 gen2 platform.
> 
> Signed-off-by: Prahlad Valluru <quic_vvalluru@quicinc.com>
> ---

Why is there a mismatch between your author name and signed off name?

> v2: Addressed dtschema errors
> 	- Fixed lt9611-irq
> 	- vdd-supply error to be ignored, as it is connected to
> 	  input supply directly, on rb3gen2
> ---
>   arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 86 ++++++++++++++++++++
>   1 file changed, 86 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
> index a085ff5b5fb2..c14d4a4bb3ce 100644
> --- a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
> +++ b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
> @@ -51,6 +51,18 @@
>   			};
>   		};
>   	};
> +	
> +	hdmi-connector {
> +		compatible = "hdmi-connector";
> +		label = "HDMI";

Is label mandatory? Doesn't seem so?

Rest LGTM.

> +		type = "a";
> +
> +		port {
> +			hdmi_con: endpoint {
> +				remote-endpoint = <&lt9611_out>;
> +			};
> +		};
> +	};
>   
>   	reserved-memory {
>   		xbl_mem: xbl@80700000 {
> @@ -530,6 +542,45 @@
>   			   <GCC_WPSS_RSCP_CLK>;
>   };
>   
> +&i2c0 {
> +	clock-frequency = <400000>;
> +	status = "okay";
> +
> +	lt9611_codec: hdmi-bridge@2b {
> +		compatible = "lontium,lt9611uxc";
> +		reg = <0x2b>;
> +
> +		interrupts-extended = <&tlmm 24 IRQ_TYPE_EDGE_FALLING>;
> +		reset-gpios = <&pm7250b_gpios 2 GPIO_ACTIVE_HIGH>;
> +
> +		vcc-supply = <&vreg_l11c_2p8>;
> +
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&lt9611_irq_pin &lt9611_rst_pin>;
> +
> +		ports {
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +
> +			port@0 {
> +				reg = <0>;
> +
> +				lt9611_a: endpoint {
> +					remote-endpoint = <&mdss_dsi0_out>;
> +				};
> +			};
> +
> +			port@2 {
> +				reg = <2>;
> +
> +				lt9611_out: endpoint {
> +					remote-endpoint = <&hdmi_con>;
> +				};
> +			};
> +		};
> +	};
> +};
> +
>   &i2c1 {
>   	status = "okay";
>   
> @@ -602,6 +653,21 @@
>   	status = "okay";
>   };
>   
> +&mdss_dsi {
> +        vdda-supply = <&vreg_l6b_1p2>;
> +        status = "okay";
> +};
> +
> +&mdss_dsi0_out {
> +        remote-endpoint = <&lt9611_a>;
> +        data-lanes = <0 1 2 3>;
> +};
> +
> +&mdss_dsi_phy {
> +        vdds-supply = <&vreg_l10c_0p88>;
> +        status = "okay";
> +};
> +
>   &qupv3_id_0 {
>   	status = "okay";
>   };
> @@ -711,3 +777,23 @@
>   	function = "gpio";
>   	bias-disable;
>   };
> +
> +&pm7250b_gpios {
> +        lt9611_rst_pin: lt9611-rst-state {
> +                pins = "gpio2";
> +                function = "normal";
> +
> +                output-high;
> +                input-disable;
> +                power-source = <0>;
> +        };
> +};
> +
> +&tlmm {
> +        lt9611_irq_pin: lt9611-irq-state {
> +                pins = "gpio24";
> +                function = "gpio";
> +                drive-strength = <8>;
> +                bias-disable;
> +        };
> +};

  reply	other threads:[~2024-05-06 19:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  7:13 [PATCH] " Venkata Prahlad Valluru
2024-04-25 14:51 ` Rob Herring
2024-04-26 14:24   ` [PATCH v2] " Prahlad Valluru
2024-05-06 19:54     ` Abhinav Kumar [this message]
2024-05-06 23:14     ` Bjorn Andersson
2024-05-07 16:30       ` [PATCH v3] " Venkata Prahlad Valluru
2024-05-07 16:35         ` Krzysztof Kozlowski
2024-05-07 19:20           ` Abhinav Kumar
2024-05-08  7:38             ` Krzysztof Kozlowski
2024-05-08  8:13               ` Dmitry Baryshkov
2024-05-09  8:31                 ` Krzysztof Kozlowski
2024-05-08 10:26               ` Prahlad Valluru
2024-05-07 18:43         ` Abhinav Kumar
2024-05-08 10:22       ` [PATCH v2] " Prahlad Valluru
2024-05-08 10:47         ` Dmitry Baryshkov
2024-05-08 14:31       ` Rob Herring (Arm)
2024-05-15 15:04         ` Prahlad Valluru
2024-05-15 15:28           ` Dmitry Baryshkov
2024-05-28 14:11             ` Prahlad Valluru
2024-05-28 14:19             ` [PATCH v4] " Venkata Prahlad Valluru
2024-05-28 15:00               ` Dmitry Baryshkov
2024-05-28 16:24                 ` Prahlad Valluru
2024-05-28 16:33                   ` Dmitry Baryshkov
2024-06-27 21:25               ` Bjorn Andersson

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=55ee8e86-e2eb-4c69-9692-df790454b8d6@quicinc.com \
    --to=quic_abhinavk@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_nankam@quicinc.com \
    --cc=quic_vvalluru@quicinc.com \
    --cc=robh@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

all inboxes | Powered by JetHome®