Ivan Grokhotkov
fe5d294f6c
pm: handle changes to the PM_MODE_ACTIVE frequency ...
The issue would manifest itself in cases when switching from PM
configuration like {active=160MHz, idle=80MHz} to {active=80MHz,
idle=80Mhz}. After the configuration was changed, PM logic would
think that current frequency was 80MHz and would not do any further
switching. In fact, frequency was still 160MHz.
2018-03-27 11:20:54 +08:00
2018-02-21 10:13:25 +03:00
2018-02-05 14:38:23 +08:00
2018-03-19 16:39:54 +08:00
2018-03-21 13:27:56 +05:00
2018-03-22 10:08:47 +08:00
2017-10-26 13:04:41 +02:00
2018-01-29 09:22:04 +08:00
2018-01-23 07:56:13 +00:00
2018-03-20 10:49:36 +08:00
2018-03-27 11:20:54 +08:00
2018-03-16 15:51:36 +08:00
2018-02-28 10:17:14 +11:00
2018-02-11 16:11:14 +08:00
2018-03-23 14:06:56 +08:00
2018-02-21 12:31:10 +05:30
2018-02-20 10:32:06 +11:00
2018-03-16 16:37:19 +08:00
2018-02-05 14:15:26 +08:00
2017-10-19 21:35:23 +08:00
2018-02-06 14:35:39 +08:00
2018-03-08 20:34:40 +08:00
2017-12-07 10:25:57 +11:00
2018-01-22 13:56:53 +01:00
2017-12-11 12:37:08 +08:00
2017-10-26 13:04:41 +02:00
2017-12-04 10:18:40 +11:00
2018-02-20 12:32:12 +05:30
2018-02-22 07:46:41 +01:00
2018-03-20 18:06:32 +05:30
2018-02-07 12:05:05 +08:00
2018-03-27 10:55:59 +08:00
2018-03-08 09:39:20 +01:00
2018-01-31 14:29:13 +08:00
2018-03-21 11:04:22 +08:00
2018-01-08 21:28:14 +08:00
2018-03-14 22:04:47 +01:00
2018-03-12 15:34:16 +03:00
fe5d294f6c