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: <20220929001745.A4F9FC433B5@smtp.kernel.org>
Date:   Wed, 28 Sep 2022 17:17:40 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Rahul Tanwar <rtanwar@...linear.com>, linux-clk@...r.kernel.org,
        mturquette@...libre.com
Cc:     linux-kernel@...r.kernel.org, linux-lgm-soc@...linear.com,
        Rahul Tanwar <rtanwar@...linear.com>
Subject: Re: [PATCH RESEND v2 3/5] clk: mxl: Avoid disabling gate clocks from clk driver

Quoting Rahul Tanwar (2022-09-21 23:24:26)
> In MxL's LGM SoC, gate clocks are supposed to be enabled or disabled
> from EPU (power management IP) in certain power saving modes. If gate
> clocks are allowed to be enabled/disabled from CGU clk driver, then
> there arises a conflict where in case clk driver disables a gate clk,
> and then EPU tries to disable the same gate clk, then it will hang
> polling for the clk gated successful status.

Is there any point in registering these clks when they're not supposed
to be controlled from Linux?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ