On Fri, Dec 02, 2016 at 11:17:35AM +0100, Hans de Goede wrote:
> The primary consumer of the lpss pwm is the i915 kms driver, but
> currently that driver cannot get the pwm because i915 platforms are
> not using devicetree and pwm-lpss does not call pwm_add_table.
>
> Another problem is that i915
In preparation to using a generic API in the DRM core for continuous CRC
generation, move the related code out of i915_debugfs.c into a new file.
Eventually, only the Intel-specific code will remain in this new file.
v2: Rebased.
v6: Rebased.
v7: Fix whitespace issue.
v9: Have intel_display_cr
The core provides now an ABI to userspace for generation of frame CRCs,
so implement the ->set_crc_source() callback and reuse as much code as
possible with the previous ABI implementation.
When handling the pageflip interrupt, we skip 1 or 2 frames depending on
the HW because they contain wrong v
Hi,
here are the patches that remain to be merged in this series. They have
been rebased and I have also addressed two smaller comments:
- Move locking into drm_crtc_add_crc_entry (Daniel Vetter).
- Define intel_crtc_set_crc_source as NULL if !CONFIG_DEBUG_FS (Jani
Nikula).
Thanks,
Tomeu
To
Use drm_accurate_vblank_count so we have the full 32 bit to represent
the frame counter and userspace has a simpler way of knowing when the
counter wraps around.
Signed-off-by: Tomeu Vizoso
Reviewed-by: Emil Velikov
---
drivers/gpu/drm/i915/i915_irq.c | 6 +++---
1 file changed, 3 insertions(+
On Fri, Dec 02, 2016 at 11:17:36AM +0100, Hans de Goede wrote:
> Add a get_state callback so that the initial state correctly reflects
> the actual hardware state.
>
> Signed-off-by: Hans de Goede
> ---
> drivers/pwm/pwm-lpss.c | 28
> 1 file changed, 28 insertions(+
From: Jani Nikula
Request the GPIO by index through the consumer API. For now, use a quick
hack to store the already requested ones, simply because I have no idea
whether this actually works or not, and I have no way to test it.
v2: switch *NULL* to *"panel"* when requesting gpio for MIPI/DSI pa
On Fri, Dec 02, 2016 at 09:48:59AM -0800, Manasi Navare wrote:
> On Fri, Dec 02, 2016 at 05:26:35PM +0100, Daniel Vetter wrote:
> > On Tue, Nov 29, 2016 at 11:30:31PM -0800, Manasi Navare wrote:
> > > At the time userspace does setcrtc, we've already promised the mode
> > > would work. The promise
On Fri, 2016-12-02 at 16:00 -0800, Rodrigo Vivi wrote:
> Along with GLK it was introduced the .is_lp and IS_GEN9_LP.
> So, following the same simplification standard we can
> put Skylake and Kabylake under the same bucket for most
> of the things.
>
> So let's add the IS_GEN9_BC for "Big Core" (no
Link to FDO regression query:
https://bugs.freedesktop.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&component=DRM%2FIntel&f0=OP&f1=OP&f2=short_desc&f3=keywords&f4=CP&f5=CP&j1=OR&known_name=i915%20regressions&list_id=600614&o2=anywordssubstr&o3=anywords
On 2016.12.04 23:57:18 +, Eric Engestrom wrote:
> 90d27a1 moved the lock before this error path but forgot to add an
> unlock here.
>
> Fixes: 90d27a1b180e51ef0713 ("drm/i915/gvt: fix deadlock in workload_thread")
> Cc: Pei Zhang
> Cc: Zhenyu Wang
> Signed-off-by: Eric Engestrom
> ---
Hi,
== Series Details ==
Series: drm/dp/mst: fix kernel oops when turning off secondary monitor
URL : https://patchwork.freedesktop.org/series/16337/
State : success
== Summary ==
Series 16337v1 drm/dp/mst: fix kernel oops when turning off secondary monitor
https://patchwork.freedesktop.org/api/1.
100% reproducible issue found on SKL SkullCanyon NUC with two external
DP daisy-chained monitors in DP/MST mode. When turning off or changing
the input of the second monitor the machine stops with a kernel
oops. This issue happened with 4.8.8 as well as drm/drm-intel-nightly.
This issue is traced
90d27a1 moved the lock before this error path but forgot to add an
unlock here.
Fixes: 90d27a1b180e51ef0713 ("drm/i915/gvt: fix deadlock in workload_thread")
Cc: Pei Zhang
Cc: Zhenyu Wang
Signed-off-by: Eric Engestrom
---
drivers/gpu/drm/i915/gvt/scheduler.c | 1 +
1 file changed, 1 insertion(
== Series Details ==
Series: drm/i915: Use memcpy_from_wc for GPU error capture
URL : https://patchwork.freedesktop.org/series/16323/
State : success
== Summary ==
Series 16323v1 drm/i915: Use memcpy_from_wc for GPU error capture
https://patchwork.freedesktop.org/api/1.0/series/16323/revisions
On all platforms we now always read the contents of buffers via the GTT,
i.e. using WC cpu access. Reads are slow, but they can be accelerated
with an internal read buffer using sse4.1 (movntqda). This is our
i915_memcpy_from_wc() routine which also checks for sse4.1 support and
so we can fallback
tree: git://anongit.freedesktop.org/drm-intel topic/core-for-CI
head: 11390213da1d7677b2ff16361a49cfa7a440da97
commit: 15bdcbcc55853f70237aca4baa4152f8396799d4 [7/9] kbuild: Disable PIE by
default
config: x86_64-rhel_gcov (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
re
17 matches
Mail list logo
