linux-kernel - Re: [PATCH] pwm: brcmstb: Utilize appropriate clock APIs in suspend/resume

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] [day] [month] [year] [list]

Message-ID: <169711894378.3084011.13476769649466212978.b4-ty@gmail.com>
Date:   Thu, 12 Oct 2023 15:55:58 +0200
From:   Thierry Reding <thierry.reding@...il.com>
To:     linux-pwm@...r.kernel.org,
        Florian Fainelli <florian.fainelli@...adcom.com>
Cc:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>,
        Broadcom internal kernel review list 
        <bcm-kernel-feedback-list@...adcom.com>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pwm: brcmstb: Utilize appropriate clock APIs in suspend/resume


On Wed, 04 Oct 2023 10:54:14 -0700, Florian Fainelli wrote:
> The suspend/resume functions currently utilize
> clk_disable()/clk_enable() respectively which may be no-ops with certain
> clock providers such as SCMI. Fix this to use clk_disable_unprepare()
> and clk_prepare_enable() respectively as we should.
> 
> 

Applied, thanks!

[1/1] pwm: brcmstb: Utilize appropriate clock APIs in suspend/resume
      commit: 4da07e8a22919fde057b554716e4c5a640d4d805

Best regards,
-- 
Thierry Reding <thierry.reding@...il.com>