linux-kernel - Re: [PATCH V2] clk: qcom: camcc-sc7180: Add parent dependency to all camera GDSCs

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: <08a6ee40-0729-3573-9938-aa44a6ef297c@quicinc.com>
Date:   Fri, 26 May 2023 16:40:09 +0530
From:   "Satya Priya Kakitapalli (Temp)" <quic_skakitap@...cinc.com>
To:     Stephen Boyd <sboyd@...nel.org>, Andy Gross <agross@...nel.org>,
        "Bjorn Andersson" <andersson@...nel.org>,
        Michael Turquette <mturquette@...libre.com>,
        Taniya Das <quic_tdas@...cinc.com>
CC:     <linux-arm-msm@...r.kernel.org>, <linux-clk@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <quic_cponnapa@...cinc.com>
Subject: Re: [PATCH V2] clk: qcom: camcc-sc7180: Add parent dependency to all
 camera GDSCs

Hi Stephen,

On 5/11/2023 1:02 AM, Stephen Boyd wrote:
> Quoting Taniya Das (2023-05-01 07:29:32)
>> Camera titan top GDSC is a parent supply to all other camera GDSCs. Titan
>> top GDSC is required to be enabled before enabling any other camera GDSCs
>> and it should be disabled only after all other camera GDSCs are disabled.
>> Ensure this behavior by marking titan top GDSC as parent of all other
>> camera GDSCs.
>>
>> Fixes: 15d09e830bbc ("clk: qcom: camcc: Add camera clock controller driver for SC7180")
>> Signed-off-by: Taniya Das <quic_tdas@...cinc.com>
> Is something broken right now? The commit text doesn't tell me if we
> need to backport this to stable kernels or merge it as soon as possible.
> What's the priority of this fix?


Modularization of camx driver triggered this issue now, but there could 
be some other scenarios which could trigger the same issue on stable 
kernels.  Hence it needs to be back ported to stable kernels.