linux-kernel - Re: [PATCH v2 2/3] clk: ti: check clock type before doing autoidle ops

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: <20181204164556.GB6707@atomide.com>
Date:   Tue, 4 Dec 2018 08:45:57 -0800
From:   Tony Lindgren <tony@...mide.com>
To:     Andreas Kemnade <andreas@...nade.info>
Cc:     Stephen Boyd <sboyd@...nel.org>, Tero Kristo <t-kristo@...com>,
        bcousson@...libre.com, letux-kernel@...nphoenux.org,
        linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-omap@...r.kernel.org, mturquette@...libre.com, paul@...an.com
Subject: Re: [PATCH v2 2/3] clk: ti: check clock type before doing autoidle
 ops

* Andreas Kemnade <andreas@...nade.info> [181204 06:17]:
> On Mon, 3 Dec 2018 07:39:10 -0800
> Tony Lindgren <tony@...mide.com> wrote:
> > The consumer device stays active just fine with PM runtime
> > calls. So yes, the problem is keeping a clock controller forced
> > active for the period of consumer device reset. Other than
> > that typically autoidle can be just kept enabled.
> > 
> Are we still talking about the same problem? Maybe I am losing track
> here. Just to make sure. 
> The patch series was about disabling autoidle for devices which cannot
> work with it during normal operation. Not during reset or something
> like that. 
> Or is the keep-clock-active-during-reset just a requirement for bigger
> restructuring ideas?

Yeah there are two issues: The fix needed for the issue you brought up,
and also how to let a reset driver to block autoidle for reset.

Regards,

Tony