From: Prahlad Valluru <quic_vvalluru@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.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_abhinavk@quicinc.com>, <quic_nankam@quicinc.com>,
<robh@kernel.org>
Subject: Re: [PATCH v4] arm64: dts: qcom: qcs6490-rb3gen2: enable hdmi bridge
Date: Tue, 28 May 2024 21:54:34 +0530 [thread overview]
Message-ID: <20240528162434.GA4578@hu-vvalluru-hyd.qualcomm.com> (raw)
In-Reply-To: <rs7m73yzuvm5rf52tyax57r33iigalplr2z7rrxm7mktdqa3bf@ecapopn7ufho>
On Tue, May 28, 2024 at 06:00:26PM +0300, Dmitry Baryshkov wrote:
> On Tue, May 28, 2024 at 07:49:54PM +0530, Venkata Prahlad Valluru wrote:
> > Rb3Gen2 has a lt9611uxc DSI-to-HDMI bridge on i2c0, with
> > reset gpio from pm7250b gpio2 and irq gpio from tlmm gpio24.
> > Bridge supplies are Vdd connected to input supply directly
> > and vcc to L11c. Enable HDMI output, bridge and corresponding
> > DSI output.
> >
> > Signed-off-by: Venkata Prahlad Valluru <quic_vvalluru@quicinc.com>
> > ---
> > v4: added fixed regulator for vdd
>
> Please don't send new iterations as replies to the previous iteration.
> It might be ignored or mishandled by the tools.
Was trying to have the context of discussion captured. Will add links
to the patchsets in the history, going forward.
>
> >
> > v3: - Updated commit text
> > - Arranged nodes in alphabetical order
> > - Fixed signoff
> > - Fixed drive strength for lt9611_irq_pin
> > - Removed 'label' from hdmi-connector, which is optional
> >
> > 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 | 94 ++++++++++++++++++++
> > 1 file changed, 94 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
> > index a085ff5b5fb2..7f00fca131a2 100644
> > --- a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
> > +++ b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
> > @@ -52,6 +52,25 @@
> > };
> > };
> >
> > + hdmi-connector {
> > + compatible = "hdmi-connector";
> > + type = "a";
> > +
> > + port {
> > + hdmi_con: endpoint {
> > + remote-endpoint = <<9611_out>;
> > + };
> > + };
> > + };
> > +
> > + lt9611_1v2: lt9611-vdd12-regulator {
> > + compatible = "regulator-fixed";
> > + regulator-name = "LT9611_1V2";
>
> Is it the regulator / net name in schematics? Or is it also used by any
> other consumers?
>
VREG_HDMI_OUT_1P2 is the naming in schematic, but i see this naming convention for rb5 based boards.
No other consumers for this.
> > +
> > + regulator-min-microvolt = <1200000>;
> > + regulator-max-microvolt = <1200000>;
> > + };
> > +
> > reserved-memory {
> > xbl_mem: xbl@80700000 {
> > reg = <0x0 0x80700000 0x0 0x100000>;
> > @@ -530,6 +549,46 @@
> > <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>;
> > +
> > + vdd-supply = <<9611_1v2>;
> > + vcc-supply = <&vreg_l11c_2p8>;
> > +
> > + pinctrl-names = "default";
> > + pinctrl-0 = <<9611_irq_pin <9611_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";
> >
> > @@ -587,6 +646,21 @@
> > remote-endpoint = <&usb_dp_qmpphy_dp_in>;
> > };
> >
> > +&mdss_dsi {
> > + vdda-supply = <&vreg_l6b_1p2>;
> > + status = "okay";
> > +};
> > +
> > +&mdss_dsi0_out {
> > + remote-endpoint = <<9611_a>;
> > + data-lanes = <0 1 2 3>;
> > +};
> > +
> > +&mdss_dsi_phy {
> > + vdds-supply = <&vreg_l10c_0p88>;
> > + status = "okay";
> > +};
> > +
> > &mdss_edp {
> > status = "okay";
> > };
> > @@ -711,3 +785,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 = <2>;
> > + bias-disable;
> > + };
> > +};
> > --
> > 2.17.1
> >
>
> --
> With best wishes
> Dmitry
next prev parent reply other threads:[~2024-05-28 16:24 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
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 [this message]
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=20240528162434.GA4578@hu-vvalluru-hyd.qualcomm.com \
--to=quic_vvalluru@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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_abhinavk@quicinc.com \
--cc=quic_nankam@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®