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  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:   Thu, 17 Jan 2019 16:03:10 +0100
From:   Marc Gonzalez <>
To:     Rajendra Nayak <>,
        MSM <>
Cc:     Andy Gross <>,
        Viresh Kumar <>,
        Bjorn Andersson <>,
        Jeffrey Hugo <>,
        LKML <>
Subject: Re: [PATCH v11 0/9] Add power domain driver for corners on

On 10/01/2019 05:02, Rajendra Nayak wrote:

> Rajendra Nayak (9):
>   dt-bindings: opp: Introduce opp-level bindings
>   OPP: Add support for parsing the 'opp-level' property
>   dt-bindings: power: Add qcom rpm power domain driver bindings
>   soc: qcom: rpmpd: Add a Power domain driver to model corners
>   soc: qcom: rpmpd: Add support for get/set performance state
>   arm64: dts: msm8996: Add rpmpd device node
>   soc: qcom: rpmhpd: Add RPMh power domain driver
>   arm64: dts: sdm845: Add rpmh powercontroller node
>   soc: qcom: rpmhpd: Mark mx as a parent for cx
>  Documentation/devicetree/bindings/opp/opp.txt |   3 +
>  .../devicetree/bindings/power/qcom,rpmpd.txt  | 145 +++++++
>  arch/arm64/boot/dts/qcom/msm8996.dtsi         |  34 ++
>  arch/arm64/boot/dts/qcom/sdm845.dtsi          |  51 +++

Whenever I see these patches adding support for msm8996 (aka sdm820) and sdm845
simultaneously, I think to myself: "Why is sdm835 being left out? It was released
between sdm820 and sdm845, it cannot be /that/ different."

So I'm wondering: how much extra work would it be to add support for msm8998
aka sdm835?


Powered by blists - more mailing lists