From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Robert Foss <robert.foss@linaro.org>,
agross@kernel.org, bjorn.andersson@linaro.org,
konrad.dybcio@somainline.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robdclark@gmail.com,
quic_abhinavk@quicinc.com, dmitry.baryshkov@linaro.org,
sean@poorly.run, airlied@linux.ie, daniel@ffwll.ch,
quic_kalyant@quicinc.com, swboyd@chromium.org,
angelogioacchino.delregno@somainline.org,
loic.poulain@linaro.org, quic_vpolimer@quicinc.com,
vkoul@kernel.org, dianders@chromium.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org,
Jonathan Marek <jonathan@marek.ca>,
vinod.koul@linaro.org, quic_jesszhan@quicinc.com
Subject: Re: [PATCH v1 9/9] arm64: dts: qcom: sm8350-hdk: Enable lt9611uxc dsi-hdmi bridge
Date: Fri, 28 Oct 2022 18:05:55 -0400 [thread overview]
Message-ID: <408b7b0c-ce30-134e-9b1f-f77c1f03f5c9@linaro.org> (raw)
In-Reply-To: <20221028120812.339100-10-robert.foss@linaro.org>
On 28/10/2022 08:08, Robert Foss wrote:
> The sm8350-hdk ships with the LT9611 UXC DSI/HDMI bridge chip.
>
> In order to toggle the board to enable the HDMI output,
> switch #7 & #8 on the rightmost multi-switch package have
> to be toggled to On.
>
> Signed-off-by: Robert Foss <robert.foss@linaro.org>
> ---
> arch/arm64/boot/dts/qcom/sm8350-hdk.dts | 106 ++++++++++++++++++++++++
> 1 file changed, 106 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm8350-hdk.dts b/arch/arm64/boot/dts/qcom/sm8350-hdk.dts
> index 6e07feb4b3b2..6666b38b58f8 100644
> --- a/arch/arm64/boot/dts/qcom/sm8350-hdk.dts
> +++ b/arch/arm64/boot/dts/qcom/sm8350-hdk.dts
> @@ -20,6 +20,17 @@ chosen {
> stdout-path = "serial0:115200n8";
> };
>
> + hdmi-out {
Generic node names, so hdmi-connector or just connector.
> + compatible = "hdmi-connector";
> + type = "a";
> +
> + port {
> + hdmi_con: endpoint {
> + remote-endpoint = <<9611_out>;
> + };
> + };
> + };
> +
> vph_pwr: vph-pwr-regulator {
> compatible = "regulator-fixed";
> regulator-name = "vph_pwr";
> @@ -29,6 +40,32 @@ vph_pwr: vph-pwr-regulator {
> regulator-always-on;
> regulator-boot-on;
> };
> +
> + lt9611_1v2: lt9611-1v2 {
Node names should be generic.
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
> + compatible = "regulator-fixed";
> + regulator-name = "LT9611_1V2";
> +
> + vin-supply = <&vph_pwr>;
> + regulator-min-microvolt = <1200000>;
> + regulator-max-microvolt = <1200000>;
> + gpio = <&tlmm 49 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> + regulator-boot-on;
> + regulator-always-on;
> + };
> +
> + lt9611_3v3: lt9611-3v3 {
Ditto
> + compatible = "regulator-fixed";
> + regulator-name = "LT9611_3V3";
> +
> + vin-supply = <&vreg_bob>;
> + gpio = <&tlmm 47 GPIO_ACTIVE_HIGH>;
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + enable-active-high;
> + regulator-boot-on;
> + regulator-always-on;
> + };
> };
>
> &adsp {
> @@ -220,6 +257,15 @@ &dispcc {
> &dsi0 {
> status = "okay";
> vdda-supply = <&vreg_l6b_1p2>;
> +
> + ports {
> + port@1 {
> + endpoint {
> + remote-endpoint = <<9611_a>;
> + data-lanes = <0 1 2 3>;
> + };
> + };
> + };
> };
>
> &dsi0_phy {
> @@ -231,6 +277,48 @@ &gpi_dma1 {
> status = "okay";
> };
>
> +&i2c15 {
> + status = "okay";
status is the last property
> + clock-frequency = <400000>;
> +
> + lt9611_codec: hdmi-bridge@2b {
> + compatible = "lontium,lt9611uxc";
> + reg = <0x2b>;
> + status = "okay";
Why status?
> +
> + interrupts-extended = <&tlmm 50 IRQ_TYPE_EDGE_FALLING>;
> + reset-gpios = <&tlmm 48 GPIO_ACTIVE_HIGH>;
> +
> + vdd-supply = <<9611_1v2>;
> + vcc-supply = <<9611_3v3>;
> +
> + 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 = <&dsi0_out>;
> + };
> + };
> +
> + port@2 {
> + reg = <2>;
> +
> + lt9611_out: endpoint {
> + remote-endpoint = <&hdmi_con>;
> + };
> + };
> +
No need for blank line
> + };
> + };
> +};
> +
> &mdss {
> status = "okay";
> };
> @@ -248,6 +336,10 @@ &qupv3_id_0 {
> status = "okay";
> };
>
> +&qupv3_id_2 {
> + status = "okay";
> +};
> +
> &slpi {
> status = "okay";
> firmware-name = "qcom/sm8350/slpi.mbn";
> @@ -544,4 +636,18 @@ usb_hub_enabled_state: usb-hub-enabled-state {
> drive-strength = <2>;
> output-low;
> };
> +
> + lt9611_rst_pin: lt9611-rst-state {
> + pins = "gpio48";
> + function = "normal";
> +
> + output-high;
> + input-disable;
> + };
> +
> + lt9611_irq_pin: lt9611-irq {
Missing suffix 'state'.
Does not look like you tested the DTS against bindings. Please run `make
dtbs_check` (see Documentation/devicetree/bindings/writing-schema.rst
for instructions).
Rebase your changes on last linux-next.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-28 22:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 12:08 [PATCH v1 0/9] Enable Display for SM8350 Robert Foss
2022-10-28 12:08 ` [PATCH v1 1/9] drm/msm: Add compatibles for SM8350 display Robert Foss
2022-10-28 12:13 ` Dmitry Baryshkov
2022-10-28 12:19 ` Dmitry Baryshkov
2022-10-28 12:29 ` Dmitry Baryshkov
2022-10-28 12:08 ` [PATCH v1 2/9] drm/msm/dpu: Refactor sc7280_pp location Robert Foss
2022-10-28 12:14 ` Dmitry Baryshkov
2022-10-28 12:08 ` [PATCH v1 3/9] drm/msm/dpu: Add SM8350 to hw catalog Robert Foss
2022-10-28 12:26 ` Dmitry Baryshkov
2022-11-11 12:39 ` Robert Foss
2022-10-28 12:08 ` [PATCH v1 4/9] arm64: dts: qcom: sm8350: Add &tlmm gpio-line-names Robert Foss
2022-10-28 12:08 ` [PATCH v1 5/9] arm64: dts: qcom: sm8350: Remove mmxc power-domain-name Robert Foss
2022-10-28 12:08 ` [PATCH v1 6/9] arm64: dts: qcom: sm8350: Use 2 interconnect cells Robert Foss
2022-10-28 13:44 ` Bjorn Andersson
2022-11-11 13:52 ` Robert Foss
2022-10-28 12:08 ` [PATCH v1 7/9] arm64: dts: qcom: sm8350: Add display system nodes Robert Foss
2022-10-28 13:50 ` Bjorn Andersson
2022-10-28 22:01 ` Krzysztof Kozlowski
2022-11-11 15:16 ` Robert Foss
2022-10-28 12:08 ` [PATCH v1 8/9] arm64: dts: qcom: sm8350-hdk: Enable display & dsi nodes Robert Foss
2022-10-28 13:51 ` Bjorn Andersson
2022-10-28 22:03 ` Krzysztof Kozlowski
2022-11-11 15:17 ` Robert Foss
2022-10-28 12:08 ` [PATCH v1 9/9] arm64: dts: qcom: sm8350-hdk: Enable lt9611uxc dsi-hdmi bridge Robert Foss
2022-10-28 13:56 ` Dmitry Baryshkov
2022-11-03 14:19 ` Dmitry Baryshkov
2022-10-28 13:57 ` Bjorn Andersson
2022-11-11 15:18 ` Robert Foss
2022-10-28 22:05 ` Krzysztof Kozlowski [this message]
2022-11-11 15:20 ` Robert Foss
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=408b7b0c-ce30-134e-9b1f-f77c1f03f5c9@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=airlied@linux.ie \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jonathan@marek.ca \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=quic_kalyant@quicinc.com \
--cc=quic_vpolimer@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robert.foss@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=vinod.koul@linaro.org \
--cc=vkoul@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).