linux-kernel - Re: [PATCH v3 7/7] clk: qcom: apcs-msm8916: use clk_parent

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20191224021636.CF47E20643@mail.kernel.org>
Date:   Mon, 23 Dec 2019 18:16:35 -0800
From:   Stephen Boyd <sboyd@...nel.org>
To:     Niklas Cassel <nks@...wful.org>
Cc:     Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Niklas Cassel <niklas.cassel@...aro.org>,
        linux-arm-msm@...r.kernel.org, amit.kucheria@...aro.org,
        Michael Turquette <mturquette@...libre.com>,
        linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 7/7] clk: qcom: apcs-msm8916: use clk_parent_data to specify the parent

Quoting Niklas Cassel (2019-12-20 09:56:16)
> On Wed, Dec 18, 2019 at 10:23:39PM -0800, Stephen Boyd wrote:
> > This is odd. The clks could be registered with of_clk_hw_register() but
> > then we lose the device provider information. Maybe we should search up
> > one level to the parent node and if that has a DT node but the
> > clk controller device doesn't we should use that instead?
> 
> Hello Stephen,
> 
> Having this in the clk core is totally fine with me,
> since it solves my problem.
> 
> Will you cook up a patch, or do you want me to do it?
> 

Can you try the patch I appended to my previous mail? I can write
something up more proper later this week.