linux-kernel - Re: [PATCH v2 1/4] crypto: caam - do not initialise clocks on the i.MX8

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: <VI1PR0402MB34855AC8C617A3D7A584A1B798ED0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
Date:   Tue, 11 Jun 2019 09:56:40 +0000
From:   Horia Geanta <horia.geanta@....com>
To:     Andrey Smirnov <andrew.smirnov@...il.com>,
        "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>
CC:     Chris Spencer <christopher.spencer@....co.uk>,
        Aymen Sghaier <aymen.sghaier@....com>,
        Cory Tusar <cory.tusar@....aero>,
        Chris Healy <cphealy@...il.com>,
        Lucas Stach <l.stach@...gutronix.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Abel Vesa <abel.vesa@....com>,
        dl-linux-imx <linux-imx@....com>,
        "linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>
Subject: Re: [PATCH v2 1/4] crypto: caam - do not initialise clocks on the
 i.MX8

On 6/7/2019 11:03 PM, Andrey Smirnov wrote:
> From: Chris Spencer <christopher.spencer@....co.uk>
> 
> There are no clocks that the CAAM driver needs to initialise on the
> i.MX8.
> 
RM lists 5 clocks for CAAM module (instance.clock): caam.aclk, caam.ipg_clk,
caam.ipg_clk_s, caam_exsc.aclk_exsc, caam_mem.clk
				
Wouldn't it be better to have these clocks in DT, instead of relying that their
root clocks (ccm_ahb_clk_root, ccm_ipg_clk_root) are critical / always on?

Thanks,
Horia