On Wednesday, July 10, 2013 09:15:12 AM Dirk Brandewie wrote: > Hi All, Hi, > 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? Well, first off, I'll queue up a revert of commit a66b2e50, as this was really about being nice to user space than anything else. And it has caused subtle problems to happen already elsewhere. Then we can figure out how to address the original issue. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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
