Hi,
Dne torek, 09. oktober 2018 ob 19:40:44 CEST je Laurent Pinchart napisal(a):
> Hi Jernej,
>
> Thank you for the patch.
>
> On Sunday, 7 October 2018 12:38:51 EEST Jernej Skrabec wrote:
> > It turns out that even new DW HDMI controllers exhibits same magenta
> > line issues as older versions.
LEROY Christophe writes:
> Michael Ellerman a écrit :
>> Michael Ellerman writes:
>>> Christophe Leroy writes:
>>>
Set PAGE_KERNEL directly in the caller and do not rely on a
hack adding PAGE_KERNEL flags when _PAGE_PRESENT is not set.
As already done for PPC64, use pgprot_c
On 8/18/18 7:03 PM, Dmitry Osipenko wrote:
> Tiling modifier can't be applied to overlay planes because all tile
> modifiers are filtered out.
>
> Fixes: e90124cb46bdb ("drm/tegra: plane: Support format modifiers")
> Signed-off-by: Dmitry Osipenko
ping
___
When I enable UBSAN and compile this driver with clang I get the
following build error:
drivers/gpu/drm/i915/intel_engine_cs.o: In function
`intel_engine_init_execlist':
drivers/gpu/drm/i915/intel_engine_cs.c:411: undefined reference to
`__compiletime_assert_411'
from what I can figure out, the
We return 0 unconditionally in 'rcar_du_crtc_set_crc_source()'.
However, 'ret' is set to some error codes if some function calls fail.
Return 'ret' instead to propagate the error code.
Fixes: 47a52d024e89 ("media: drm: rcar-du: Add support for CRC computation")
Signed-off-by: Christophe JAILLET
On 11-10-18, 08:54, Jordan Crouse wrote:
I understand what you are trying to say Jordan and I agree with those
expectations. But what I am looking for is consistency across Qcom
code using the same feature. Which enables better support for the code
going forward, etc. And if we are going to go a d
On Mon, Oct 15, 2018 at 10:49:24AM -0400, Harry Wentland wrote:
> The leadership of freedesktop.org (fd.o) has recently expressed interest
> in having an elected governing body. Given the tight connection between
> fd.o and X.Org and the fact that X.Org has such a governing body it
> seemed obvious
The RADV bits are:
Reviewed-by: Samuel Pitoiset
Thanks!
On 10/16/18 7:31 AM, Keith Packard wrote:
Offers three clocks, device, clock monotonic and clock monotonic
raw. Could use some kernel support to reduce the deviation between
clock values.
v2:
Ensure deviation is at least as big
On Tue, Oct 16, 2018 at 7:31 AM Keith Packard wrote:
>
> Offers three clocks, device, clock monotonic and clock monotonic
> raw. Could use some kernel support to reduce the deviation between
> clock values.
>
> v2:
> Ensure deviation is at least as big as the GPU time interval.
>
> v3:
>
On Mon, 15 Oct 2018 12:02:14 -0400
"Kazlauskas, Nicholas" wrote:
> On 10/15/2018 09:57 AM, Pekka Paalanen wrote:
> > On Fri, 12 Oct 2018 08:58:23 -0400
> > "Kazlauskas, Nicholas" wrote:
> >
> >> On 10/12/2018 07:20 AM, Koenig, Christian wrote:
> >>> Am 12.10.2018 um 11:21 schrieb Pekka Paal
So far, struct ttm_bo_global_ref was the only way of initializing a struct
ttm_bo_global. Providing separate initializer and release functions for
struct ttm_bo_global gives drivers the option of implementing their own
init and release callbacks for drm_global_references of type
DRM_GLOBAL_TTM_BO.
The functions ttm_bo_global_init() and ttm_bo_global_release() do not
receive an argument of type struct ttm_bo_global. Both take a struct
drm_global_reference that contains points to a struct ttm_bo_global_ref.
Renaming them reflects this.
Signed-off-by: Thomas Zimmermann
---
Documentation/gpu/
TTM uses global memory and BO for backing graphics buffers. These are
represented by struct ttm_mem_global and struct ttm_bo_global.
Currently, struct ttm_bo_global can only be initialized and released through
struct ttm_bo_global_ref. This is a workaround for passing an instance of
ttm_mem_global
https://bugs.freedesktop.org/show_bug.cgi?id=107823
--- Comment #7 from Jan Burgmeier ---
Created attachment 142042
--> https://bugs.freedesktop.org/attachment.cgi?id=142042&action=edit
edid info from sysfs
Here is the edid info extracted from sysfs:
/sys/devices/pci:00/:00:01.0/drm/ca
https://bugs.freedesktop.org/show_bug.cgi?id=108386
Bug ID: 108386
Summary: How Do You Access 24*7 Live Quicken Support ?
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: norma
https://bugs.freedesktop.org/show_bug.cgi?id=108386
proadvisor247 changed:
What|Removed |Added
URL||https://www.proadvisor247.c
https://bugs.freedesktop.org/show_bug.cgi?id=106747
Lakshmi changed:
What|Removed |Added
Status|RESOLVED|CLOSED
Resolution|NOTOURBUG
https://bugs.freedesktop.org/show_bug.cgi?id=108262
--- Comment #2 from Lakshmi ---
Reporter were you able to verify with latest intel gpu tools?
Here you can find the latest intel gpu tools where you can build and install
latest intel gpu tools git://anongit.freedesktop.org/xorg/app/intel-gpu-t
https://bugs.freedesktop.org/show_bug.cgi?id=106747
--- Comment #7 from Martin Peres ---
(In reply to Lakshmi from comment #6)
> Closing this bug, as we were unable to reproduce this bug.
Yes, the new runner made this issue impossible.
--
You are receiving this mail because:
You are the assign
https://bugs.freedesktop.org/show_bug.cgi?id=108381
--- Comment #2 from Michel Dänzer ---
Please send the patch (with a commit log, generated by git format-patch) to the
mesa-dev mailing list for review.
--
You are receiving this mail because:
You are the assignee for the bug.__
Adding Hans, who broke this.
-Daniel
On Mon, Oct 15, 2018 at 6:20 AM Daniel Drake wrote:
>
> Hi,
>
> On Mon, Oct 8, 2018 at 1:48 PM Daniel Drake wrote:
> > I recently filed a bug report regarding graphics corruption seen on
> > Gemini Lake platforms:
> > https://bugs.freedesktop.org/show_bug.cgi?
On Tue, Oct 16, 2018 at 11:25 AM Daniel Vetter wrote:
> Adding Hans, who broke this.
Sorry, mixed up bugs, I think this is something else.
-Daniel
> -Daniel
> On Mon, Oct 15, 2018 at 6:20 AM Daniel Drake wrote:
> >
> > Hi,
> >
> > On Mon, Oct 8, 2018 at 1:48 PM Daniel Drake wrote:
> > > I rece
On Wed, Aug 29, 2018 at 12:23 PM Andrzej Hajda wrote:
> On 29.08.2018 12:01, Liviu Dudau wrote:
> > On Wed, Aug 29, 2018 at 11:58:20AM +0200, Andrzej Hajda wrote:
> >> On 28.08.2018 15:45, Linus Walleij wrote:
> >>> On Mon, Aug 27, 2018 at 1:53 PM Andrzej Hajda wrote:
> >>> I'm sorry RTSM is hal
Hi Swati,
On Mon, Oct 15, 2018 at 01:39:54PM +0530,
swatisha...@outlook.ms-acdc.office.com wrote:
> From: Vidya Srinivas
>
> The following pixel formats are packed format that follows 4:2:2
> chroma sampling. For memory represenation each component is
> allocated 16 bits each. Thus each pixel o
On Wed, Aug 29, 2018 at 2:16 PM Andrzej Hajda wrote:
> My question still stands: what is wrong/missing with dpi panel?
Hopefully described with my other answer :)
> I did not analyze details, but pl111 output seems to be DPI compatible.
This patch set is not trying to support the electronic de
The HVS block is supposed to fill the pixelvalve FIFOs fast enough to
meet the requested framerate. The problem is, the HVS and memory bus
bandwidths are limited, and if we don't take these limitations into
account we might end up with HVS underflow errors.
This patch is trying to model the per-pl
Hi Swati,
On Mon, Oct 15, 2018 at 01:39:54PM +0530,
swatisha...@outlook.ms-acdc.office.com wrote:
Btw, I can't reply to this address.
> From: Vidya Srinivas
>
>
> The following pixel formats are packed format that follows 4:2:2
> chroma sampling. For memory represenation each component is
> a
On Fri, Oct 12, 2018 at 05:35:55PM +0100, Alexandru Gheorghe wrote:
> Enable the following formats
> - DRM_FORMAT_X0L0: DP650
> - DRM_FORMAT_X0L2: DP550, DP650
>
> Signed-off-by: Alexandru Gheorghe
Acked-by: Liviu Dudau
> ---
> drivers/gpu/drm/arm/malidp_hw.c | 14 +++---
> driver
On Fri, Oct 12, 2018 at 05:35:54PM +0100, Alexandru Gheorghe wrote:
> Mali-DP implements a number of tiled yuv formats which are not
> currently described in drm_fourcc.h.
> This adds those definitions and describes their memory layout by
> using the newly added char_per_block, block_w, block_h.
>
On Mon, 15 Oct 2018, Stephen Boyd wrote:
> When I enable UBSAN and compile this driver with clang I get the
> following build error:
>
> drivers/gpu/drm/i915/intel_engine_cs.o: In function
> `intel_engine_init_execlist':
> drivers/gpu/drm/i915/intel_engine_cs.c:411: undefined reference to
> `__c
Hi Christophe,
Thank you for the patch.
On Tuesday, 16 October 2018 09:58:25 EEST Christophe JAILLET wrote:
> We return 0 unconditionally in 'rcar_du_crtc_set_crc_source()'.
> However, 'ret' is set to some error codes if some function calls fail.
>
> Return 'ret' instead to propagate the error c
Quoting Jani Nikula (2018-10-16 10:59:42)
> On Mon, 15 Oct 2018, Stephen Boyd wrote:
> > When I enable UBSAN and compile this driver with clang I get the
> > following build error:
> >
> > drivers/gpu/drm/i915/intel_engine_cs.o: In function
> > `intel_engine_init_execlist':
> > drivers/gpu/drm/i9
On Tue, 16 Oct 2018, Mamta Shukla wrote:
> Shift * to be adjacent to pointer name to follow Linux coding style.
> Issue found with checkpatch.pl
> ERROR: "foo * bar" should be "foo *bar"
The patch looks OK, but at this point, you know how to send a patch, so it
would be better to focus on chang
Am 16.10.2018 um 10:04 schrieb Thomas Zimmermann:
> The functions ttm_bo_global_init() and ttm_bo_global_release() do not
> receive an argument of type struct ttm_bo_global. Both take a struct
> drm_global_reference that contains points to a struct ttm_bo_global_ref.
> Renaming them reflects this.
Am 16.10.18 um 12:43 schrieb Koenig, Christian:
> Am 16.10.2018 um 10:04 schrieb Thomas Zimmermann:
>> The functions ttm_bo_global_init() and ttm_bo_global_release() do not
>> receive an argument of type struct ttm_bo_global. Both take a struct
>> drm_global_reference that contains points to a stru
On Monday, 2018-10-15 16:48:06 -0700, Lucas De Marchi wrote:
> LANG=C sort -u .gitignore | sponge .gitignore
>
> This way it's easier to keep track of the entries.
>
> Signed-off-by: Lucas De Marchi
Sure, why not:
Acked-by: Eric Engestrom
> ---
> .gitignore | 56 +++--
On Monday, 2018-10-15 16:48:07 -0700, Lucas De Marchi wrote:
> This is the directory used by meson/autotools (at least in the
> .gitlab-ci configuration) so ignore the whole dir.
This is extremely specific to this one case; what does this change for
the gitlab ci?
>
> Signed-off-by: Lucas De Mar
On Tue, 16 Oct 2018, Chris Wilson wrote:
> Quoting Jani Nikula (2018-10-16 10:59:42)
>> diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c
>> b/drivers/gpu/drm/i915/intel_engine_cs.c
>> index f27dbe26bcc1..897d5a557d88 100644
>> --- a/drivers/gpu/drm/i915/intel_engine_cs.c
>> +++ b/drivers/gpu/d
Make sure we always restart the timer after a timeout and remove the
device specific workarounds.
Signed-off-by: Christian König
---
drivers/gpu/drm/etnaviv/etnaviv_sched.c | 2 --
drivers/gpu/drm/scheduler/sched_main.c | 1 +
drivers/gpu/drm/v3d/v3d_sched.c | 3 ---
3 files changed, 1
Signal a fault to the scheduler on an illegal instruction or register
access violation instead of kicking of the reset handler directly.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 -
drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c | 21 -
drivers/
Add a helper to immediately start timeout handling in case of a hardware
fault.
Signed-off-by: Christian König
---
drivers/gpu/drm/scheduler/sched_main.c | 13 +
include/drm/gpu_scheduler.h| 1 +
2 files changed, 14 insertions(+)
diff --git a/drivers/gpu/drm/scheduler/s
Was never used.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/si_dma.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/si_dma.c
b/drivers/gpu/drm/amd/amdgpu/si_dma.c
index adbaea6da0d7..d9b27d7017dd 100644
--- a/drivers/gpu/drm/amd/a
On Mon, Oct 15, 2018 at 04:11:41PM +, Deepak Singh Rawat wrote:
> > On Wed, Oct 10, 2018 at 05:16:43PM -0700, Deepak Rawat wrote:
> > > Selftest for drm damage helper iterator functions.
> > >
> > > Cc: ville.syrj...@linux.intel.com
> > > Cc: Daniel Vetter
> > > Cc: Pekka Paalanen
> > > Cc: D
On Fri, Oct 12, 2018 at 12:16:10PM +0200, Hans de Goede wrote:
> The Acer One 10 uses a clamshell design with a detachable keyboard.
> As such in normal operating mode, with the keyboard attach the device
> is in landscape mode (and the Acer logo at boot also shows in landscape
> mode).
>
> But th
On Fri, Oct 12, 2018 at 05:36:00PM +0100, Alexandru Gheorghe wrote:
> Add selftests for the following newly added functions:
> - drm_format_info_block_width
> - drm_format_info_block_height
> - drm_format_info_min_pitch
>
> Signed-off-by: Alexandru Gheorghe
There's a bit a bikeshed going on with
On Fri, Oct 12, 2018 at 03:17:00PM -0500, Benoit Parrot wrote:
> Global shared resources (like hw overlays) for omapdrm are implemented
> as a part of atomic state using the drm_private_obj infrastructure
> available in the atomic core.
>
> omap_global_state is introduced as a drm atomic private o
On Mon, Oct 15, 2018 at 09:46:40AM -0400, sunpeng...@amd.com wrote:
> From: Leo Li
>
> This fixes a general protection fault, caused by accessing the contents
> of a flip_done completion object that has already been freed. It occurs
> due to the preemption of a non-blocking commit worker thread W
This adds the device tree bindings for the Samsung S6D16D0
panel. This is a command mode only panel using DSI.
Cc: devicet...@vger.kernel.org
Cc: Sam Ravnborg
Cc: Andrzej Hajda
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- None, if you're OK with it please ACK so I can queue
the patch.
The Samsung S6D16D0 is a simple comman mode only DSI display
that is used on the ST-Ericsson Ux500 reference design
TVK1281618 user interface board (UIB).
Cc: Sam Ravnborg
Cc: Andrzej Hajda
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Drop Backlight dependency from the Kconfig - this di
On Mon, Oct 15, 2018 at 02:05:29PM -0300, Rodrigo Siqueira wrote:
> For historical reason, the function drm_wait_vblank_ioctl always return
> -EINVAL if something gets wrong. This scenario limits the flexibility
> for the userspace make detailed verification of the problem and take
> some action. I
On Tue, Oct 16, 2018 at 12:30:16PM +0200, Julia Lawall wrote:
>
>
> On Tue, 16 Oct 2018, Mamta Shukla wrote:
>
> > Shift * to be adjacent to pointer name to follow Linux coding style.
> > Issue found with checkpatch.pl
> > ERROR: "foo * bar" should be "foo *bar"
>
> The patch looks OK, but at t
Le lun. 15 oct. 2018 à 11:12, Benjamin Gaignard
a écrit :
>
> Le sam. 13 oct. 2018 à 17:17, Christoph Hellwig a écrit :
> >
> > The DMA API does its own zone decisions based on the coherent_dma_mask.
> >
> > Signed-off-by: Christoph Hellwig
>
> Reviewed-by: Benjamin Gaignard
Christoph do you p
On Mon, Oct 15, 2018 at 10:33:06PM -0400, Lyude Paul wrote:
> Unfortunately, it appears our fix in:
> commit b5d29843d8ef ("drm/atomic_helper: Allow DPMS On<->Off changes
> for unregistered connectors")
>
> Which attempted to work around the problems introduced by:
> commit 4d80273976bf ("drm/atom
On Tue, Oct 16, 2018 at 02:21:17PM +0200, Daniel Vetter wrote:
> On Mon, Oct 15, 2018 at 04:11:41PM +, Deepak Singh Rawat wrote:
> > > On Wed, Oct 10, 2018 at 05:16:43PM -0700, Deepak Rawat wrote:
> > > > Selftest for drm damage helper iterator functions.
> > > >
> > > > Cc: ville.syrj...@linux
I've added my rb to patch #1 and pushed it to drm-misc-next.
I would really like to get an rb from other people on patch #2 before
proceeding.
Daniel, Dave and all the other usual suspects on the list what is your
opinion on this implementation?
Christian.
Am 15.10.2018 um 11:04 schrieb Ko
On Tue, Oct 16, 2018 at 11:40:45AM +0200, Boris Brezillon wrote:
> The HVS block is supposed to fill the pixelvalve FIFOs fast enough to
> meet the requested framerate. The problem is, the HVS and memory bus
> bandwidths are limited, and if we don't take these limitations into
> account we might en
Am Samstag, 13. Oktober 2018, 12:56:54 CEST schrieb Enric Balletbo i Serra:
> 'encoder' is deferenced before it is null sanity checked, hence we
> potentially have a null pointer dereference bug. Instead, initialise
> drm_drv from encoder->dev->dev_private after we are sure 'encoder' is
> not null.
Hi Daniel,
On Tue, 16 Oct 2018 14:57:43 +0200
Daniel Vetter wrote:
> On Tue, Oct 16, 2018 at 11:40:45AM +0200, Boris Brezillon wrote:
> > The HVS block is supposed to fill the pixelvalve FIFOs fast enough to
> > meet the requested framerate. The problem is, the HVS and memory bus
> > bandwidths
On Tue, Oct 16, 2018 at 3:10 PM Boris Brezillon
wrote:
>
> Hi Daniel,
>
> On Tue, 16 Oct 2018 14:57:43 +0200
> Daniel Vetter wrote:
>
> > On Tue, Oct 16, 2018 at 11:40:45AM +0200, Boris Brezillon wrote:
> > > The HVS block is supposed to fill the pixelvalve FIFOs fast enough to
> > > meet the req
https://bugzilla.kernel.org/show_bug.cgi?id=201439
Bug ID: 201439
Summary: Amdgpu: general protection fault at dce110_vblank_set
in display resume
Product: Drivers
Version: 2.5
Kernel Version: drm-next-4.21-wip
Hardware
On Tue, Oct 16, 2018 at 03:12:54PM +0200, Daniel Vetter wrote:
> On Tue, Oct 16, 2018 at 3:10 PM Boris Brezillon
> wrote:
> >
> > Hi Daniel,
> >
> > On Tue, 16 Oct 2018 14:57:43 +0200
> > Daniel Vetter wrote:
> >
> > > On Tue, Oct 16, 2018 at 11:40:45AM +0200, Boris Brezillon wrote:
> > > > The H
https://bugs.freedesktop.org/show_bug.cgi?id=80618
mirh changed:
What|Removed |Added
Status|NEW |NEEDINFO
CC|
Op 15-10-18 om 19:05 schreef Rodrigo Siqueira:
> For historical reason, the function drm_wait_vblank_ioctl always return
> -EINVAL if something gets wrong. This scenario limits the flexibility
> for the userspace make detailed verification of the problem and take
> some action. In particular, the v
On Mon, 15 Oct 2018, "Sharma, Shashank" wrote:
> Regards
>
> Shashank
>
>
> On 10/15/2018 4:39 PM, Jani Nikula wrote:
>> On Mon, 15 Oct 2018, Jani Nikula wrote:
>>> On Fri, 05 Oct 2018, clinton.a.tay...@intel.com wrote:
From: Clint Taylor
HDMI Forum VSDB YCBCR420 deep color capabi
Hi,
Le jeudi 29 mars 2018 à 09:56 +0200, Maxime Ripard a écrit :
> On Tue, Mar 27, 2018 at 10:08:48AM +0200, Paul Kocialkowski wrote:
> > On Fri, 2018-03-23 at 11:03 +0100, Maxime Ripard wrote:
> > > On Wed, Mar 21, 2018 at 04:28:58PM +0100, Paul Kocialkowski wrote:
> > > > In order to check wheth
tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.21-wip
head: 6af94a9d0e185f48bef5cc1372f3ada89d003858
commit: 15296db70619984157e60666da5da8994a66870e [10/27] drm/amdgpu/vcn:Add
ring W/R PTR check for VCN DPG mode stop
smatch warnings:
drivers/gpu/drm/amd/amdgpu/vcn_v1_0.c:1174
Hi,
Le vendredi 23 mars 2018 à 11:06 +0100, Maxime Ripard a écrit :
> On Wed, Mar 21, 2018 at 04:28:59PM +0100, Paul Kocialkowski wrote:
> > In order to check whether the frontend supports a specific format, an
> > explicit list and a related helper are introduced.
> >
> > They are then used to d
Hi folks,
I just randomly add some people that committed code to the
DSI core so I can get some reasonable feedback.
I started looking at some DSI drivers I'm adding and it seems
this platform (Ux500 MCDE) can control the bus frequency
of the DSI interface. It can be controlled independently for
ret_code should be initialized with 0. The check of read/write
ptr should be activate when UVD_POWER_STATUS_TILES is off.
Signed-off-by: James Zhu
---
drivers/gpu/drm/amd/amdgpu/vcn_v1_0.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/vcn_v1_0
Hi Dan,
Thanks! I send out the correct patch for review.
Best Regards!
James Zhu
On 2018-10-16 09:56 AM, Dan Carpenter wrote:
> tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.21-wip
> head: 6af94a9d0e185f48bef5cc1372f3ada89d003858
> commit: 15296db70619984157e60666da5da8994
On 16.10.2018 16:06, Linus Walleij wrote:
> Hi folks,
>
> I just randomly add some people that committed code to the
> DSI core so I can get some reasonable feedback.
>
> I started looking at some DSI drivers I'm adding and it seems
> this platform (Ux500 MCDE) can control the bus frequency
> of th
https://bugzilla.kernel.org/show_bug.cgi?id=201439
Michel Dänzer (mic...@daenzer.net) changed:
What|Removed |Added
CC||harry.wentl...@amd.co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrey Grodzovsky (2):
amdgpu/test: Allow BO mapping flags to be passed in tests
amdgpu/test: Fix deadlock tests for AI and RV v2
Rob Clark (14):
xf86drmHash: remove redundant zero init
freedreno/msm: get rid of ring_b
On 2018-10-16 08:33 AM, Daniel Vetter wrote:
> On Mon, Oct 15, 2018 at 09:46:40AM -0400, sunpeng...@amd.com wrote:
>> From: Leo Li
>>
>> This fixes a general protection fault, caused by accessing the contents
>> of a flip_done completion object that has already been freed. It occurs
>> due to th
Acked-by: Alex Deucher
From: amd-gfx on behalf of Zhu, James
Sent: Tuesday, October 16, 2018 10:15:01 AM
To: amd-...@lists.freedesktop.org
Cc: jzh...@gmail.com; dri-devel@lists.freedesktop.org; kbu...@01.org;
kbuild-...@01.org; dan.carpen...@oracle.com
Subject
On 10/16/18 4:26 AM, Eric Engestrom wrote:
On Monday, 2018-10-15 16:48:07 -0700, Lucas De Marchi wrote:
This is the directory used by meson/autotools (at least in the
.gitlab-ci configuration) so ignore the whole dir.
This is extremely specific to this one case; what does this change for
the g
Patches 1-3 Reviewed-by: Andrey Grodzovsky
Patch 4 Acked-by: Andrey Grodzovsky
Andrey
On 10/16/2018 07:55 AM, Christian König wrote:
> Make sure we always restart the timer after a timeout and remove the
> device specific workarounds.
>
> Signed-off-by: Christian König
> ---
> drivers/gpu/
https://bugs.freedesktop.org/show_bug.cgi?id=108379
--- Comment #1 from Alex Deucher ---
Please attach your xorg log (if using X) and dmesg output.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
On Tue, Oct 16, 2018 at 11:00 AM Li, Sun peng (Leo) wrote:
>
>
>
> On 2018-10-16 08:33 AM, Daniel Vetter wrote:
> > On Mon, Oct 15, 2018 at 09:46:40AM -0400, sunpeng...@amd.com wrote:
> >> From: Leo Li
> >>
> >> This fixes a general protection fault, caused by accessing the contents
> >> of a fli
From: Sean Paul
It causes a WARN in drm_atomic_get_plane_state(), and is not used by
atomic (or dpu).
Signed-off-by: Sean Paul
---
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
b/drivers/gpu/drm/msm/disp/dp
Hi Linus.
On Tue, Oct 16, 2018 at 02:34:08PM +0200, Linus Walleij wrote:
> This adds the device tree bindings for the Samsung S6D16D0
> panel. This is a command mode only panel using DSI.
>
> Cc: devicet...@vger.kernel.org
> Cc: Sam Ravnborg
> Cc: Andrzej Hajda
> Signed-off-by: Linus Walleij
>
> > > Obviously needs some adjusting on the igt side too, since we seem to be
> > > missing the igt scaffolding for tests-drm-helper.ko.
> > > -Daniel
> >
> > Hi Daniel,
> >
> > Thanks for the review. I am a little confused here. Should we have single
> > kernel module for drm plane helper selftest
This reverts commit 8e3b16e2117409625b89807de3912ff773aea354.
Using the component framework requires all components to undo in
->unbind what ->bind does. Unfortunately that particular commit
broke this rule. In particular, this is an issue if a single
component during probe fails. In that case, co
Hi Linus.
On Tue, Oct 16, 2018 at 02:34:09PM +0200, Linus Walleij wrote:
> The Samsung S6D16D0 is a simple comman mode only DSI display
> that is used on the ST-Ericsson Ux500 reference design
> TVK1281618 user interface board (UIB).
>
> Cc: Sam Ravnborg
> Cc: Andrzej Hajda
> Signed-off-by: Lin
>
> On Tue, Oct 16, 2018 at 02:21:17PM +0200, Daniel Vetter wrote:
> > On Mon, Oct 15, 2018 at 04:11:41PM +, Deepak Singh Rawat wrote:
> > > > On Wed, Oct 10, 2018 at 05:16:43PM -0700, Deepak Rawat wrote:
> > > > > Selftest for drm damage helper iterator functions.
> > > > >
> > > > > Cc: vill
On Tuesday, 2018-10-16 08:24:02 -0700, Lucas De Marchi wrote:
> On 10/16/18 4:26 AM, Eric Engestrom wrote:
> > On Monday, 2018-10-15 16:48:07 -0700, Lucas De Marchi wrote:
> > > This is the directory used by meson/autotools (at least in the
> > > .gitlab-ci configuration) so ignore the whole dir.
>
On Tue, Oct 16, 2018 at 03:36:20PM +0200, Maarten Lankhorst wrote:
> Op 15-10-18 om 19:05 schreef Rodrigo Siqueira:
> > For historical reason, the function drm_wait_vblank_ioctl always return
> > -EINVAL if something gets wrong. This scenario limits the flexibility
> > for the userspace make detail
On Tue, Oct 16, 2018 at 04:28:09PM +0300, Ville Syrjälä wrote:
> On Tue, Oct 16, 2018 at 03:12:54PM +0200, Daniel Vetter wrote:
> > On Tue, Oct 16, 2018 at 3:10 PM Boris Brezillon
> > wrote:
> > >
> > > Hi Daniel,
> > >
> > > On Tue, 16 Oct 2018 14:57:43 +0200
> > > Daniel Vetter wrote:
> > >
> >
On Tue, Oct 16, 2018 at 11:52:45AM -0400, Sean Paul wrote:
> From: Sean Paul
>
> It causes a WARN in drm_atomic_get_plane_state(), and is not used by
> atomic (or dpu).
>
> Signed-off-by: Sean Paul
Reviewed-by: Daniel Vetter
I guess leftover from refactoring and upstreaming in parallel?
-Dan
On Tue, Oct 16, 2018 at 06:09:23PM +0200, Stefan Agner wrote:
> This reverts commit 8e3b16e2117409625b89807de3912ff773aea354.
>
> Using the component framework requires all components to undo in
> ->unbind what ->bind does. Unfortunately that particular commit
> broke this rule. In particular, thi
Am Dienstag, den 16.10.2018, 18:09 +0200 schrieb Stefan Agner:
> This reverts commit 8e3b16e2117409625b89807de3912ff773aea354.
>
> Using the component framework requires all components to undo in
> ->unbind what ->bind does. Unfortunately that particular commit
> broke this rule. In particular, th
https://bugs.freedesktop.org/show_bug.cgi?id=107823
--- Comment #8 from raxon...@gmail.com ---
@Jan:
I was wondering can you see the issue with their staging branch?
Here is what I can recommend you to try :
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
If possible fo
On Tue, Oct 16, 2018 at 06:38:31PM +0200, Daniel Vetter wrote:
> On Tue, Oct 16, 2018 at 03:36:20PM +0200, Maarten Lankhorst wrote:
> > Op 15-10-18 om 19:05 schreef Rodrigo Siqueira:
> > > For historical reason, the function drm_wait_vblank_ioctl always return
> > > -EINVAL if something gets wrong.
https://bugs.freedesktop.org/show_bug.cgi?id=108317
--- Comment #9 from Nicolai Hähnle ---
Thanks for the report. An apitrace that reproduces the problem would be
extremely helpful.
--
You are receiving this mail because:
You are the assignee for the bug.
On Tue, Oct 16, 2018 at 12:44 PM Daniel Vetter wrote:
>
> On Tue, Oct 16, 2018 at 11:52:45AM -0400, Sean Paul wrote:
> > From: Sean Paul
> >
> > It causes a WARN in drm_atomic_get_plane_state(), and is not used by
> > atomic (or dpu).
> >
> > Signed-off-by: Sean Paul
>
> Reviewed-by: Daniel Vett
On Tue, Oct 16, 2018 at 06:41:51PM +0200, Daniel Vetter wrote:
> On Tue, Oct 16, 2018 at 04:28:09PM +0300, Ville Syrjälä wrote:
> > On Tue, Oct 16, 2018 at 03:12:54PM +0200, Daniel Vetter wrote:
> > > On Tue, Oct 16, 2018 at 3:10 PM Boris Brezillon
> > > wrote:
> > > >
> > > > Hi Daniel,
> > > >
>
On Tue, Oct 16, 2018 at 7:39 PM Ville Syrjälä
wrote:
>
> On Tue, Oct 16, 2018 at 06:41:51PM +0200, Daniel Vetter wrote:
> > On Tue, Oct 16, 2018 at 04:28:09PM +0300, Ville Syrjälä wrote:
> > > On Tue, Oct 16, 2018 at 03:12:54PM +0200, Daniel Vetter wrote:
> > > > On Tue, Oct 16, 2018 at 3:10 PM Bo
On Tue, Oct 16, 2018 at 7:28 PM Ville Syrjälä
wrote:
>
> On Tue, Oct 16, 2018 at 06:38:31PM +0200, Daniel Vetter wrote:
> > On Tue, Oct 16, 2018 at 03:36:20PM +0200, Maarten Lankhorst wrote:
> > > Op 15-10-18 om 19:05 schreef Rodrigo Siqueira:
> > > > For historical reason, the function drm_wait_v
https://bugs.freedesktop.org/show_bug.cgi?id=104362
--- Comment #9 from Vladimir Usikov ---
My Radeon 7950 dead, can`t test any more.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.f
Le lun. 15 oct. 2018 à 10:00, Daniel Vetter a écrit :
>
> On Fri, Oct 12, 2018 at 11:46:39AM +0200, Benjamin Gaignard wrote:
> > Since drm_atomic_helper_shutdown() rework it is possible to do additional
> > clean up in sti driver: custom plane destroy functions become useless and
> > clean up enco
1 - 100 of 161 matches
Mail list logo
