On Sat, 19 Jan 2019 12:09:48 +0530
"J, KEERTHY" <j-keerthy@xxxxxx> wrote:
On 1/19/2019 1:18 AM, Tony Lindgren wrote:
* Andreas Kemnade <andreas@xxxxxxxxxxxx> [190118 19:42]:
On Fri, 18 Jan 2019 20:38:47 +0100
Andreas Kemnade <andreas@xxxxxxxxxxxx> wrote:
Hi,and there are quite few hwmods marked by this flag.
On Fri, 18 Jan 2019 10:36:30 -0800
Tony Lindgren <tony@xxxxxxxxxxx> wrote:
til the next workaround.well, if we want to manually disable it and not automatically,
That flags also causes the iclk being enabled/disabled
Yes but SWSUP_IDLE for the interface clock to me currently
"manually enable and disable ocp interface clock"
we have to disable autoidle or it will be automatically disabled.
Disabling it manually when it is already auto-disabled (by autoidle) is
just practically a no-op towards the clock.
and with your changes it becomes:Yes, we are, so proper testing is needed. But If I read those comments
"manually enable and disable ocp interface clock and block
autoidle while in use".
So aren't we now changing the way things behave in general
it was always intended this way but not fully implemented because it
appeared to be more work like needing a usecounter (which my patchset
also adds) for that autoidle flag.
And then there are those clocks marked by this flags (on am33xx) which
do not have that autoidle feature at all, so the risk is not too high.
Keerthy, can you please test this series on top of the
related clock patches with your am335x PM test cases?
Can you point me to the clock series that needs to be tested
along with this?