Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751900AbaBBQKR (ORCPT ); Sun, 2 Feb 2014 11:10:17 -0500 Received: from netrider.rowland.org ([192.131.102.5]:43847 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751726AbaBBQKO (ORCPT ); Sun, 2 Feb 2014 11:10:14 -0500 Date: Sun, 2 Feb 2014 11:10:13 -0500 (EST) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: Zoran Markovic cc: linux-kernel@vger.kernel.org, , Shaibal Dutta , Greg Kroah-Hartman , Sarah Sharp , Xenia Ragiadakou , Julius Werner , Krzysztof Mazur , Matthias Beyer , Dan Williams , Mathias Nyman , Thomas Pugliese Subject: Re: [RFC PATCHv2] usb: move hub init and LED blink work to power efficient workqueue In-Reply-To: <1391311006-4138-1-git-send-email-zoran.markovic@linaro.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 1 Feb 2014, Zoran Markovic wrote: > From: Shaibal Dutta > > 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 > Cc: Alan Stern > Cc: Sarah Sharp > Cc: Xenia Ragiadakou > Cc: Julius Werner > Cc: Krzysztof Mazur > Cc: Matthias Beyer > Cc: Dan Williams > Cc: Mathias Nyman > Cc: Thomas Pugliese > Signed-off-by: Shaibal Dutta > [zoran.markovic@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 Acked-off-by: Alan Stern 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/