Hi All, Tianyu debugged into https://bugzilla.kernel.org/show_bug.cgi?id=59781 and found that commit a66b2e50 is causing the regression. Tianyu has proposed a fix (patch attached to bugzilla) but having scaling drivers receive hotplug notifications through two paths seems weird. Looking at the core code and some of the other scaling drivers I don't see an obvious fix. Maybe adding optional suspend/resume callbacks to the scaling driver interface? All the scaling drivers that need to do stateful work in the init/exit callbacks are being affected by this change so I think there are other subtle side-effects out there that haven't been noticed yet. I am not sure how we should proceed here? Thoughts? --Dirk -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
