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]
Date:   Mon, 31 Aug 2020 09:57:39 +0200
From:   Konrad Dybcio <konradybcio@...il.com>
To:     Amit Pundir <amit.pundir@...aro.org>
Cc:     Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        John Stultz <john.stultz@...aro.org>,
        Sumit Semwal <sumit.semwal@...aro.org>,
        linux-arm-msm <linux-arm-msm@...r.kernel.org>,
        dt <devicetree@...r.kernel.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6] arm64: dts: qcom: Add support for Xiaomi Poco F1 (Beryllium)

> Hi Konrad,
>
> I couldn't find answer to your question around missing
> (regulatorname)-supply properties. Need help in figuring out that
> part.

When the phone boots up and RPM(H) kicks in, you should see regulators
probing like "s1 supplied by foo". Without the *-supply stuff, you
will likely get "supplied by regulator-dummy". This happens here [1]
and to my knowledge it is the "eletrical wiring" for Linux, as in it
makes Linux aware of which regulators are connected electrically to
the same supply (so that kernel knows when the supply is on and what
voltage it's at). For qcom platforms, this is common per-pmic (afaik,
please check if you are able to!), so you can likely just copy-paste
that part from msm8998-mtp.dtsi, which also uses pm(i)8998.

Konrad

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ