mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, venkata.valluru@oss.qualcomm.com,
	Jessica Zhang <jesszhan0024@gmail.com>
Subject: Re: [PATCH v4 1/2] arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support
Date: Tue, 13 Oct 2026 00:25:49 +0530	[thread overview]
Message-ID: <as0tNQg8AMeEauWT@hu-mdsor-hyd.qualcomm.com> (raw)
In-Reply-To: <3gylobhugzzwngtxwzke2o6almcmjzxrjqefpkmcpjy74baxvh@akzm74tyb2n6>

On Wed, Oct 07, 2026 at 04:40:26PM +0300, Dmitry Baryshkov wrote:
> On Wed, Oct 07, 2026 at 06:21:06PM +0530, Mohit Dsor wrote:
> > Enable the Shikra MDSS display subsystem on the Qualcomm Shikra IQS
> > EVK board and add the Lontium LT9611UXD DSI-to-HDMI bridge node.
> > 
> > The LT9611UXD is connected via I2C (bus 4, address 0x41), powered by
> > a GPIO-controlled 3.3V regulator (PM8150 GPIO4) and an always-on 1.8V
> > rail. Reset is on GPIO76 and interrupt on GPIO85.
> > 
> > The bridge receives DSI output from MDSS and drives an HDMI-A
> > connector, with the link wired as: DPU -> DSI0 -> LT9611UXD -> HDMI.
> > 
> > Regulator and pinctrl labels use generic board-level names
> > (vreg_disp_3p3, bridge_irq_pin, bridge_rst_pin) to decouple them
> > from the bridge chip.
> > 
> > Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
> > ---
> >  arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts | 109 ++++++++++++++++++++++++++++
> >  1 file changed, 109 insertions(+)
> > 
> > +
> > +&i2c4 {
> > +	status = "okay";
> > +
> > +	lt9611uxd: lt9611uxd@41 {
> 
> unused label. rename the node to hdmi-bridge
The label will be required in overlays on top of HDMI so shall we remove it now or add in overlay series ?
> 
> > +		compatible = "lontium,lt9611uxd";
> > +		reg = <0x41>;
> > +		interrupts-extended = <&tlmm 85 IRQ_TYPE_EDGE_FALLING>;
> > +		reset-gpios = <&tlmm 76 GPIO_ACTIVE_LOW>;
> > +		vcc-supply = <&vreg_disp_3p3>;
> > +		vdd-supply = <&pm8150_s4>;
> > +
> > +		pinctrl-0 = <&bridge_irq_pin &bridge_rst_pin>;
> > +		pinctrl-names = "default";
> > +
> > +		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>;
> 
> hdmi_connector_out
Will fix it in next version.
> 
> > +				};
> > +			};
> > +		};
> > +	};
> > +};
> > +
> > @@ -67,6 +160,22 @@ &sdhc_2 {
> >  	status = "okay";
> >  };
> >  
> > +&tlmm {
> > +	bridge_irq_pin: bridge-irq-state {
> > +		pins = "gpio85";
> > +		function = "gpio";
> > +		drive-strength = <2>;
> > +		bias-disable;
> > +	};
> > +
> > +	bridge_rst_pin: bridge-rst-state {
> 
> I think the current recommendation is to sort them by the pin number.
Sure, will sort it accordingly.
> 
> > +		pins = "gpio76";
> > +		function = "gpio";
> > +		drive-strength = <8>;
> > +		bias-disable;
> > +	};
> > +};
> > +
> >  &usb_1_hsphy {
> >  	vdd-supply = <&pm8150_l4>;
> >  	vdda-pll-supply = <&pm8150_l12>;
> > 
> > -- 
> > 2.34.1
> > 
> 
> -- 
> With best wishes
> Dmitry

  reply	other threads:[~2026-10-12 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 12:51 [PATCH v4 0/2] arm64: " Mohit Dsor
2026-10-07 12:51 ` [PATCH v4 1/2] arm64: dts: " Mohit Dsor
2026-10-07 13:40   ` Dmitry Baryshkov
2026-10-12 18:55     ` Mohit Dsor [this message]
2026-10-07 12:51 ` [PATCH v4 2/2] arm64: defconfig: Enable LT9611C bridge driver Mohit Dsor
2026-10-07 13:41   ` Dmitry Baryshkov
2026-10-09 11:50   ` Krzysztof Kozlowski
2026-10-12 18:56     ` Mohit Dsor

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=as0tNQg8AMeEauWT@hu-mdsor-hyd.qualcomm.com \
    --to=mohit.dsor@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=jesszhan0024@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=venkata.valluru@oss.qualcomm.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

all inboxes | Powered by JetHome®