On Mon, Mar 23, 2015 at 11:39:12AM +0200, Ville Syrjälä wrote:
> On Fri, Mar 20, 2015 at 09:09:51PM +, Chris Wilson wrote:
> > On Fri, Mar 20, 2015 at 09:28:08PM +0200, ville.syrj...@linux.intel.com
> > wrote:
> > > From: Ville Syrjälä
> > >
> > > msleep() can sleep for way too long, so swit
On Fri, Mar 20, 2015 at 09:09:51PM +, Chris Wilson wrote:
> On Fri, Mar 20, 2015 at 09:28:08PM +0200, ville.syrj...@linux.intel.com wrote:
> > From: Ville Syrjälä
> >
> > msleep() can sleep for way too long, so switch wait_for() to use
> > usleep_range() instead. Following a totally unscienti
On Fri, Mar 20, 2015 at 12:31:16PM -0700, Jesse Barnes wrote:
> On 03/20/2015 12:28 PM, ville.syrj...@linux.intel.com wrote:
> > From: Ville Syrjälä
> >
> > msleep() can sleep for way too long, so switch wait_for() to use
> > usleep_range() instead. Following a totally unscientific method
> > I j
Tested-By: PRC QA PRTS (Patch Regression Test System Contact:
shuang...@intel.com)
Task id: 6020
-Summary-
Platform Delta drm-intel-nightly Series Applied
PNV -2 274/274
On Fri, Mar 20, 2015 at 09:28:08PM +0200, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> msleep() can sleep for way too long, so switch wait_for() to use
> usleep_range() instead. Following a totally unscientific method
> I just picked the range as W-2W.
>
> This cuts the i915 in
On 03/20/2015 12:28 PM, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> msleep() can sleep for way too long, so switch wait_for() to use
> usleep_range() instead. Following a totally unscientific method
> I just picked the range as W-2W.
>
> This cuts the i915 init time on my BSW
From: Ville Syrjälä
msleep() can sleep for way too long, so switch wait_for() to use
usleep_range() instead. Following a totally unscientific method
I just picked the range as W-2W.
This cuts the i915 init time on my BSW to almost half:
- initcall i915_init+0x0/0xa8 [i915] returned 0 after 41997
