On Sun, Apr 21, 2019 at 01:59:04AM +0300, Laurent Pinchart wrote:
> Hi Daniel,
>
> On Thu, Apr 18, 2019 at 12:07:44PM +0200, Daniel Vetter wrote:
> > On Thu, Apr 18, 2019 at 11:02 AM Maxime Ripard wrote:
> > > On Thu, Apr 18, 2019 at 09:52:10AM +0200, Daniel Vetter wrote:
> > > > On Thu, Apr 18, 2
On Sun, Apr 21, 2019 at 01:40:45AM +0300, Laurent Pinchart wrote:
> Hi Paul,
>
> On Thu, Apr 18, 2019 at 01:49:54PM +0200, Paul Kocialkowski wrote:
> > On Thu, 2019-04-18 at 11:02 +0200, Maxime Ripard wrote:
> > > On Thu, Apr 18, 2019 at 09:52:10AM +0200, Daniel Vetter wrote:
> > >> And a lot of p
On Thu, Apr 18, 2019 at 01:15:17PM +, Mun, Gwan-gyeong wrote:
> On Thu, 2019-04-18 at 10:28 +0200, Daniel Vetter wrote:
> > On Thu, Apr 18, 2019 at 11:09:29AM +0300, Gwan-gyeong Mun wrote:
> > > The hotplug detection routine of drm_helper_hpd_irq_event() can
> > > detect
> > > changing of statu
tree: git://people.freedesktop.org/~airlied/linux.git drm-legacy-cleanup
head: 7b7678e3949f22d2442179f27d219b4b09ef1730
commit: 739d8489bcb277a1a27e56d0ef529f41c46425b4 [13/24] drm/nouveau: add
kconfig option to turn off nouveau legacy contexts. (v2)
config: arm-lpc18xx_defconfig (attached as
On Thu, Apr 18, 2019 at 10:41:35AM +0200, Thomas Gleixner wrote:
> Replace the indirection through struct stack_trace by using the storage
> array based interfaces.
>
> The original code in all printing functions is really wrong. It allocates a
> storage array on stack which is unused because depo
On Thu, Apr 18, 2019 at 02:27:54PM +0530, Ramalingam C wrote:
> Content protection property is created once and stored in
> drm_mode_config. And attached to all HDCP capable connectors.
>
> Signed-off-by: Ramalingam C
Reviewed-by: Daniel Vetter
> ---
> drivers/gpu/drm/drm_atomic_uapi.c | 4 +
On Thu, Apr 18, 2019 at 02:27:56PM +0530, Ramalingam C wrote:
> This patch adds a DRM ENUM property to the selected connectors.
> This property is used for mentioning the protected content's type
> from userspace to kernel HDCP authentication.
>
> Type of the stream is decided by the protected con
Hi
On Sun, Apr 21, 2019 at 12:43 AM Laurent Pinchart
wrote:
>
> Hi Tomi,
>
> Thank you for the patch.
>
> On Tue, Mar 26, 2019 at 12:31:36PM +0200, Tomi Valkeinen wrote:
> > For some reason the driver has a msleep(100) after writing to
> > DP_PHY_CTRL. Toshiba's documentation doesn't suggest any
On Tue, 23 Apr 2019, David Santamaría Rogado wrote:
> Hi Jani,
>
> When are the changes in drm-misc-next pushed?
>
> I'm testing recent kernels that don't work with some models because
> the dsi display problem you are aware. Works with 4.15 but not with
> more recent kernels.
>
> The model I have
On Fri, Apr 19, 2019 at 05:57:09PM +0200, Marc-André Lureau wrote:
> This patch does more harm than good, as it breaks both Xwayland and
> gnome-shell with X11.
>
> Xwayland requires DRI3 & DRI3 requires PRIME.
>
> X11 crash for obscure double-free reason which are hard to debug
> (starting X11 b
Hi,
> > The DRI3 code extensively uses prime_handle_to_fd and
> > prime_fd_to_handle for self-import.
The callbacks are not used for self-import.
> I believe the cap was removed because the driver only supports
> self-import. But the driver only runs inside VMs where there is no(?)
> other dm
On Thu, Apr 18, 2019 at 02:27:57PM +0530, Ramalingam C wrote:
> Attaches the content type property for HDCP2.2 capable connectors.
>
> Implements the update of content type from property and apply the
> restriction on HDCP version selection.
>
> v2:
> s/cp_content_type/content_protection_type [
On Thu, Apr 18, 2019 at 02:09:25PM +0200, Christian König wrote:
> Add a peer2peer flag noting that the importer can deal with device
> resources which are not backed by pages.
>
> Signed-off-by: Christian König
Should we add something like "Such importers should also support dynamic
dma_buf att
On Tue, Apr 23, 2019 at 10:16:50AM +0200, Daniel Vetter wrote:
> On Thu, Apr 18, 2019 at 02:09:25PM +0200, Christian König wrote:
> > Add a peer2peer flag noting that the importer can deal with device
> > resources which are not backed by pages.
> >
> > Signed-off-by: Christian König
>
> Should
Hi Laurent,
On Sun, Apr 21, 2019 at 12:14 AM Laurent Pinchart
wrote:
>
> Hi Tomi,
>
> Thank you for the patch.
>
> On Tue, Mar 26, 2019 at 12:31:27PM +0200, Tomi Valkeinen wrote:
> > DP always uses ANSI 8B10B encoding. Some monitors (old?) may not have
> > the ANSI 8B10B bit set in DPCD, even if
On Fri, Apr 19, 2019 at 07:19:04PM +0100, Chris Wilson wrote:
> sync_dump() is an unused, unexported, function that adds 64k to the
> kernel image and doesn't even provide locking around the global array it
> uses.
>
> add/remove: 0/2 grow/shrink: 0/0 up/down: 0/-65734 (-65734)
> Function
Hi,
On Mon, 2019-04-15 at 13:48 -0700, Eric Anholt wrote:
> Paul Kocialkowski writes:
>
> > Since the OOM interrupt directly deals with the binner bo, it doesn't
> > make sense to try and handle it without a binner buffer registered.
> >
> > Signed-off-by: Paul Kocialkowski
> > ---
> > driver
Quoting Daniel Vetter (2019-04-23 09:21:16)
> On Fri, Apr 19, 2019 at 07:19:04PM +0100, Chris Wilson wrote:
> > sync_dump() is an unused, unexported, function that adds 64k to the
> > kernel image and doesn't even provide locking around the global array it
> > uses.
> >
> > add/remove: 0/2 grow/sh
https://bugs.freedesktop.org/show_bug.cgi?id=110472
Michel Dänzer changed:
What|Removed |Added
QA Contact|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop
On Tue, 2019-04-23 at 10:30 +0200, Paul Kocialkowski wrote:
> Hi,
>
> On Mon, 2019-04-15 at 13:48 -0700, Eric Anholt wrote:
> > Paul Kocialkowski writes:
> >
> > > Since the OOM interrupt directly deals with the binner bo, it doesn't
> > > make sense to try and handle it without a binner buffer
https://bugs.freedesktop.org/show_bug.cgi?id=110478
Michel Dänzer changed:
What|Removed |Added
Component|Driver/AMDgpu |DRM/AMDgpu
QA Contact|xorg-t...
Hi,
On Tue, 23 Apr 2019 at 08:26, Daniel Vetter wrote:
> On Sun, Apr 21, 2019 at 01:59:04AM +0300, Laurent Pinchart wrote:
> > > > > - drm fourcc code doesn't actually define the drm_format_info
> > > > > uniquely, drivers can override that (that's an explicit design
> > > > > intent of modif
On Sat, 20 Apr 2019 at 05:25, John Stultz wrote:
>
> From: Sean Paul
>
> __mmap2 isn't supported on all platforms, mmap64 is the right way
> to do this in android.
>
> Also folds in a fix from Stéphane Marchesin
> to use an offset in bytes not pages, as that's what mmap64 takes.
>
> Cc: Emil Vel
https://bugs.freedesktop.org/show_bug.cgi?id=109456
--- Comment #3 from libgra...@gmail.com ---
Created attachment 144077
--> https://bugs.freedesktop.org/attachment.cgi?id=144077&action=edit
Dmesg output from failed Xorg start
--
You are receiving this mail because:
You are the assignee for t
https://bugs.freedesktop.org/show_bug.cgi?id=109456
--- Comment #4 from libgra...@gmail.com ---
Created attachment 144078
--> https://bugs.freedesktop.org/attachment.cgi?id=144078&action=edit
Xorg output from failed Xorg start
--
You are receiving this mail because:
You are the assignee for th
On Sat, 20 Apr 2019 at 05:25, John Stultz wrote:
>
> From: Adrian Salido
>
> When calling drmModeAtomicAddProperty allocation of memory happens as
> needed in increments of 16 elements. This can be very slow if there are
> multiple properties to be updated in an Atomic Commit call.
>
> Increase t
On Sat, 20 Apr 2019 at 05:25, John Stultz wrote:
>
> Clang complains when initializing unions using "= {0}"
> so instead use memset.
>
> Cc: Emil Velikov
> Cc: Sean Paul
> Cc: Alistair Strachan
> Cc: Marissa Wall
> Signed-off-by: John Stultz
Reviewed-by: Emil Velikov
-Emil
https://bugs.freedesktop.org/show_bug.cgi?id=109456
--- Comment #5 from libgra...@gmail.com ---
Have compiled 5.0.7 with the commit indicated by the bisect reverted and it
boots to Xorg fine.
Running an OpenGL application subsequently will hang the VM though.
--
You are receiving this mail beca
Am Sonntag, 21. April 2019, 10:25:50 CEST schrieb Jonas Karlman:
> When ddc-i2c-bus property is used, a NULL pointer dereference is reported:
>
> [ 31.041669] Unable to handle kernel NULL pointer dereference at virtual
> address 0008
> [ 31.041671] pgd = 4d3c16f6
> [ 31.041673] [000
On Sat, 20 Apr 2019 at 05:25, John Stultz wrote:
>
> From: Hemant Hariyani
>
> Allows mmap on dmabuf fd with MAP_SHARED and PROT_WRITE.
>
> This fixes boot failures caused due to mmap() returning error
>
Commit message is quite meh - xf86-video-omap does not use the API, so
things should work (tm
On Sat, Apr 13, 2019 at 6:54 PM wrote:
> From: Ondrej Jirman
>
> H6 has a different I/O voltage bias setting method than A80. Prepare
> existing code for using alternative bias voltage setting methods.
>
> Signed-off-by: Ondrej Jirman
> Acked-by: Maxime Ripard
This patch applied to the pinctr
On Sat, Apr 13, 2019 at 6:54 PM wrote:
> From: Ondrej Jirman
>
> H6 SoC has a "pio group withstand voltage mode" register (datasheet
> description), that needs to be used to select either 1.8V or 3.3V I/O mode,
> based on what voltage is powering the respective pin banks and is thus used
> for I
Add support for scaling on writeback. To do this add writeback_dest_w
and writeback_dest_h as writeback connector properties to specify the
desired output dimensions.
Then implement downscaling on writeback for Malidp-550 and Malidp-650
(upscaling on writeback is not supported on these devices).
v
Add new properties to specify width and height for writeback.
Signed-off-by: Ben Davis
---
drivers/gpu/drm/drm_atomic_uapi.c | 8
drivers/gpu/drm/drm_writeback.c | 30 ++
include/drm/drm_connector.h | 4
include/drm/drm_mode_config.h | 10 +
The phase setting part of malidp_crtc_atomic_check_scaling is refactored
to allow use in writeback scaling.
Also the enable_memwrite function prototype is simplified by directly
passing mw_state.
Signed-off-by: Ben Davis
---
drivers/gpu/drm/arm/malidp_crtc.c | 49 +++-
drivers/g
On Mon, Feb 18, 2019 at 09:27:04PM -0300, Fabio Estevam wrote:
> VXT Ltd is a manufacturer of projected capacitive touch panel
> and display solutions: http://www.vxt.com.tw/
>
> Reviewed-by: Otavio Salvador
> Reviewed-by: Rob Herring
> Signed-off-by: Fabio Estevam
> ---
> Changes since v1:
> -
On 20/04/2019 20:24, Noralf Trønnes wrote:
>
>
> Den 20.04.2019 12.45, skrev Noralf Trønnes:
>> This moves the modesetting code from drm_fb_helper to drm_client so it
>> can be shared by all internal clients.
>>
>> Changes this time:
>> - Use full drm_client_init/release for the modesets (Daniel
On Fri, Feb 22, 2019 at 06:51:52PM +0100, Paweł Chmiel wrote:
> From: Jonathan Bakker
>
> This commit adds documentation for Samsung s6e63m0 AMOLED LCD panel
> driver.
>
> Signed-off-by: Jonathan Bakker
> Signed-off-by: Paweł Chmiel
> Reviewed-by: Rob Herring
> ---
> Changes from v2:
> - Ad
On 2019-04-23 at 10:11:48 +0200, Daniel Vetter wrote:
> On Thu, Apr 18, 2019 at 02:27:57PM +0530, Ramalingam C wrote:
> > Attaches the content type property for HDCP2.2 capable connectors.
> >
> > Implements the update of content type from property and apply the
> > restriction on HDCP version sel
https://bugs.freedesktop.org/show_bug.cgi?id=104611
--- Comment #10 from Kevin Hamacher ---
Created attachment 144079
--> https://bugs.freedesktop.org/attachment.cgi?id=144079&action=edit
Nullptr deref after powercycling MST display
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=104611
--- Comment #11 from Kevin Hamacher ---
I'm also affected by this.
Setup:
GPUs: RX 580 (used), R9 Fury
Screens: 3xU2415, connected via DP. 2 of them connected via MST, 1 HDMI to
disabled screen, 1 HDMI to Oculus Rift VR
Linux x7 5.0.7-arch1-1
On Wed, Feb 20, 2019 at 09:21:55AM +0100, Maxime Ripard wrote:
> The Ronbo RB070D30 panel is a 1024x600 MIPI-DSI panel.
>
> Signed-off-by: Maxime Ripard
> ---
> Documentation/devicetree/bindings/display/panel/ronbo,rb070d30.yaml | 52
>
> 1 f
Hi
Am 17.04.19 um 09:54 schrieb Maxime Ripard:
> Move the DRM formats API to turn this into a more generic image formats API
> to be able to leverage it into some other places of the kernel, such as
> v4l2 drivers.
Here's some nitpicking: 'image_format_*' appears slightly vague; it
could refer to
Hi Laurent,
On Thu, Apr 18, 2019 at 09:27:11AM +0300, Laurent Pinchart wrote:
> The V4L2 API is missing the 16-bit RGB555 formats for the RGBA, RGBX,
> ABGR, XBGR, BGRA and BGRX component orders. Add them, using the same
> 4CCs as DRM.
>
> Signed-off-by: Laurent Pinchart
> ---
> Changes since v1:
On Tue, Feb 26, 2019 at 09:55:19AM +0200, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v2:
> - Added Reviewed-by from Rob to the binding patches
> - Added help text to Kconfig (osd101t2587-53ts)
> - Print the error values in dev_err/warn
> - Added Reviewed-by from Sam to the osd101t2587-53ts patc
On Tue, 23 Apr 2019 at 09:05, Gerd Hoffmann wrote:
>
> Hi,
>
> > > The DRI3 code extensively uses prime_handle_to_fd and
> > > prime_fd_to_handle for self-import.
>
> The callbacks are not used for self-import.
>
Userspace converts from it's own handles to a dmabuf fd and vice-versa.
I assumed t
On Tue, Feb 26, 2019 at 10:11:53AM +0200, Peter Ujfalusi wrote:
> In case mipi_dsi_attach() fails remove the registered panel to avoid added
> panel without corresponding device.
>
> Signed-off-by: Peter Ujfalusi
> ---
> drivers/gpu/drm/panel/panel-simple.c | 9 -
> 1 file changed, 8 ins
On Tue, Mar 26, 2019 at 03:02:08PM +0800, Jerry Han wrote:
> The Boe Himax8279d is a 8.0" panel with a 1200x1920 resolution and
> connected to DSI using four lanes.
>
> V7:
> - Add the information of the reviewer
>
> V6:
> - Add the information of the reviewer
>
> V5:
> - Added changelog
>
> V4
On Tue, Mar 26, 2019 at 03:09:33PM +0800, Jerry Han wrote:
> Support Boe Himax8279d 8.0" 1200x1920 TFT LCD panel, it is a MIPI DSI
> panel.
>
> V7:
> - Add the information of the reviewer
> - Remove unnecessary delays, The udelay_range code gracefully returns
> without hitting the scheduler on
On Tue, Apr 23, 2019 at 1:15 PM Ramalingam C wrote:
>
> On 2019-04-23 at 10:11:48 +0200, Daniel Vetter wrote:
> > On Thu, Apr 18, 2019 at 02:27:57PM +0530, Ramalingam C wrote:
> > > Attaches the content type property for HDCP2.2 capable connectors.
> > >
> > > Implements the update of content type
On Tue, Feb 19, 2019 at 03:04:37PM +0100, Marek Vasut wrote:
> Document the Emerging Display Technology Corp. (EDT) ETM0430G0DH6
> display, which is a 480x272 4.3" TFT display.
>
> Signed-off-by: Marek Vasut
> Cc: Rob Herring
> Cc: Jan Tuerk
> Cc: Thierry Reding
> Cc: devicet...@vger.kernel.or
On Fri, Mar 22, 2019 at 10:33:34AM +0200, Jyri Sarha wrote:
> Changes since v6:
> - Make power-supply a mandatory property
> - Split binding to a separate patch
> - Drop Tomi's reviewed-by, since the patch has changed quite a bit since his
> review
>
> Previous round:
> https://patchwork.kernel.
On Sun, Apr 14, 2019 at 12:59:10AM +0530, Souptick Joarder wrote:
> Remove duplicate header which is included twice.
>
> Signed-off-by: Souptick Joarder
> ---
> drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c | 1 -
> 1 file changed, 1 deletion(-)
Applied, thanks.
Thierry
signature.asc
On Tue, Apr 16, 2019 at 12:16:29PM +0200, Marco Felsch wrote:
> Add support for the ET035012DM6 3.5" QVGA TFT LCD panel. The datasheet
> can be retrieved online:
>
> https://www.glynshop.com/erp/owweb/Daten/DSS/EDT/Products/ \
> Specifications/Active%20Displays/ET035012DM6.pdf
>
> Signed-off-by:
On Tue, Apr 23, 2019 at 12:48 PM Ben Davis wrote:
>
> Add support for scaling on writeback. To do this add writeback_dest_w
> and writeback_dest_h as writeback connector properties to specify the
> desired output dimensions.
> Then implement downscaling on writeback for Malidp-550 and Malidp-650
>
On Tue, Apr 16, 2019 at 12:06:44PM +0200, Marco Felsch wrote:
> Add support for the Evervision VG804821 800x480 5.0" LCD TFT parallel
> panel to DRM simple panel driver.
>
> Signed-off-by: Marco Felsch
> Reviewed-by: Rob Herring
> ---
> .../bindings/display/panel/evervision,vgg804821.txt | 12
On Tue, Apr 16, 2019 at 12:06:43PM +0200, Marco Felsch wrote:
> Evervision Electronics is a panel manufacturer from Taipei.
> http://www.evervisionlcd.com/index.php?lang=en
>
> Signed-off-by: Marco Felsch
> Reviewed-by: Rob Herring
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt |
On Tue, Apr 16, 2019 at 12:06:45PM +0200, Marco Felsch wrote:
> Add support the Evervision VGG804821 800x480 5.0" WVGA TFT panel.
>
> Signed-off-by: Marco Felsch
> ---
> v2:
> - pixel data should be driven on neg. edge since the panel applies
> the data on positiv edge.
>
> drivers/gpu/drm/pa
Well you at least have to give me time till after the holidays to get
going again :)
Not sure exactly jet why we need patch number 5.
And we should probably commit patch #1 and #2.
Christian.
Am 22.04.19 um 13:54 schrieb Grodzovsky, Andrey:
> Ping for patches 3, new patch 5 and patch 6.
>
> An
Remove the check for IOMMU presence since it was considered a
layer violation.
This means we have no reliable way to destinguish between coherent
hardware IOMMU DMA address translations and incoherent SWIOTLB DMA
address translations, which we can't handle. So always presume the
former. This means
Hi,
On Tue, 2019-04-23 at 09:30 +0200, Daniel Vetter wrote:
> On Sun, Apr 21, 2019 at 01:40:45AM +0300, Laurent Pinchart wrote:
> > Hi Paul,
> >
> > On Thu, Apr 18, 2019 at 01:49:54PM +0200, Paul Kocialkowski wrote:
> > > On Thu, 2019-04-18 at 11:02 +0200, Maxime Ripard wrote:
> > > > On Thu, Apr
Am 23.04.19 um 14:31 schrieb Serge Semin:
> Since commit 4b050ba7a66c ("MIPS: pgtable.h: Implement the
> pgprot_writecombine function for MIPS") and commit c4687b15a848 ("MIPS: Fix
> definition of pgprot_writecombine()") write-combine vma mapping is
> available to be used by kernel subsystems for M
Am 19.04.19 um 19:13 schrieb Alex Deucher:
On Thu, Apr 18, 2019 at 8:09 AM Christian König
wrote:
A lot of root complexes can still do P2P even when PCI devices
don't share a common upstream bridge.
Start adding a whitelist and allow P2P if both participants are
attached to known good root com
On 21/04/2019 10:25, Jonas Karlman wrote:
> When ddc-i2c-bus property is used, a NULL pointer dereference is reported:
>
> [ 31.041669] Unable to handle kernel NULL pointer dereference at virtual
> address 0008
> [ 31.041671] pgd = 4d3c16f6
> [ 31.041673] [0008] *pgd=
> [
On Tue, Apr 23, 2019 at 12:26:02PM +0200, Heiko Stuebner wrote:
> Am Sonntag, 21. April 2019, 10:25:50 CEST schrieb Jonas Karlman:
> > When ddc-i2c-bus property is used, a NULL pointer dereference is reported:
> >
> > [ 31.041669] Unable to handle kernel NULL pointer dereference at virtual
> >
Am 22.04.19 um 20:35 schrieb John Stultz:
On Mon, Apr 22, 2019 at 7:59 AM Alex Deucher wrote:
On Sat, Apr 20, 2019 at 12:25 AM John Stultz wrote:
Clang complains when initializing unions using "= {0}"
so instead use memset.
Cc: Emil Velikov
Cc: Sean Paul
Cc: Alistair Strachan
Cc: Marissa
Hi,
On Mon, 2019-04-15 at 13:50 -0700, Eric Anholt wrote:
> Paul Kocialkowski writes:
>
> > The binner bo is not required until the V3D is in use, so avoid
> > allocating it at probe and do it on the first non-dumb BO allocation.
> > Keep track of which clients are using the V3D and liberate the
Am 23.04.19 um 12:26 schrieb Emil Velikov:
On Sat, 20 Apr 2019 at 05:25, John Stultz wrote:
From: Hemant Hariyani
Allows mmap on dmabuf fd with MAP_SHARED and PROT_WRITE.
This fixes boot failures caused due to mmap() returning error
Commit message is quite meh - xf86-video-omap does not us
Hi Thierry,
On 23/04/2019 14.55, Thierry Reding wrote:
> On Tue, Feb 26, 2019 at 09:55:19AM +0200, Peter Ujfalusi wrote:
>> Hi,
>>
>> Changes since v2:
>> - Added Reviewed-by from Rob to the binding patches
>> - Added help text to Kconfig (osd101t2587-53ts)
>> - Print the error values in dev_err/w
On Tue, Apr 23, 2019 at 02:24:11PM +0200, Daniel Vetter wrote:
> On Tue, Apr 23, 2019 at 12:48 PM Ben Davis wrote:
> >
> > Add support for scaling on writeback. To do this add writeback_dest_w
> > and writeback_dest_h as writeback connector properties to specify the
> > desired output dimensions.
https://bugs.freedesktop.org/show_bug.cgi?id=110481
--- Comment #2 from Christian König ---
(In reply to baopeng from comment #0)
> - if (p->ring->funcs->parse_cs || p->ring->funcs->patch_cs_in_place) {
> + if (0)
> If we don't delete, vce will be very slow.
>
> Is this the fundamental
Well that is certainly a NAK because it can lead to deadlock in the
memory management.
You can't just busy wait with all those locks held.
Regards,
Christian.
Am 23.04.19 um 03:45 schrieb Liang, Prike:
Acked-by: Prike Liang
Thanks,
Prike
-Original Message-
From: Chunming Zhou
Sent:
Am 23.04.19 um 04:00 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/radeon/radeon_drv.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/radeon/radeon_drv.h
b/drivers/gpu/drm/radeon/radeon_drv.h
inde
Feel free to merge 1+2 since they don't really depend on any other work
in the series and they were previously reviewed.
Nicholas Kazlauskas
On 4/23/19 8:32 AM, Koenig, Christian wrote:
> Well you at least have to give me time till after the holidays to get
> going again :)
>
> Not sure exactly
On Tue, Apr 23, 2019 at 04:00:26PM +0300, Peter Ujfalusi wrote:
> Hi Thierry,
>
> On 23/04/2019 14.55, Thierry Reding wrote:
> > On Tue, Feb 26, 2019 at 09:55:19AM +0200, Peter Ujfalusi wrote:
> >> Hi,
> >>
> >> Changes since v2:
> >> - Added Reviewed-by from Rob to the binding patches
> >> - Adde
How about adding more condition ctx->resv inline to address your concern? As
well as don't wait from same user, shouldn't lead to deadlock.
Otherwise, any other idea?
Original Message
Subject: Re: [PATCH] ttm: wait mem space if user allow while gpu busy
From: Christian König
To
Hi Laurent,
On Thu, Apr 18, 2019 at 09:06:45AM +0300, Laurent Pinchart wrote:
> Hi Jacopo,
>
> On Thu, Apr 04, 2019 at 07:39:05PM +0200, Jacopo Mondi wrote:
> > HI Laurent,
> > if you help me out understanding the bit swapping procedure in VSP
> > I would be more confident in saying I actually r
https://bugs.freedesktop.org/show_bug.cgi?id=110478
--- Comment #3 from cmdr...@gmail.com ---
(In reply to Michel Dänzer from comment #2)
> Yeah, this is a kernel issue. There's only a small amount of VRAM available,
> so the 5760x2160 framebuffer can't fit, and the kernel driver doesn't
> supp
Hi Laurent,
On Thu, Mar 28, 2019 at 09:07:19AM +0200, Laurent Pinchart wrote:
> Add support for the V4L2_PIX_FMT_RGBA444, V4L2_PIX_FMT_RGBX444,
> V4L2_PIX_FMT_ABGR444, V4L2_PIX_FMT_XBGR444, V4L2_PIX_FMT_BGRA444 and
> V4L2_PIX_FMT_BGRX444 formats to the VSP driver.
>
> Signed-off-by: Laurent Pincha
Hi Laurent,
On Thu, Mar 28, 2019 at 09:07:20AM +0200, Laurent Pinchart wrote:
> Add support for the V4L2_PIX_FMT_RGBA555, V4L2_PIX_FMT_RGBX555,
> V4L2_PIX_FMT_ABGR555, V4L2_PIX_FMT_XBGR555, V4L2_PIX_FMT_BGRA555 and
> V4L2_PIX_FMT_BGRX555 formats to the VSP driver.
>
> Signed-off-by: Laurent Pincha
This series is on top of drm-misc because of panfrost and lima drovers
which are missing form amd-staging-drm-next. Once i land it in drm-misc
I will merge and p[ush it into drm-next.
Andrey
On 4/22/19 10:35 PM, Dieter Nützel wrote:
> Hello Andrey,
>
> this series can't apply (brake on #3) on t
On Tue, Apr 23, 2019 at 3:00 PM Liviu Dudau wrote:
>
> On Tue, Apr 23, 2019 at 02:24:11PM +0200, Daniel Vetter wrote:
> > On Tue, Apr 23, 2019 at 12:48 PM Ben Davis wrote:
> > >
> > > Add support for scaling on writeback. To do this add writeback_dest_w
> > > and writeback_dest_h as writeback con
OK, i will merge them into amd-staging drm-next.
Andrey
On 4/23/19 9:14 AM, Kazlauskas, Nicholas wrote:
> Feel free to merge 1+2 since they don't really depend on any other work
> in the series and they were previously reviewed.
>
> Nicholas Kazlauskas
>
> On 4/23/19 8:32 AM, Koenig, Christian wr
Hi Laurent,
On Thu, Mar 28, 2019 at 09:07:21AM +0200, Laurent Pinchart wrote:
> Add support for the DRM_FORMAT_RGBA, DRM_FORMAT_RGBX,
> DRM_FORMAT_ABGR and DRM_FORMAT_XBGR formats to the DU driver.
> Those formats are only available on Gen3.
>
> Signed-off-by: Laurent Pinchart
> -
Hi Laurent,
On Thu, Mar 28, 2019 at 09:07:22AM +0200, Laurent Pinchart wrote:
> Add support for the DRM_FORMAT_RGBA, DRM_FORMAT_RGBX,
> DRM_FORMAT_ABGR, DRM_FORMAT_XBGR, DRM_FORMAT_BGRA and
> DRM_FORMAT_BGRX formats to the DU driver. Those formats are only
> available on Ge
On Tue, Apr 23, 2019 at 12:55:07PM +0100, Emil Velikov wrote:
> On Tue, 23 Apr 2019 at 09:05, Gerd Hoffmann wrote:
> >
> > Hi,
> >
> > > > The DRI3 code extensively uses prime_handle_to_fd and
> > > > prime_fd_to_handle for self-import.
> >
> > The callbacks are not used for self-import.
> >
> U
Hi Laurent,
On Thu, Mar 28, 2019 at 09:07:23AM +0200, Laurent Pinchart wrote:
> Add support for the DRM_FORMAT_RGBA5551, DRM_FORMAT_RGBX5551,
> DRM_FORMAT_ABGR1555, DRM_FORMAT_XBGR1555, DRM_FORMAT_BGRA5551 and
> DRM_FORMAT_BGRX5551 formats to the DU driver. Those formats are only
> available on Ge
Hi Jacopo,
On Tue, Apr 23, 2019 at 03:21:53PM +0200, Jacopo Mondi wrote:
> On Thu, Apr 18, 2019 at 09:06:45AM +0300, Laurent Pinchart wrote:
> > On Thu, Apr 04, 2019 at 07:39:05PM +0200, Jacopo Mondi wrote:
> >> HI Laurent,
> >> if you help me out understanding the bit swapping procedure in VSP
On 4/23/19 8:32 AM, Koenig, Christian wrote:
> Well you at least have to give me time till after the holidays to get
> going again :)
>
> Not sure exactly jet why we need patch number 5.
Probably you missed the mail where I pointed out a bug I found during
testing - I am reattaching the mail an
Reviewed-by: Andrey Grodzovsky
Andrey
On 4/20/19 8:50 AM, Jonathan Neuschäfer wrote:
> Since commit 222b5f044159 ("drm/sched: Refactor ring mirror list
> handling."), drm_sched_hw_job_reset is no longer there, so let's adjust
> the doc comment accordingly.
>
> Signed-off-by: Jonathan Neuschäfer
Hi
Am 07.04.19 um 18:52 schrieb Noralf Trønnes:
> It is generic code and having it in the helper will let other drivers
> benefit from it.
>
> One change was necessary assuming this to be true:
> INTEL_INFO(dev_priv)->num_pipes == dev->mode_config.num_crtc
>
> Suggested-by: Daniel Vetter
> Cc:
On 4/22/19 8:48 AM, Chunming Zhou wrote:
> Hi Andrey,
>
> static void drm_sched_process_job(struct dma_fence *f, struct
> dma_fence_cb *cb)
> {
> ...
> spin_lock_irqsave(&sched->job_list_lock, flags);
> /* remove job from ring_mirror_list */
> list_del_init(&s_job->no
Check that we have a V3D device registered before attempting to
allocate a binner buffer object.
Signed-off-by: Paul Kocialkowski
---
drivers/gpu/drm/vc4/vc4_v3d.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_v3d.c b/drivers/gpu/drm/vc4/vc4_v3d.c
index 7c490106e
The binner BO is not required until the V3D is in use, so avoid
allocating it at probe and do it on the first non-dumb BO allocation.
Keep track of which clients are using the V3D and liberate the buffer
when there is none left, using a kref. Protect the logic with a
mutex to avoid race conditions
Changes since v5:
* Fix more locking mistakes;
* Introduce get/put helpers;
* Grabbed a reference when submitting an exec job with a binner slot.
* Addressed misc comments.
Changes since v4:
* Used a kref on the binner bo instead of firstopen/lastclose;
* Added a mutex to prevent race conditions;
In preparation for wrapping the binner bo allocation helper with
put/get helpers, pass the vc4 dev directly and drop the vc4 prefix.
Signed-off-by: Paul Kocialkowski
---
drivers/gpu/drm/vc4/vc4_v3d.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/
Since the OOM interrupt directly deals with the binner bo, it doesn't
make sense to try and handle it without a binner buffer registered.
Signed-off-by: Paul Kocialkowski
---
drivers/gpu/drm/vc4/vc4_irq.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_irq.c b/driv
Well that's not so easy of hand.
The basic problem here is that when you busy wait at this place you can
easily run into situations where application A busy waits for B while B
busy waits for A -> deadlock.
So what we need here is the deadlock detection logic of the ww_mutex. To
use this we
This patch is to fix deadlock between fence->lock and sched->job_list_lock,
right?
So I suggest to just move list_del_init(&s_job->node) from
drm_sched_process_job to work thread. That will avoid deadlock described in the
link.
Original Message
Subject: Re: [PATCH v5 3/6] drm
Hi Jacopo,
On Tue, Apr 23, 2019 at 03:55:08PM +0200, Jacopo Mondi wrote:
> On Thu, Mar 28, 2019 at 09:07:20AM +0200, Laurent Pinchart wrote:
> > Add support for the V4L2_PIX_FMT_RGBA555, V4L2_PIX_FMT_RGBX555,
> > V4L2_PIX_FMT_ABGR555, V4L2_PIX_FMT_XBGR555, V4L2_PIX_FMT_BGRA555 and
> > V4L2_PIX_FMT
1 - 100 of 202 matches
Mail list logo