linux-kernel - Re: [PATCH RFC v2 4/5] ARM: dts: qcom: msm8974: add HDMI nodes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20191009022131.604B52070B@mail.kernel.org>
Date:   Tue, 08 Oct 2019 19:21:30 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Brian Masney <masneyb@...tation.org>, robdclark@...il.com,
        sean@...rly.run
Cc:     bjorn.andersson@...aro.org, a.hajda@...sung.com,
        Laurent.pinchart@...asonboard.com, airlied@...ux.ie,
        daniel@...ll.ch, dri-devel@...ts.freedesktop.org,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        freedreno@...ts.freedesktop.org, jonathan@...ek.ca,
        Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH RFC v2 4/5] ARM: dts: qcom: msm8974: add HDMI nodes

Quoting Brian Masney (2019-10-06 18:45:08)
> diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi b/arch/arm/boot/dts/qcom-msm8974.dtsi
> index 7fc23e422cc5..af02eace14e2 100644
> --- a/arch/arm/boot/dts/qcom-msm8974.dtsi
> +++ b/arch/arm/boot/dts/qcom-msm8974.dtsi
> @@ -1335,6 +1342,77 @@
>                                 clocks = <&mmcc MDSS_AHB_CLK>;
>                                 clock-names = "iface";
>                         };
> +
> +                       hdmi: hdmi-tx@...22100 {
> +                               status = "disabled";
> +
> +                               compatible = "qcom,hdmi-tx-8974";
> +                               reg = <0xfd922100 0x35c>,
> +                                     <0xfc4b8000 0x60f0>;
> +                               reg-names = "core_physical",
> +                                           "qfprom_physical";

Is this the qfprom "uncorrected" physical address? If so, why can't this
node use an nvmem to read whatever it needs out of the qfprom?

> +
> +                               interrupt-parent = <&mdss>;
> +                               interrupts = <8 IRQ_TYPE_LEVEL_HIGH>;
> +
> +                               power-domains = <&mmcc MDSS_GDSC>;
> +