The most recent merge commit in airlied/drm-next has problems with
confusing old_crtc_state and new_crtc_state. Use the
for_each_oldnew_crtc_in_state macros to clean up the confusion,
and explicitly look at the correct state instead of looking at
asyh->state.
With these fixes it becomes more obvio
Am 15.08.2017 um 05:49 schrieb Sandy Huang:
> This adds support for Rockchip soc lvds found on rk3288
> Based on the patches from Mark yao and Heiko Stuebner
>
> Signed-off-by: Sandy Huang
> Signed-off-by: Mark Yao
> Signed-off-by: Heiko Stuebner
> ---
> drivers/gpu/drm/rockchip/Kconfig
The last part of drm_atomic_check_only is testing whether we need to
fail with -EINVAL when modeset is not allowed, but forgets to return
the value when atomic_check() fails first.
This results in -EDEADLK being replaced by -EINVAL, and the sanity
check in drm_modeset_drop_locks kicks in:
[ 308.
On Tue, Aug 15, 2017 at 11:57:06AM +0200, Maarten Lankhorst wrote:
> The last part of drm_atomic_check_only is testing whether we need to
> fail with -EINVAL when modeset is not allowed, but forgets to return
> the value when atomic_check() fails first.
>
> This results in -EDEADLK being replaced
Op 15-08-17 om 12:02 schreef Daniel Vetter:
> On Tue, Aug 15, 2017 at 11:57:06AM +0200, Maarten Lankhorst wrote:
>> The last part of drm_atomic_check_only is testing whether we need to
>> fail with -EINVAL when modeset is not allowed, but forgets to return
>> the value when atomic_check() fails fir
Quoting Christian König (2017-08-13 14:04:29)
> Am 11.08.2017 um 19:01 schrieb Chris Wilson:
> > This is an illegal scenario, to free the fence whilst there are pending
> > callbacks. Currently, we emit a WARN and then cast aside the callbacks
> > leaving them dangling. Alternatively, we could set
The NULL comment is referring to the path to line 3388 via line 3360. But
if the value is not NULL, there will be an update of previously freed
memory.
julia
-- Forwarded message --
Date: Tue, 15 Aug 2017 18:58:51 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
This looks like another variant of the code I just commented on, with the
same problems. Note also the comments about iterator index variables,
although the code is not shown. I haven't checked those issues.
julia
-- Forwarded message --
Date: Tue, 15 Aug 2017 17:33:08 +0800
Fro
Am 15.08.2017 um 13:23 schrieb Chris Wilson:
Quoting Christian König (2017-08-13 14:04:29)
Am 11.08.2017 um 19:01 schrieb Chris Wilson:
This is an illegal scenario, to free the fence whilst there are pending
callbacks. Currently, we emit a WARN and then cast aside the callbacks
leaving them dan
Since commit 4a97a3da420b ("drm: Don't update property values for atomic
drivers") atomic drivers must not update property values as properties
are read from the state instead. To catch remaining users, the
drm_object_property_set_value() function now throws a warning when
called by atomic drivers
Since commit 4a97a3da420b ("drm: Don't update property values for atomic
drivers") atomic drivers must not update property values as properties
are read from the state instead. To catch remaining users, the
drm_object_property_set_value() function now throws a warning when
called by atomic drivers
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Vedran Miletić changed:
What|Removed |Added
Depends on||102179
Referenced Bugs:
https://bugs.
From: Thierry Reding
Add tracepoint events for HDMI controller register accesses.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/hdmi.c | 8 +++-
drivers/gpu/drm/tegra/trace.h | 7 +++
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/tegra/hdmi.c
From: Thierry Reding
Register offsets are usually fairly small numbers, so an unsigned int is
more than enough to represent them.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dsi.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/tegra/dsi.
From: Thierry Reding
Add tracepoint events for DPAUX controller register accesses.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dpaux.c | 8 +++-
drivers/gpu/drm/tegra/trace.h | 7 +++
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/tegra/dpaux
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Vedran Miletić changed:
What|Removed |Added
Depends on||101415
Referenced Bugs:
https://bugs.
From: Thierry Reding
The mapping of PRIME buffers can reuse much of the GEM mapping code, so
extract the common bits into a new tegra_gem_mmap() helper.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/gem.c | 48 +++--
1 file changed, 33 insertio
From: Thierry Reding
None of the driver-specific IOCTLs are privileged, so mark them as such
and advertise that the driver supports render nodes.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/drm.c | 44 +---
1 file changed, 29 insertions(+), 1
From: Thierry Reding
The display architecture in Tegra186 changes slightly compared to
earlier Tegra generations, which requires that we recursively scan
host1x sub-devices from device tree.
Signed-off-by: Thierry Reding
---
drivers/gpu/host1x/bus.c | 26 +-
1 file chan
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Senad changed:
What|Removed |Added
Depends on||102233
Referenced Bugs:
https://bugs.freedeskt
On 15 August 2017 at 00:22, Jason Ekstrand wrote:
> /*
> + * Invalid Modifier
> + *
> + * This modifier can be used as a sentinel to terminate the format modifiers
> + * list, or to initialize a variable with an invalid modifier. It might also
> be
> + * used to report an error back to userspace
Laurent asked for this.
Cc: Laurent Pinchart
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/drm_connector.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
index ba9f36cef68c..b458eb488128 100644
--- a/
On Mon, Aug 14, 2017 at 04:22:51PM -0700, Jason Ekstrand wrote:
> Cc: Daniel Stone
pls read libdrm.git/include/drm/README.
-Daniel
> ---
> include/drm/drm_fourcc.h | 31 ++
> include/drm/drm_mode.h | 50
>
> 2 files
Quoting Thierry Reding (2017-08-15 14:42:40)
> From: Thierry Reding
>
> The mapping of PRIME buffers can reuse much of the GEM mapping code, so
> extract the common bits into a new tegra_gem_mmap() helper.
>
> Signed-off-by: Thierry Reding
> ---
> drivers/gpu/drm/tegra/gem.c | 48
> ++
https://bugs.freedesktop.org/show_bug.cgi?id=96783
Chris Wilson changed:
What|Removed |Added
Resolution|NOTOURBUG |---
Assignee|intel-gfx-bugs@lis
Signed-off-by: Boyuan Zhang
Acked-by: Alex Deucher
---
tests/amdgpu/Makefile.am | 1 +
tests/amdgpu/amdgpu_test.c | 6 +
tests/amdgpu/amdgpu_test.h | 15 ++
tests/amdgpu/frame.h | 2 +-
tests/amdgpu/uvd_enc_tests.c | 500
tests/amdg
On Tue, Aug 15, 2017 at 10:02 PM, Linus Walleij
wrote:
> On Mon, Aug 14, 2017 at 4:20 PM, Daniel Vetter wrote:
>
>> Wrt merging/maintaining: Want to include it in the drm-misc pile? We'll
>> happily throw commit rights at every driver submission (and honestly
>> expect that, since it helps tremen
https://bugs.freedesktop.org/show_bug.cgi?id=97220
--- Comment #4 from kenneth johansson ---
So I tried latest
git://people.freedesktop.org/~agd5f/linux
branch amd-staging-4.12
still not working.
aug 15 23:17:39 brix kernel: [drm] Atomic commit: SET crtc id 0:
[99ef99e9c000]
aug 15 23:17:
https://bugs.freedesktop.org/show_bug.cgi?id=97220
--- Comment #5 from Harry Wentland ---
I believe this is a tiled display. Correct me if I'm wrong. This means that
besides MST support (where we still have to iron out some bugs) this display
also requires tiled display support which we currently
https://bugs.freedesktop.org/show_bug.cgi?id=102203
Andy Furniss changed:
What|Removed |Added
CC||adf.li...@gmail.com
--- Comment #3 from
Hello,
This patch series fixes support for planes that cross the screen boundaries.
The KMS API supports such a configuration, but the DU and VSP hardware
doesn't. This leads to different kind of dispay artifacts or hangs.
The series starts with a bit of refactoring to share existing code and mak
The plane atomic check implementation is identical on Gen2 (DU planes)
and Gen3 (VSP planes), but two separate functions exist as they operate
on different data structures. Refactor the code to share the
implementation.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_du_plane.c
There is no point in accepting fully off-screen planes as they won't be
displayed. Reject them in the atomic check.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_du_plane.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/gpu/drm/rcar-du/rcar_du_pl
Unlike the KMS API, the hardware doesn't support planes exceeding the
screen boundaries. Clip plane coordinates to support the use case.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_du_plane.c | 66 +
drivers/gpu/drm/rcar-du/rcar_du_plane.h |
We want the adjusted_mode->clock to be the actual clock we're
expecting to program, so that consumers see the right values for clock
and vrefresh.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_dsi.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers
This driver communicates with the Atmel microcontroller for sequencing
the poweron of the TC358762 DSI-DPI bridge and controlling the
backlight PWM.
v2: Set the same default orientation as the closed source firmware
used, which is the best for viewing angle.
v3: Rewrite as an i2c client driver
The incoming mode might have a missing vrefresh field if it came from
drmModeSetCrtc(), which the kernel is supposed to calculate using
drm_mode_vrefresh(). We could either use that or the adjusted_mode's
original vrefresh value.
However, we can maintain a more exact vrefresh value (not just the
We need the following things to happen in sequence:
DSI host creation
DSI device creation in the panel driver (needs DSI host)
DSI device attach from panel to host.
DSI drm_panel_add()
DSI encoder creation
DSI encoder's DRM panel/bridge attach
Unless we allow device creation while the host isn't
This doesn't yet cover input, but the driver does get the display
working when the firmware is disabled from talking to our I2C lines.
Signed-off-by: Eric Anholt
Acked-by: Rob Herring
---
.../panel/raspberrypi,7inch-touchscreen.txt| 49 ++
1 file changed, 49 insertio
This patch fixes the following soft lockup:
BUG: soft lockup - CPU#0 stuck for 23s! [weston:307]
On weston idle-timeout the IP is powered down and reset
asserted. On weston resume we get a massive vblank
IRQ storm due to the LDI registers having lost some state.
This state loss is caused by ade
Hi Dmitry,
At 08/15/2017 03:18 PM, Dmitry Vyukov wrote:
Hello,
I am getting the following deadlock report while booting linux-next on
91dfed74eabcdae9378131546c446442c29bf769 in qemu. Config is attached.
WARNING: possible recursive locking detected
4.13.0-rc4-next-20170811 #2 Not tainted
Dear Michel,
On 2017-08-15 03:19, Michel Dänzer wrote:
On 15/08/17 02:48 AM, Paul Menzel wrote:
On 08/14/17 03:15, Michel Dänzer wrote:
On 11/08/17 01:02 AM, Paul Menzel wrote:
On 08/10/17 15:14, Paul Menzel wrote:
Xorg:
/dev/shm/bee-root/xorg-server/xorg-server-1.19.3-0/source/dix/dispatc
https://bugs.freedesktop.org/show_bug.cgi?id=97220
--- Comment #6 from kenneth johansson ---
I have no idea what a tiled display is.
If I use the Intel display port I get or more correctly used to get two
displays that I could then combine with xrandr into one larger. Now the kernel
driver prese
Hi Jan,
On 14 August 2017 at 03:44, Jan Vesely wrote:
> On Fri, 2017-07-28 at 10:23 -0400, Jan Vesely wrote:
>> Fixes: 7d8c9464081634f053e16e5eac9655a12fae1dc4
>> Signed-off-by: Jan Vesely
>
> ping.
> Emil, should I just drop this patch?
> another alternative is to remove the list implementation
> -Original Message-
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: Tuesday, August 15, 2017 10:50 PM
> To: Zhang, Tina
> Cc: intel-...@lists.freedesktop.org; intel-gvt-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org; ville.syrj...@
The function has far more in common with drm_syncobj_find than with
any in the get/put functions.
Signed-off-by: Jason Ekstrand
Acked-by: Christian König (v1)
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 2 +-
drivers/gpu/drm/drm_syncobj.c | 10 +-
include/drm/drm_syncobj.h
From: Dave Airlie
This interface will allow sync object to be used to back
Vulkan fences. This API is pretty much the vulkan fence waiting
API, and I've ported the code from amdgpu.
v2: accept relative timeout, pass remaining time back
to userspace.
v3: return to absolute timeouts.
v4: absolute
Vulkan VkFence semantics require that the application be able to perform
a CPU wait on work which may not yet have been submitted. This is
perfectly safe because the CPU wait has a timeout which will get
triggered eventually if no work is ever submitted. This behavior is
advantageous for multi-th
It is useful in certain circumstances to know when the fence is replaced
in a syncobj. Specifically, it may be useful to know when the fence
goes from NULL to something valid. This does make syncobj_replace_fence
a little more expensive because it has to take a lock but, in the common
case where
Hi all,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/gpu/drm/i915/i915_gem_execbuffer.c: In function 'get_fence_array':
drivers/gpu/drm/i915/i915_gem_execbuffer.c:2163:20: error: 'GFP_TEMPORARY'
undeclared (first use in this functi
https://bugzilla.kernel.org/show_bug.cgi?id=196635
--- Comment #9 from Janpieter Sollie (janpieter.sol...@dommel.be) ---
I just browsed through a few howtos:
It won't be easy to point to the problem: in 4.10, it hit a triple fault and
then crashed with dpm enabled. do you want a bisection from tha
https://bugzilla.kernel.org/show_bug.cgi?id=196635
--- Comment #10 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Janpieter Sollie from comment #9)
> It won't be easy to point to the problem: in 4.10, it hit a triple fault and
> then crashed with dpm enabled. do you want a bisection from
52 matches
Mail list logo
