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
| ||
|
Message-Id: <20221125123638.823261-9-bryan.odonoghue@linaro.org> Date: Fri, 25 Nov 2022 12:36:28 +0000 From: Bryan O'Donoghue <bryan.odonoghue@...aro.org> To: linux-arm-msm@...r.kernel.org, freedreno@...ts.freedesktop.org, devicetree@...r.kernel.org Cc: robdclark@...il.com, quic_abhinavk@...cinc.com, dmitry.baryshkov@...aro.org, sean@...rly.run, airlied@...il.com, daniel@...ll.ch, robh+dt@...nel.org, dianders@...omium.org, david@...t.cz, krzysztof.kozlowski+dt@...aro.org, swboyd@...omium.org, konrad.dybcio@...ainline.org, agross@...nel.org, andersson@...nel.org, dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org, bryan.odonoghue@...aro.org Subject: [PATCH v4 08/18] dt-bindings: msm: dsi-controller-main: Add vdd* descriptions back in When converting from .txt to .yaml we didn't include descriptions for the existing regulator supplies. - vdd - vdda - vddio Add those descriptions into the yaml now as they were prior to the conversion. In the .txt description we marked these regulators as required, however, that requirement appears to have been in error. Taking the example of sc7180-trogdor-wormdingler.dtsi. The avdd and avee come from GPIO controlled external regulators, not the SoC and in this case there's no need for vddio to power an I/O bus. Similarly the regulators for the LCD are controlled by the panel driver not by the dsi-ctrl driver. It would be possible to connect a different type of panel to the DSI bus here in which case we may or may not want to make use of vdd, vdda or vddio. This is also the case for older chipsets like apq8064, msm8916 etc the vdd* regulators in the dsi-ctrl block are helpers not dependencies. Add the description of vdd, vdda and vddio back in for the existing upstream dts where vdd, vdda or vddio are already declared but, don't declare those regulators required - they are not SoC requirements. Fixes: 4dbe55c97741 ("dt-bindings: msm: dsi: add yaml schemas for DSI bindings") Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@...aro.org> --- .../bindings/display/msm/dsi-controller-main.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml b/Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml index 0fbb0c04f4b06..bcbcbdca1a78a 100644 --- a/Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml +++ b/Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml @@ -133,6 +133,18 @@ properties: - port@0 - port@1 + vdd-supply: + description: + vdd regulator device node + + vddio-supply: + description: + vdd-io regulator device node + + vdda-supply: + description: + vdda regulator device node + required: - compatible - reg -- 2.38.1
Powered by blists - more mailing lists