linux-kernel - Re: [RESEND PATCH] arm64: DT: qcom: msm8998: Provide missing "xo" and "sleep

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] [day] [month] [year] [list]

Message-ID: <20210918230609.qbdcneew7ukwdxst@SoMainline.org>
Date:   Sun, 19 Sep 2021 01:06:09 +0200
From:   Marijn Suijten <marijn.suijten@...ainline.org>
To:     phone-devel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>
Cc:     ~postmarketos/upstreaming@...ts.sr.ht,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...ainline.org>,
        Konrad Dybcio <konrad.dybcio@...ainline.org>,
        Martin Botka <martin.botka@...ainline.org>,
        Jami Kettunen <jami.kettunen@...ainline.org>,
        Stephen Boyd <sboyd@...nel.org>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH] arm64: DT: qcom: msm8998: Provide missing "xo"
 and "sleep_clk" to GCC

On 2021-09-18 16:35:02, Marijn Suijten wrote:
> In a future patch the GCC driver will stop requesting this xo clock by
> its global "xo" name, in favour of of having an explicit phandle here in
> the DT.  Aside from that this clock in addition to the mandatory
> "sleep_clk" were never passed despite being required by the relevant
> dt-bindings.
> 
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...ainline.org>
> Signed-off-by: Marijn Suijten <marijn.suijten@...ainline.org>
> ---
> Resending to directly address Rob Herring in the To: field and add
> Stephen Boyd to cc whom already queued the clk driver part in clk-next.

Apologies for the re-send noise; this patch is already going in through
the qcom tree:
https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/commit/?h=for-next&id=2c2f64ae36d97c1ec756ed781640f7951f7bac42