On Sat, 1 Feb 2014, Zoran Markovic wrote: > From: Shaibal Dutta <shaibal.du...@broadcom.com> > > Allow the scheduler to select the best CPU to handle hub initalization > and LED blinking work. This extends idle residency times on idle CPUs > and conserves power. > > This functionality is enabled when CONFIG_WQ_POWER_EFFICIENT is selected. > > Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org> > Cc: Alan Stern <st...@rowland.harvard.edu> > Cc: Sarah Sharp <sarah.a.sh...@linux.intel.com> > Cc: Xenia Ragiadakou <burzalod...@gmail.com> > Cc: Julius Werner <jwer...@chromium.org> > Cc: Krzysztof Mazur <krzys...@podlesie.net> > Cc: Matthias Beyer <m...@beyermatthias.de> > Cc: Dan Williams <dan.j.willi...@intel.com> > Cc: Mathias Nyman <mathias.ny...@linux.intel.com> > Cc: Thomas Pugliese <thomas.pugli...@gmail.com> > Signed-off-by: Shaibal Dutta <shaibal.du...@broadcom.com> > [zoran.marko...@linaro.org: Rebased to latest kernel. Added commit message. > Changed reference from system to power efficient workqueue for LEDs in > check_highspeed() and hub_port_connect_change().] > Signed-off-by: Zoran Markovic <zoran.marko...@linaro.org>
Acked-off-by: Alan Stern <st...@rowland.harvard.edu> Is there some reason why schedule_delayed_work() doesn't use the power-efficient work queue by default? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
