linux-kernel - Re: Question on pre running clocks

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]

Date:   Fri, 20 Oct 2023 12:39:05 +0530
From:   Arun KS <arunks.linux@...il.com>
To:     linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org
Cc:     sboyd@...nel.org, mturquette@...libre.com,
        Arun KS <getarunks@...il.com>
Subject: Re: Question on pre running clocks

+ linux-clk

On Fri, Oct 20, 2023 at 12:37 PM Arun KS <arunks.linux@...il.com> wrote:
>
> Hello,
>
> Lets say there is a clock which is enabled by bootloaders and is pre
> running as linux boots.
> Is it mandatory for the client drivers to call clk_prepare_enable() on
> them to initialise the enable_count to 1?
>
> Or is there a way we can specify to the kernel that this clock is
> already enabled by bootloader and initialise the enable_count for this
> clock to 1.
>
> Because otherwise, clk_disable() prints a WARN() if a client driver
> uses clock handle where clk_prepare_enable() is not called.
>
> I grep through the code, but could find any details. Appreciate any pointers.
>
> Regards,
> Arun