this one is needed for the patch I just reviewed to populate the
PAR bits.
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
On Mon, 31 Mar 2014 21:07:04 +0200
Daniel Vetter dan...@ffwll.ch wrote:
On Mon, Mar 31, 2014 at 11:13:57AM -0700, Jesse Barnes wrote:
Going below the minimum value may affect the BLC_EN line, so try to use
the VBT provided minimum where possible, otherwise use an experimentally
derived
-crtc_htotal / 2;
}
if (INTEL_INFO(dev)-gen 3)
My only concern here is that some chip might try to use a nonzero
vsyncshift for a non-interlaced mode. But that should be easy to
bisect to if so, so
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open
Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
mode timings!.
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
This makes HDMI testers happier on VLV platforms. It may be that we
need it for any non-SVO platform, but I don't have any tests to back
that up, so I'm leaving other pre-ILK platforms alone for now.
Tested-by: Clint Taylor clinton.a.tay...@intel.com
Signed-off-by: Jesse Barnes jbar
!
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
On Thu, 20 Mar 2014 10:30:32 -0700
Jesse Barnes jbar...@virtuousgeek.org wrote:
On Thu, 20 Mar 2014 14:42:32 +0100
Daniel Vetter dan...@ffwll.ch wrote:
On Wed, Mar 19, 2014 at 05:41:37PM -0700, Ben Widawsky wrote:
I can't say it's completely unexpected that this would be your response
Junxiao, can you add you reviewed-by to this patch?
Thanks,
Jesse
On Mon, 3 Mar 2014 14:27:57 -0800
Jesse Barnes jbar...@virtuousgeek.org wrote:
So don't try to allocate and program it, we're only fooling ourselves.
Reported-by: Chang, Junxiao junxiao.ch...@intel.com
Signed-off-by: Jesse
GTT_PAGE_SIZE here too? I'm worried the kernel PAGE_SIZE
will change at some point and blow us up. At least in places where
we're doing our own thing rather than using the x86 bits...
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing
this in Chromium for disabling PSR in cases where it
doesn't work? Or to optimize power consumption when the kernel driver
gets it wrong? Or just for debug?
Seems potentially useful, just curious what motivated you guys.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
)
Reported-by: Kristian Høgsberg hoegsb...@gmail.com
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/i915_drv.h |2 ++
drivers/gpu/drm/i915/intel_display.c | 11 ++-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915
Let them eat cake.
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/i915_params.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_params.c
b/drivers/gpu/drm/i915/i915_params.c
index a66ffb6..5f81047 100644
-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/drm_modes.c|8
drivers/gpu/drm/i915/intel_fbdev.c | 37 ++--
include/drm/drm_crtc.h |2 ++
3 files changed, 28 insertions(+), 19 deletions(-)
diff --git a/drivers/gpu/drm
As of IVB, the memory controller does internal swizzling already, so we
shouldn't need to enable these. Based on an earlier fix from Kristian.
v2: preserve swizzling if BIOS had it set (Daniel)
Reported-by: Kristian Høgsberg hoegsb...@gmail.com
Signed-off-by: Jesse Barnes jbar
there was a bit of momentum awhile back, but it
seems to have dissipated.
We could try to extract it from kernel source somehow, but for user API
stuff, I think we really want man pages in libdrm, in addition to
whatever web based documentation we make available.
--
Jesse Barnes, Intel Open Source
On Fri, 14 Mar 2014 19:16:01 +0100
Daniel Vetter dan...@ffwll.ch wrote:
On Fri, Mar 14, 2014 at 7:03 PM, Jesse Barnes jbar...@virtuousgeek.org
wrote:
Yeah just saying a man page should be required as part of any new
ioctl.
Yeah I agree and long-term we'll get there. Otherwise I wouldn't
instead?
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
On Sat, 8 Mar 2014 11:33:15 +0100
Daniel Vetter dan...@ffwll.ch wrote:
On Fri, Mar 07, 2014 at 08:57:55AM -0800, Jesse Barnes wrote:
By stuffing the fb allocation into the crtc, we get mode set lifetime
refcounting for free, but have to handle the initial pin fence
slightly differently
On Sat, 8 Mar 2014 11:36:24 +0100
Daniel Vetter dan...@ffwll.ch wrote:
On Fri, Mar 07, 2014 at 08:57:53AM -0800, Jesse Barnes wrote:
As of IVB, the memory controller does internal swizzling already, so we
shouldn't need to enable these. Based on an earlier fix from Kristian.
Reported
we're both
holding the crtc mutex and prepare_to_wait() will take the crtc
vbl_wait queue lock, but since things look safe as-is I guess it's not
a big deal.
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
Early at init time, we can try to read out the plane config structure
and try to preserve it if possible.
v2: alloc fb obj at init time after fetching plane config
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/i915_drv.h | 3 ++
drivers/gpu/drm/i915
This should allow BIOS fb inheritance to work on ILK+ machines too.
v2: handle tiled BIOS fbs (Kristian)
split out common bits (Jesse)
v3: alloc fb obj out in _init
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/intel_display.c | 62
As of IVB, the memory controller does internal swizzling already, so we
shouldn't need to enable these. Based on an earlier fix from Kristian.
Reported-by: Kristian Høgsberg hoegsb...@gmail.com
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/i915_gem.c| 7
(Daniel)
take fbdev fb ref and remove unused error path (Daniel)
Requested-by: Daniel Vetter dan...@ffwll.ch
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/intel_display.c | 145 ---
drivers/gpu/drm/i915/intel_drv.h | 1
(Daniel)
v12:fix up fb vs pipe size checking (Chris)
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/intel_display.c | 1 -
drivers/gpu/drm/i915/intel_drv.h | 1 +
drivers/gpu/drm/i915/intel_fbdev.c | 174 +--
3 files changed
(Kristian)
pull out common bits (Jesse)
v13: move fb obj alloc out to _init
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/intel_display.c | 63
1 file changed, 63 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_display.c
-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/drm_modes.c| 8
drivers/gpu/drm/i915/intel_fbdev.c | 37 ++---
include/drm/drm_crtc.h | 2 ++
3 files changed, 28 insertions(+), 19 deletions(-)
diff --git a/drivers/gpu/drm
Some machines may have a broken VBT or no VBT at all, but we still want
to use SSC there. So check for it and keep it enabled if we see it
already on. Based on an earlier fix from Kristian.
Reported-by: Kristian Høgsberg hoegsb...@gmail.com
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
On Thu, 6 Mar 2014 09:35:23 +
Chris Wilson ch...@chris-wilson.co.uk wrote:
On Wed, Mar 05, 2014 at 02:48:26PM -0800, Jesse Barnes wrote:
@@ -7554,6 +7610,8 @@ static int intel_crtc_cursor_set(struct drm_crtc
*crtc,
goto fail;
}
+ intel_sync_crtc(crtc
On Thu, 6 Mar 2014 09:12:40 +
Chris Wilson ch...@chris-wilson.co.uk wrote:
On Wed, Mar 05, 2014 at 02:48:27PM -0800, Jesse Barnes wrote:
This gets us out of our init code and out to userspace quite a bit
faster, but does open us up to some bugs given the state of our init
time locking
On Thu, 6 Mar 2014 11:28:13 +0200
Ville Syrjälä ville.syrj...@linux.intel.com wrote:
On Wed, Mar 05, 2014 at 02:48:30PM -0800, Jesse Barnes wrote:
It takes awhile to fetch the DPCD and EDID for caching, so take it out
of the critical path to improve init time.
Signed-off-by: Jesse
No special reason. It shouldn't matter on BYT either, really, since
pipe A doesn't have special characteristics like it does on HSW.
Jesse
On Thu, 6 Mar 2014 17:19:22 +0800
Lin, Mengdong mengdong@intel.com wrote:
Hi Jesse,
Could you tell us why Baytrail Gfx driver does not always
them, or it'll end
up staying disabled forever, and then we'll be stuck without a command
checker and some advanced features coming up...
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http
-off-by: Imre Deak imre.d...@intel.com
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/i915_dma.c | 14
drivers/gpu/drm/i915/i915_drv.c | 4 +--
drivers/gpu/drm/i915/i915_drv.h | 4 +--
drivers/gpu/drm/i915/intel_display.c | 27
,
+ .domains = BDW_DISPLAY_POWER_DOMAINS,
.is_enabled = hsw_power_well_enabled,
.set = hsw_set_power_well,
},
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
(POWER_DOMAIN_TRANSCODER_EDP) | \
+ BIT(POWER_DOMAIN_INIT))
#define HSW_DISPLAY_POWER_DOMAINS ( \
(POWER_DOMAIN_MASK ~HSW_ALWAYS_ON_POWER_DOMAINS) |\
BIT(POWER_DOMAIN_INIT))
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel
)
- power_well-ops-sync_hw(dev_priv, power_well);
- }
+ for_each_power_well(i, power_well, POWER_DOMAIN_MASK, power_domains)
+ power_well-ops-sync_hw(dev_priv, power_well);
mutex_unlock(power_domains-lock);
}
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse
= DPLL_ID_PRIVATE;
Same goes here, though I suppose there's more room for additional,
specific domains down at this level...
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing
|
- I915_DISPLAY_PIPE_B_VBLANK_INTERRUPT;
+ dev_priv-irq_mask = ~enable_mask;
I915_WRITE(PORT_HOTPLUG_EN, 0);
POSTING_READ(PORT_HOTPLUG_EN);
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
);
}
mutex_unlock(power_domains-lock);
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo
, power_domain);
+
return has_audio;
}
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman
seemed nicer... but either way works
I guess.
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman
-display_irqs_enabled = true;
+
+ if (dev_priv-dev-irq_enabled)
+ valleyview_display_irqs_install(dev_priv);
+}
This made me do a double take, then I saw you were checking the actual
drm_device irq enabled state rather than checking the new field again...
Looks good.
Reviewed-by: Jesse Barnes
well to be always enabled. */
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
. :)
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
{
set_power_wells(power_domains, i9xx_always_on_power_well);
}
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org
On Wed, 5 Mar 2014 13:55:00 +0100
Daniel Vetter dan...@ffwll.ch wrote:
On Thu, Feb 20, 2014 at 08:50:59PM +, Chris Wilson wrote:
On Thu, Feb 20, 2014 at 12:39:57PM -0800, Jesse Barnes wrote:
Useful for bug reports.
Hey, this would be useful for error state as well :)
I seem
On Tue, 4 Mar 2014 22:08:12 +0100
Daniel Vetter dan...@ffwll.ch wrote:
On Tue, Mar 04, 2014 at 12:33:01PM -0800, Jesse Barnes wrote:
On Tue, 4 Mar 2014 21:08:42 +0100
Daniel Vetter daniel.vet...@ffwll.ch wrote:
Both Ville and QA rather immediately complained that with the new
On Wed, 5 Mar 2014 19:34:45 +0100
Daniel Vetter dan...@ffwll.ch wrote:
On Wed, Mar 05, 2014 at 08:27:08AM -0800, Jesse Barnes wrote:
On Tue, 4 Mar 2014 22:08:12 +0100
Daniel Vetter dan...@ffwll.ch wrote:
On Tue, Mar 04, 2014 at 12:33:01PM -0800, Jesse Barnes wrote:
On Tue, 4 Mar
Drivers ought to complain otherwise.
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/drm_fb_helper.c | 2 ++
drivers/gpu/drm/i915/intel_dp.c | 4
drivers/gpu/drm/i915/intel_drv.h | 3 +++
3 files changed, 9 insertions(+)
diff --git a/drivers/gpu/drm
This lets us return to userspace more quickly and should improve init
and suspend/resume times as well, allowing us to return to userspace
sooner.
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/i915_drv.c | 2 +-
drivers/gpu/drm/i915/i915_drv.h | 4
In the hotplug case, nothing was grabbing VDD, leading to some warnings.
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/intel_dp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 763f235
I'm worried about the locking in this... I've also commented out the
state checker, but that can be re-added as a check after any queued CRTC
changes as another queued item, so should be easy to fix.
This set drastically improves the init time of the i915 module (based on
initcall_debug timing),
This gets us out of our init code and out to userspace quite a bit
faster, but does open us up to some bugs given the state of our init
time locking.
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/i915_dma.c| 3 ++-
drivers/gpu/drm/i915/i915_drv.h| 1
Reduces params in a few places and makes workqueueing the eDP caching work
easier.
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/intel_dp.c | 23 +--
drivers/gpu/drm/i915/intel_drv.h | 1 +
2 files changed, 10 insertions(+), 14 deletions
On Thu, 06 Mar 2014 01:29:14 +0200
Imre Deak imre.d...@intel.com wrote:
On Wed, 2014-03-05 at 14:48 -0800, Jesse Barnes wrote:
This lets us return to userspace more quickly and should improve init
and suspend/resume times as well, allowing us to return to userspace
sooner.
IMHO
, then doing a mode set that ends up doing just a pipe base
update, right?
Otherwise,
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http
.
Cc: Jesse Barnes jbar...@virtuousgeek.org
Signed-off-by: Daniel Vetter daniel.vet...@ffwll.ch
---
drivers/gpu/drm/i915/intel_fbdev.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_fbdev.c
b/drivers/gpu/drm/i915/intel_fbdev.c
index
as
possible (it even has hotplug handling and all that) fall back if more
outputs could have been enabled.
v2: Fix up my confusion about what enabled means - it's passed from
the fbdev helper, we need to check for a non-zero connector-encoder
link. Spotted by Ville.
Cc: Jesse Barnes jbar
commit 2514bc510d0c3aadcc5204056bb440fa36845147
Author: Jesse Barnes jbar...@virtuousgeek.org
Date: Thu Jun 21 15:13:50 2012 -0700
drm/i915: prefer wide slow to fast narrow in DP configs
I'm pretty sure I'll regret this patch, but otoh I expect we won't
make progress here without
On Thu, 27 Feb 2014 11:01:08 +0200
Jani Nikula jani.nik...@linux.intel.com wrote:
On Thu, 27 Feb 2014, Jani Nikula jani.nik...@linux.intel.com wrote:
On Wed, 26 Feb 2014, Jesse Barnes jbar...@virtuousgeek.org wrote:
On Mon, 13 Jan 2014 16:25:21 +0530
akash.g...@intel.com wrote:
From
So don't try to allocate and program it, we're only fooling ourselves.
Reported-by: Chang, Junxiao junxiao.ch...@intel.com
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
drivers/gpu/drm/i915/i915_dma.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915
On Mon, 3 Mar 2014 11:14:09 -0800
Jesse Barnes jbar...@virtuousgeek.org wrote:
On Thu, 27 Feb 2014 11:01:08 +0200
Jani Nikula jani.nik...@linux.intel.com wrote:
On Thu, 27 Feb 2014, Jani Nikula jani.nik...@linux.intel.com wrote:
On Wed, 26 Feb 2014, Jesse Barnes jbar
On Fri, 7 Feb 2014 18:37:01 -0200
Rodrigo Vivi rodrigo.v...@gmail.com wrote:
From: Jesse Barnes jbar...@virtuousgeek.org
The intent is to get back to userspace as quickly as possible so it can
start doing drawing or whatever. It should also allow our
suspend/resume/init time to improve
;
}
@@ -8131,7 +8131,7 @@ void intel_mark_idle(struct drm_device *dev)
gen6_rps_idle(dev-dev_private);
out:
- hsw_enable_package_c8(dev_priv);
+ intel_runtime_pm_put(dev_priv);
}
void intel_mark_fb_busy(struct drm_i915_gem_object *obj,
Reviewed-by: Jesse Barnes jbar
);
+ intel_runtime_pm_get(dev_priv);
mutex_unlock(dev_priv-pc8.lock);
}
Oh here it is, the next patch in the series. :)
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx
it looks like these functions are just documentation around the
runtime PM bits. I don't see them get remove totally in favor of the
runtime_pm_get|put calls later on, is that possible or desirable?
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology
-dev;
But OTOH, in cases where we have a separate, explicit power well for
display, doesn't the aux_display_runtime_get|put make sense? We don't
want just global runtime get/put everywhere since we can be finer
grained in may cases, right?
--
Jesse Barnes, Intel Open Source Technology Center
-rps.delayed_resume_work,
intel_gen6_powersave_work);
}
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http
-pc8.lock);
INIT_DELAYED_WORK(dev_priv-rps.delayed_resume_work,
intel_gen6_powersave_work);
Yay, this is a nice simplification overall.
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
issue really...
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
intel_dotclock_calculate(int link_freq, const struct intel_link_m_n
*m_n);
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org
(dev_priv-modeset_restore_lock);
dev_priv-modeset_restore = MODESET_DONE;
mutex_unlock(dev_priv-modeset_restore_lock);
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing
intel_init_runtime_pm),
but
+ * it can be changed with the standard runtime PM files frmo sysfs.
typo from
Otherwise, Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org
);
- hsw_enable_package_c8(dev_priv);
- }
}
void intel_display_power_get(struct drm_device *dev,
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
= false;
dev_priv-pm.irqs_disabled = false;
}
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
Though my earlier comments about getting rid of the init special case
still apply... I think it would be a little easier to understand in
that case (though maybe not, I guess we'd have to see
On Fri, 28 Feb 2014 19:38:17 +0200
Imre Deak imre.d...@intel.com wrote:
On Fri, 2014-02-28 at 09:13 -0800, Jesse Barnes wrote:
On Thu, 27 Feb 2014 19:26:43 -0300
Paulo Zanoni przan...@gmail.com wrote:
From: Paulo Zanoni paulo.r.zan...@intel.com
We had
,
+ base, base +
(uint32_t)dev_priv-gtt.stolen_size);
+ base = 0;
+ }
}
return base;
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
Tested-by: Arjan van de Ven ar...@linux.intel.com
Thanks,
--
Jesse Barnes, Intel Open
);
}
}
- spin_unlock_irqrestore(dev-vblank_time_lock, irqflags2);
+ spin_unlock(dev-vblank_time_lock);
} else {
if (!dev-vblank[crtc].enabled) {
atomic_dec(dev-vblank[crtc].refcount);
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
;/** Protects vblank count and time
updates during vblank enable/disable */
spinlock_t vbl_lock;
- struct timer_list vblank_disable_timer;
u32 max_vblank_count; /** size of vblank counter register */
Yeah this looks like a good fix.
Reviewed-by: Jesse Barnes
.
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
,
struct timeval *tvblank, unsigned flags);
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo
On Wed, 26 Feb 2014 20:02:19 +0200
Imre Deak imre.d...@intel.com wrote:
On Thu, 2014-02-20 at 11:58 -0800, Jesse Barnes wrote:
On Wed, 19 Feb 2014 14:29:44 +0200
Ville Syrjälä ville.syrj...@linux.intel.com wrote:
On Tue, Feb 18, 2014 at 12:02:20AM +0200, Imre Deak wrote:
Based
and 3.14-rc1 didn't prove fruitful,
either because I messed it up or there's a combination of things that
fix the issue. So instead I did a regular git bisect between 3.12 and
3.13 to see which commit _broke_ things and caused the above behavior.
That landed me at:
Author: Jesse Barnes
addressed:
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
(struct drm_device *dev)
if (INTEL_INFO(dev)-gen = 6)
gen6_rps_idle(dev-dev_private);
+
+out:
+ hsw_package_c8_gpu_idle(dev_priv);
}
void intel_mark_fb_busy(struct drm_i915_gem_object *obj,
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes
)
intel_modeset_check_state(crtc-dev);
+ intel_runtime_pm_put(dev_priv);
return ret;
}
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
drm_connector *connector, bool
force)
} else
status = connector_status_unknown;
+out:
+ intel_runtime_pm_put(dev_priv);
return status;
}
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
there are more places we need this too.. wonder if it would
be better to put the get into some wrapper around our sysfs files...
But these bits look correct, if not sufficient, so:
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
the Gunit
goes away too. But in that case the GT will be shut down as well, so I
don't think the display vs GT thing by itself is a problem.
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http
To silence locking complaints. This was a rebase failure on my part in
commit fa9fa083d0606cb323f6105c17702460ea0a6780
Author: Jesse Barnes jbar...@virtuousgeek.org
Date: Tue Feb 11 15:28:56 2014 -0800
drm/i915: read out hw state earlier v2
Reported-by: Ville Syrjälä ville.syrj
(GEN7_L3SQCREG4)
~L3SQ_URB_READ_CAM_MATCH_DISABLE);
I don't think we have good docs on this, but since it works empirically:
Acked-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel
);
+ hsw_enable_package_c8(dev_priv);
+ }
+ }
mutex_unlock(power_domains-lock);
}
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel
];
- }
-
- intel_display_set_init_power(dev_priv, false);
-}
-
static void haswell_modeset_global_resources(struct drm_device *dev)
{
modeset_update_power_wells(dev);
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
any requests made by it since
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
,
},
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
~HSW_ALWAYS_ON_POWER_DOMAINS) |\
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
I wonder if we want a way to parameterize the lane count instead, in
case we end up doing 1 lane for example in the future, or have some
other power domain that can provide multiple levels of power.
But I suppose we can
issue, the rest looks like a good change and
pulls some of the HSW bits out of the generic routines.
Reviewed-by: Jesse Barnes jbar...@virtuousgeek.org
--
Jesse Barnes, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx
701 - 800 of 2916 matches
Mail list logo