On Mon, Sep 24, 2018 at 09:32:11PM +0300, Ville Syrjälä wrote:
> On Mon, Sep 24, 2018 at 02:15:35PM -0400, Nicholas Kazlauskas wrote:
> > Modern display hardware is capable of supporting variable refresh rates
> > and adaptive sync technologies. The properties for querying and
> > controlling these
On Tue, Sep 25, 2018 at 06:28:17PM +0300, Ville Syrjälä wrote:
> On Tue, Sep 25, 2018 at 04:35:59PM +0200, Michel Dänzer wrote:
> > On 2018-09-25 4:04 p.m., Ville Syrjälä wrote:
> > > On Tue, Sep 25, 2018 at 03:28:28PM +0200, Michel Dänzer wrote:
> > >> On 2018-09-24 10:26 p.m., Ville Syrjälä wrote
On Mon, Sep 24, 2018 at 02:15:34PM -0400, Nicholas Kazlauskas wrote:
> These patches are part of a proposed new interface for supporting variable
> refresh rate via DRM properties.
>
> === Changes from v1 ===
>
> For drm:
>
> * The variable_refresh_capable property is now flagged as
> DRM_MODE
On Mon, Sep 24, 2018 at 06:54:02PM +, Satish Kumar Nagireddy wrote:
> This patch adds two new framebuffer flags, so that application can
> communicate alternate interlaced field information to DRM.
>
> This patch also modifies the validation of framebuffer flags in DRM
> core framework. This i
On Mon, Sep 24, 2018 at 02:08:14PM -0700, Radhakrishna Sripada wrote:
> At times 12bpc HDMI cannot be driven due to faulty cables, dongles
> level shifters etc. To workaround them we may need to drive the output
> at a lower bpc. Currently the user space does not have a way to limit
> the bpc. The
Hi,
the last error message seems to come from the following config option:
CONFIG_DRM_FBDEV_OVERALLOC=200
Changing it to the default value fixes the issue:
CONFIG_DRM_FBDEV_OVERALLOC=100
Sergey
On 09/29/2018 08:14 PM, Noralf Trønnes wrote:
Den 28.09.2018 23.01, skrev Stefan Wahren:
Hi,
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/gpu/drm/stm/ltdc.c: In function 'ltdc_plane_atomic_check':
drivers/gpu/drm/stm/ltdc.c:694:13: warning:
variable 'src_y' set but not used [-Wunused-but-set-variable]
u32 src_x, src_y, src_w, src_h;
^
^
drivers/gpu/d
I have no idea where 2880 is coming from, my monitor has resolution 1280
* 1024.
Is this a DRM bug ?
On 09/30/2018 03:29 PM, Noralf Trønnes wrote:
Den 29.09.2018 22.52, skrev Sergey Suloev:
Hi,
the last error message seems to come from the following config option:
CONFIG_DRM_FBDEV_OVERALL
Hi, Noralf,
I have tested you patch with 4.19-rc5.
The issue has changed from oops into the following error message in boot
log:
[ 3.501261] vc4-drm soc:gpu: [drm:drm_fb_helper_fbdev_setup
[drm_kms_helper]] *ERROR* Failed to set fbdev configuration
The console output stops at this mome
On Wed, Sep 26, 2018 at 01:53:12PM +0200, Thomas Zimmermann wrote:
> This patch unifies the naming of DRM functions for reference counting
> of struct drm_device. The resulting code is more aligned with the rest
> of the Linux kernel interfaces.
>
> Signed-off-by: Thomas Zimmermann
Reviewed-by:
From: "Y.C. Chen"
The value of pitches is not correct while calling mode_set.
The issue we found so far on following system:
- Debian8 with XFCE Desktop
- Ubuntu with KDE Desktop
- SUSE15 with KDE Desktop
Signed-off-by: Y.C. Chen
---
drivers/gpu/drm/ast/ast_mode.c | 1 +
1 file changed, 1 inse
Hi,Noralf,
I was hoping Eric would look at it and so I didn't include your email to
CC. From now on as you can be a backup person I will always include you.
Thanks for the fix. Can you also explain which config option(s) causes
this problem ? Because the default config for arm64 works well.
Here is my log
[ 2.868157] [drm:drm_setup_crtcs [drm_kms_helper]] connector 29
enabled? yes
[ 2.868199] [drm:drm_setup_crtcs [drm_kms_helper]] connector 44
enabled? no
[ 2.868234] [drm:drm_setup_crtcs [drm_kms_helper]] connector 50
enabled? yes
[ 2.868271] [drm:drm_setup_crtcs [drm
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/gpu/drm/amd/amdgpu/psp_v3_1.c: In function 'psp_v3_1_ring_stop':
drivers/gpu/drm/amd/amdgpu/psp_v3_1.c:359:19: warning:
variable 'ring' set but not used [-Wunused-but-set-variable]
Signed-off-by: YueHaibing
---
drivers/gpu/drm/amd/amdgpu/p
Hi Noralf,
On Sat, 2018-09-08 at 15:46 +0200, Noralf Trønnes wrote:
> The CMA helper is already using the drm_fb_helper_generic_probe part of
> the generic fbdev emulation. This patch makes full use of the generic
> fbdev emulation by using its drm_client callbacks. This means that
> drm_mode_conf
Add support to async updates of cursors by using the new atomic
interface for that.
Signed-off-by: Enric Balletbo i Serra
---
Hi,
This is a second version of the patch to add async-plane update support
to the Rockchip driver.
The patch was tested on a Samsung Chromebook Plus in two ways.
1. R
On 28-Sep-2018 9:00 PM, "Laurent Pinchart" <
laurent.pinch...@ideasonboard.com> wrote:
>
> Hi Souptick,
>
> On Friday, 28 September 2018 18:05:18 EEST Laurent Pinchart wrote:
> > On Thursday, 27 September 2018 09:34:18 EEST Souptick Joarder wrote:
> > > On Tue, Sep 18, 2018 at 10:05 PM Souptick Joa
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/gpu/drm/amd/amdgpu/psp_v11_0.c: In function 'psp_v11_0_ring_stop':
drivers/gpu/drm/amd/amdgpu/psp_v11_0.c:309:19: warning:
variable 'ring' set but not used [-Wunused-but-set-variable]
Signed-off-by: YueHaibing
---
drivers/gpu/drm/amd/amdgp
Hi, Heiko:
Reviewed-by: zhengyang
The rk3328 uses a dw-hdmi controller with an external hdmi phy from
Innosilicon which uses the generic phy framework for access.
Add the necessary data and the compatible for the rk3328 to the
rockchip dw-hdmi driver.
Signed-off-by: Heiko Stuebner
Tested-by
Why are you resending this? It's because you added some more patches
on the end? Just send those as a new series...
regards,
dan carpenter
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-de
On Wed, Sep 26, 2018 at 10:23:17AM -0600, Jordan Crouse wrote:
> On Wed, Sep 26, 2018 at 01:48:58PM +0200, Thomas Zimmermann wrote:
> > This patch unifies the naming of DRM functions for reference counting
> > of struct drm_gem_object. The resulting code is more aligned with the
> > rest of the Lin
On Wed, Sep 26, 2018 at 01:36:23PM +0200, Thomas Zimmermann wrote:
> This patch unifies the naming of DRM functions for reference counting
> of struct drm_gem_object. The resulting code is more aligned with the
> rest of the Linux kernel interfaces.
Pushed to drm-misc-next.
thanks,
Gerd
__
On Wed, Sep 26, 2018 at 04:59:31PM +0200, Noralf Trønnes wrote:
> This adds an optional function table on GEM objects.
> The main benefit is for drivers that support more than one type of
> memory (shmem,vram,cma) for their buffers depending on the hardware it
> runs on. With the callbacks attached
On Wed, Sep 26, 2018 at 04:59:32PM +0200, Noralf Trønnes wrote:
> This adds a library for shmem backed GEM objects.
>
> Signed-off-by: Noralf Trønnes
> ---
>
> Changes since version 3:
> - Drop cache modes (Thomas Hellstrom)
> - Add a GEM attached vtable
>
> Documentation/gpu/drm-kms-helpers.r
On Wed, Sep 26, 2018 at 04:59:29PM +0200, Noralf Trønnes wrote:
> This patchset adds a library for shmem backed GEM objects and makes use
> of it in tinydrm.
>
> Thomas gave me some feedback that made me realise that the cachemodes
> pattern I had picked up from some other drivers didn't apply to
On Wed, Sep 26, 2018 at 09:41:51PM +0200, Hans de Goede wrote:
> Hi All,
>
> This series converts the vboxvideo driver to the modesetting API, once this
> is merged I will submit a patch to move the driver out of staging and into
> drivers/gpu/drm.
>
> This series consists of 3 parts:
>
> 1) Mor
On Wed, Sep 26, 2018 at 09:42:02PM +0200, Hans de Goede wrote:
> Atomic modesetting does not use the traditional dpms call backs, instead
> we should check crtc_state->active.
>
> Signed-off-by: Hans de Goede
Are you sure this does what you want it to do? Atomic helpers fully shut
down the scree
On Wed, Sep 26, 2018 at 10:41:50PM +0200, Stefan Agner wrote:
> From: Satendra Singh Thakur
>
> Use the drm_display_mode_to_videomode function to calculate front/
> back porches and sync length.
>
> Cc: Madhur Verma
> Cc: Hemanshu Srivastava
> Signed-off-by: Satendra Singh Thakur
> Signed-off
Hi Dave,
Adding out-bridge support for the use of LVDS bridge device
to MIPI-DSI driver, Samsung 16x16 tiled format support to
scalder and gsc drivers and configurable plane alpha and pixel
blend mode supports to mixer driver including one cleanup for
removing exynos specific suspen
On Thu, Sep 27, 2018 at 05:30:07PM -0700, Deepak Rawat wrote:
> From: Rob Clark
>
> Add an atomic helper to implement dirtyfb support. This is needed to
> support DSI command-mode panels with x11 userspace (ie. when we can't
> rely on pageflips to trigger a flush to the panel).
>
> v2: Modified
On Thu, Sep 27, 2018 at 05:30:06PM -0700, Deepak Rawat wrote:
> Selftest for drm damage helper iterator functions.
>
> Cc: ville.syrj...@linux.intel.com
> Cc: Daniel Vetter
> Cc: Pekka Paalanen
> Signed-off-by: Deepak Rawat
> ---
> drivers/gpu/drm/selftests/Makefile| 3 +-
> .../
On Fri, Sep 28, 2018 at 05:41:26PM +0300, Eugeniy Paltsev wrote:
> UDL doesn't support vblank functionality so we don't need to
> initialize vblank here (we are able to send page flip
> completion events even without vblank initialization)
>
> Moreover current drm_vblank_init call with num_crtcs >
On Fri, Sep 28, 2018 at 05:50:44PM -0500, Rob Herring wrote:
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> For drm_modes.c, the full node path is already printed out, so printing
> just the node name a 2nd ti
On Sat, Sep 29, 2018 at 07:12:00PM +0200, Noralf Trønnes wrote:
> Sergey Suloev reported a crash happening in drm_client_dev_hotplug()
> when fbdev had failed to register.
>
> [9.124598] vc4_hdmi 3f902000.hdmi: ASoC: Failed to create component
> debugfs directory
> [9.147667] vc4_hdmi 3f9
On Mon, Oct 01, 2018 at 01:26:04PM +0800, Y.C. Chen wrote:
> From: "Y.C. Chen"
>
> The value of pitches is not correct while calling mode_set.
> The issue we found so far on following system:
> - Debian8 with XFCE Desktop
> - Ubuntu with KDE Desktop
> - SUSE15 with KDE Desktop
>
> Signed-off-by:
https://bugs.freedesktop.org/show_bug.cgi?id=108086
--- Comment #4 from jeckfer...@gmail.com ---
After the cleaning of .cache, it's going fine. Will report back after a week or
two.
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=108086
--- Comment #5 from Mike Lothian ---
So I think your distro uses the same build time for all their Mesa builds which
means the cache is trying to reuse Mesa 18.1 shaders on Mesa 18.2
There's a fix to use the build-id on the mailing list, so hop
https://bugzilla.kernel.org/show_bug.cgi?id=201295
Bug ID: 201295
Summary: amdgpu :09:00.0: Direct firmware load for
amdgpu/polaris11_mc.bin failed with error -2
Product: Drivers
Version: 2.5
Kernel Version: 4.17.11, 4.17.12,
https://bugzilla.kernel.org/show_bug.cgi?id=201295
--- Comment #1 from Dennis Wagelaar (dwagel...@gmail.com) ---
Created attachment 278863
--> https://bugzilla.kernel.org/attachment.cgi?id=278863&action=edit
dmesg output for kernel-4.16.16-200.fc27.x86_64
--
You are receiving this mail because
https://bugzilla.kernel.org/show_bug.cgi?id=201295
--- Comment #2 from Dennis Wagelaar (dwagel...@gmail.com) ---
Suspicious section from kernel 4.18.16 dmesg output:
[2.801753] amdgpu :09:00.0: Direct firmware load for
amdgpu/polaris11_mc.bin failed with error -2
[2.801754] mc: Failed
https://bugs.freedesktop.org/show_bug.cgi?id=108095
--- Comment #4 from Paul Menzel ---
Created attachment 141818
--> https://bugs.freedesktop.org/attachment.cgi?id=141818&action=edit
Output of `glxinfo`
Please find the output of `glxinfo` attached. Here is an excerpt.
```
Extended renderer i
Hi,
On 01-10-18 09:51, Daniel Vetter wrote:
On Wed, Sep 26, 2018 at 09:41:51PM +0200, Hans de Goede wrote:
Hi All,
This series converts the vboxvideo driver to the modesetting API, once this
is merged I will submit a patch to move the driver out of staging and into
drivers/gpu/drm.
This serie
Hi,
On 01-10-18 09:25, Dan Carpenter wrote:
Why are you resending this? It's because you added some more patches
on the end? Just send those as a new series...
I accidentally numbered the cover-letter of the original series
01/15 instea dof 00/15 this confused Greg, so he asked for a resend.
https://bugs.freedesktop.org/show_bug.cgi?id=108095
--- Comment #5 from Michel Dänzer ---
Does restarting xfwm4 with any of these arguments make a difference?
xfwm4 --replace --vblank=off
xfwm4 --replace --vblank=glx
xfwm4 --replace --vblank=xpresent
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=201295
--- Comment #3 from Michel Dänzer (mic...@daenzer.net) ---
Error -2 is -ENOENT, "No such file or directory", so the
amdgpu/polaris11_mc.bin file is missing where the amdgpu module is loaded from
(could be the initrd).
This is a configuration erro
https://bugzilla.kernel.org/show_bug.cgi?id=201295
Dennis Wagelaar (dwagel...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Hello Giulio Benetti,
The patch 490cda5a3c82: "drm/sun4i: Handle DRM_BUS_FLAG_PIXDATA_*EDGE
checking if panel is used." from Jul 18, 2018, leads to the following
static checker warning:
drivers/gpu/drm/sun4i/sun4i_tcon.c:558 sun4i_tcon0_mode_set_rgb()
warn: 'tcon->panel' isn't an
On Fri, Sep 21, 2018 at 04:46:47PM +0300, Ville Syrjälä wrote:
> On Fri, Sep 21, 2018 at 01:34:00AM -0700, Manasi Navare wrote:
> > On Wed, Sep 19, 2018 at 01:57:00PM +0300, Ville Syrjälä wrote:
> > > On Tue, Sep 18, 2018 at 02:10:17PM -0700, Manasi Navare wrote:
> > > > On Tue, Sep 18, 2018 at 10:
Hi,
On 01-10-18 09:53, Daniel Vetter wrote:
On Wed, Sep 26, 2018 at 09:42:02PM +0200, Hans de Goede wrote:
Atomic modesetting does not use the traditional dpms call backs, instead
we should check crtc_state->active.
Signed-off-by: Hans de Goede
Are you sure this does what you want it to do?
Hello Jeykumar Sankaran,
The patch 25fdd5933e4c: "drm/msm: Add SDM845 DPU support" from Jun
27, 2018, leads to the following static checker warning:
drivers/gpu/drm/msm/msm_drv.c:562 msm_drm_init()
warn: 'priv->disp_thread[i].thread' isn't an ERR_PTR
drivers/gpu/drm/msm/msm_drv.c
On Mon, Oct 01, 2018 at 12:38:56PM +0300, Dan Carpenter wrote:
> Hello Jeykumar Sankaran,
>
> The patch 25fdd5933e4c: "drm/msm: Add SDM845 DPU support" from Jun
> 27, 2018, leads to the following static checker warning:
>
> drivers/gpu/drm/msm/msm_drv.c:562 msm_drm_init()
> warn: 'pri
https://bugs.freedesktop.org/show_bug.cgi?id=108098
--- Comment #1 from Michel Dänzer ---
Can you try a newer kernel? Support for Ryzen APUs was known to be a bit rough
around the edges until recently.
--
You are receiving this mail because:
You are the assignee for the bug.
On Tue, Sep 18, 2018 at 12:04:35PM -0700, Manasi Navare wrote:
> > > [...]
> > > diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.c
> > > b/drivers/gpu/drm/i915/intel_runtime_pm.c
> > > index 480dadb1047b..146e2d6cf954 100644
> > > --- a/drivers/gpu/drm/i915/intel_runtime_pm.c
> > > +++ b/driver
Trying to put the virtio-gpu driver's ttm resource handling
into shape. Also improve the resource id handling.
Gerd Hoffmann (8):
drm/virtio: use virtio_gpu_object->hw_res_handle in
virtio_gpufb_create()
drm/virtio: use virtio_gpu_object->hw_res_handle in
virtio_gpu_mode_dumb_create()
Drop pointless resid variable in virtio_gpufb_create(), just use
the hw_res_handle field in virtio_gpu_object directly.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_fb.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_
Initialize objects with TTM_PL_FLAG_SYSTEM placement, move them over to
TTM_PL_FLAG_TT after they are created (i.e. registered in the host).
That way the ttm backend will handle attach/detach just fine and we
don't need the extra virtio_gpu_object_attach() calls.
TODO: check ioctl fence.
Signed-o
Drop pointless res_id variable in virtio_gpu_resource_create_ioctl(),
just use the hw_res_handle field in virtio_gpu_object directly.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 24
1 file changed, 8 insertions(+), 16 deletions(-)
diff --gi
Remove the virtio_gpu_object_{attach,detach} calls from move_notify()
callback. Add them to the ttm_tt_{populate,unpopulate} callbacks, which
is the correct place to handle this.
The new ttm_tt_{populate,unpopulate} callbacks call the
ttm_pool_populate()/unpopulate() functions (which are the defa
Drop pointless resid variable in virtio_gpu_mode_dumb_create(), just use
the hw_res_handle field in virtio_gpu_object directly.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_gem.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/virti
We pass the obj anyway, so obj->hw_res_handle can be used instead.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 1 -
drivers/gpu/drm/virtio/virtgpu_fb.c| 2 +-
drivers/gpu/drm/virtio/virtgpu_gem.c | 2 +-
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 4 ++--
drivers
Move virtio_gpu_resource_id_{get,put} to virtgpu_object.c and make them
static. Allocate and free the id on creation and destroy, drop all
other calls. That way objects have a valid handle for the whole
lifetime of the object.
Also fixes ids leaking. Worst offender are dumb buffers, and I think
Track whenever the virtio_gpu_object is already created (i.e. host knows
about it) in a new variable. Add checks to virtio_gpu_object_attach()
to do nothing on objects not created yet.
Make virtio_gpu_ttm_bo_destroy() use the new variable too, instead of
expecting hw_res_handle indicating the obj
+ dri-devel
This patch may also break other ARM DRM drivers. I cced dri-devel so
that they could manage this.
And below relevant link for ARM DRM maintainers,
https://www.spinics.net/lists/arm-kernel/msg676098.html
Thanks,
Inki Dae
2018년 9월 29일 (토) 오전 1:19, Marek Szyprowski 님이 작성:
>
> Hi Robin
Hi Daniel,
On Monday, 1 October 2018 09:52:20 EEST Daniel Vetter wrote:
> On Fri, Sep 28, 2018 at 06:30:35PM +0300, Laurent Pinchart wrote:
> > On Friday, 28 September 2018 18:05:18 EEST Laurent Pinchart wrote:
> > > On Thursday, 27 September 2018 09:34:18 EEST Souptick Joarder wrote:
> > > > On T
Den 01.10.2018 09.56, skrev Alexey Brodkin:
Hi Noralf,
On Fri, 2018-09-28 at 12:42 +0200, Noralf Trønnes wrote:
Den 28.09.2018 09.34, skrev Alexey Brodkin:
Hi Noralf,
On Sat, 2018-09-08 at 15:46 +0200, Noralf Trønnes wrote:
The CMA helper is already using the drm_fb_helper_generic_probe pa
https://bugs.freedesktop.org/show_bug.cgi?id=100891
--- Comment #9 from Luke A. Guest ---
I've also been getting these messages on my card:
[435103.682225] amdgpu: [powerplay]
last message was failed ret is 0
[435104.057921] amdgpu: [powerplay]
failed to send
Gerd Hoffmann (2):
drm: virtual connectors can have edid too
drm/bochs: add edid support.
drivers/gpu/drm/bochs/bochs.h | 1 +
drivers/gpu/drm/bochs/bochs_hw.c | 38 ++
drivers/gpu/drm/bochs/bochs_kms.c | 16 +---
drivers/gpu/drm/drm_con
Recent qemu (latest master branch, upcoming 3.1 release) got support
for EDID data. This patch adds guest driver support.
EDID support in qemu is not (yet) enabled by default, so please use
'qemu -device VGA,edid=on' for testing.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/bochs/bochs.h
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/drm_connector.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
index 6011d769d5..95cbbf7ee5 100644
--- a/drivers/gpu/drm/drm_connector.c
+++ b/drivers/gpu/drm/
Hi Noralf,
On 17/09/2018 09:53, Neil Armstrong wrote:
> Hi Noralf, Daniel,
>
> On 14/09/2018 18:33, Noralf Trønnes wrote:
>>
>> Den 14.09.2018 10.23, skrev Neil Armstrong:
>>> Hi Daniel,
>>>
>>> On 13/09/2018 16:55, Daniel Vetter wrote:
On Thu, Sep 13, 2018 at 04:26:53PM +0200, Neil Armstron
This series is an effort to have the msm drm driver start using the DRM gpu
scheduler for its general job scheduling needs. Immediate benefits to the msm
drm driver include async fencing and improved driver performance.
Testing is still under progress, but general GPU submissions, preemption,
time
When the scheduler comes into picture, the msm_gpu_submit() will be
called from the scheduler worker thread. So save the necessary information
into msm job structure for use at the actual GPU submission time. This
also simplifies the msm_gpu_submit() API.
Signed-off-by: Sharat Masetty
---
driver
Track the GPU fences created at submit time with idr instead of the ring
the sequence number. This helps with easily changing the underlying
fence to something we don't truly own, like the scheduler fence.
Also move the GPU fence allocation to msm_gpu_submit() and have
the function return the fenc
The submit path in msm_gpu_submit() takes a reference to the buffer
object and the iova. This should not be needed with a little bit of
code rearrangement. We still keep the same semantic of a valid GPU
submission holding a reference to the base object and the iova until
retirement.
Signed-off-by
We are going to soon deal with lot more fences, so change the generic
name 'fence' to hw_fence to denote association with an actual hardware
submission.
Signed-off-by: Sharat Masetty
---
drivers/gpu/drm/msm/msm_gem.h| 2 +-
drivers/gpu/drm/msm/msm_gem_submit.c | 17 -
dr
The scheduler needs an instance name mostly for debug purposes. Save the
name in the ringbuffer instead of a stack variable, so that the name
can be shared with the scheduler.
Signed-off-by: Sharat Masetty
---
drivers/gpu/drm/msm/msm_ringbuffer.c | 5 ++---
drivers/gpu/drm/msm/msm_ringbuffer.h |
This patch changes to kzalloc and avoids setting individual submit
struct fields to zero manually.
Signed-off-by: Sharat Masetty
---
drivers/gpu/drm/msm/msm_gem_submit.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/msm/msm_gem_submit.c
b/drivers/gpu/
This patch fixes a trivial leak when trying to create a submitqueue.
Signed-off-by: Sharat Masetty
Reviewed-by: Jordan Crouse
---
drivers/gpu/drm/msm/msm_submitqueue.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/msm_submitqueue.c
b/drivers/gpu/drm
In cases where the scheduler instance is used a base object of another
vendor driver object, it's not clear if the driver can call sched cleanup on
the fail path. Set the sched->thread to NULL, so that the vendor driver
can safely call drm_sched_fini() during cleanup.
Signed-off-by: Sharat Masetty
This patch hooks up the DRM gpu scheduler to the msm DRM driver. The
most noticeable changes to the driver are as follows. The submit path is
split into two parts, in the user context the submit(job) is created and
added to one of the entity's scheduler run queue. The scheduler then
tries to drain
The base scheduler patch has barebones timeout implementation, it does
not account for issues like starvation on lower priority rings. This
patch enables more accurate measurement on time spent on each
ringbuffer, thereby helping us with better timeout detection mechanism.
Signed-off-by: Sharat Ma
Add an optional backend function op which will let the scheduler clients
know when the timeout work got scheduled for a job. This will help
drivers with multiple schedulers(one per ring) measure time spent on the
ring accurately, eventually helping with better timeout detection.
Signed-off-by: Sha
With the introduction of the scheduler, most of the code related to
timeout detection, recovery and submission retirement are no longer
needed in the msm driver. This patch simply removes the no longer used
code.
Signed-off-by: Sharat Masetty
---
drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 3 -
dr
From: Matteo Croce
add jiffies_delta_to_msecs() helper func to calculate the delta between
two times and eventually 0 if negative.
Suggested-by: Eric Dumazet
Signed-off-by: Matteo Croce
Reviewed-by: Eric Dumazet
Acked-by: Simon Horman
Signed-off-by: Pablo Neira Ayuso
---
include/linux/jiff
With the regular means of adding the dsi-component in probe it creates
a race condition with the panel probing, as the panel device only gets
created after the dsi-bus got created.
When the panel-driver is build as a module it currently fails hard as the
panel cannot be probed directly:
dw_mipi_d
From: Nickey Yang
Add the ROCKCHIP DSI controller driver that uses the Synopsys DesignWare
MIPI DSI host controller bridge and remove the old separate one.
changes:
v2:
add err_pllref, remove unnecessary encoder.enable & disable
correct spelling mistakes
v3:
call dw_mipi_dsi_unbind() i
From: Nickey Yang
Allow to also drive a slave dw-mipi-dsi controller in a dual-dsi
setup. This will require additional implementation-specific
code to look up the slave instance and do specific setup.
Also will probably need code in the specific crtcs as dual-dsi
does not equal two separate dsi o
The Rockchip DSI driver was separate till now, not using the common
bridge driver that was introduced a bit later. So this series migrates
over to use that common bridge driver and then also adds support for
dual-dsi to both the bridge and Rockchip glue code.
The bridge-migration itself is based o
__dw_mipi_dsi_probe() does all the grabbing of resources and does it using
devm-helpers. So this is happening on each try of master bringup possibly
slowing down things a lot.
Drivers using the component framework may instead want to call
dw_mipi_dsi_probe separately in their probe function to set
Right now the host is only unregistered when the driver is used via the
bridge api and not via the component api, leading to the host staying
registered in cases like probe deferral.
So move the host unregister to the general remove function, so that it
gets cleaned up in all cases.
Signed-off-by
Add the Rockchip-sepcific dual-dsi setup and hook it into the VOP as well.
As described in the general dual-dsi devicetree binding, the panel should
define two input ports and point each of them to one of the used dsi-
controllers, as well as declare one of them as clock-master.
This is used to det
From: Nickey Yang
This patch update describe panel/port links, including
unit addresses in documentation of device tree bindings
for the rockchip DSI controller based on the Synopsys
DesignWare MIPI DSI host controller.
Signed-off-by: Nickey Yang
Reviewed-by: Brian Norris
Reviewed-by: Rob Herr
Den 01.10.2018 13.56, skrev Laurent Pinchart:
Hi Daniel,
On Monday, 1 October 2018 09:52:20 EEST Daniel Vetter wrote:
On Fri, Sep 28, 2018 at 06:30:35PM +0300, Laurent Pinchart wrote:
On Friday, 28 September 2018 18:05:18 EEST Laurent Pinchart wrote:
On Thursday, 27 September 2018 09:34:18 E
Hi Andrzej
Am Freitag, 21. September 2018, 08:11:16 CEST schrieb Andrzej Hajda:
> On 20.09.2018 13:20, Heiko Stuebner wrote:
> > Hi Andrzej,
> >
> > Am Montag, 27. August 2018, 13:34:07 CEST schrieb Andrzej Hajda:
> >> On 21.08.2018 16:05, Heiko Stuebner wrote:
> >>> Add the Rockchip-sepcific dual
Hi Christian,
I took the repository Dieter suggested and gave it a spin. I am not
sure, if I got the API right.
In userspace I create a bo and get a fd.
bo = gbm_bo_create(gbm, w, h, GBM_FORMAT_ARGB, GBM_BO_USE_LINEAR);
dmabuf_fd = gbm_bo_get_fd(bo);
Then I pass the fd to the grabber driver.
https://bugzilla.kernel.org/show_bug.cgi?id=199139
juliolok...@gmail.com changed:
What|Removed |Added
CC||juliolok...@gmail.com
--- Comment
On Mon, Oct 01, 2018 at 08:59:41AM +0200, Daniel Vetter wrote:
> On Mon, Sep 24, 2018 at 08:13:08PM +0300, Ville Syrjälä wrote:
> > On Mon, Sep 24, 2018 at 06:10:14PM +0200, Daniel Vetter wrote:
> > > On Thu, Sep 20, 2018 at 09:51:43PM +0300, Ville Syrjala wrote:
> > > > From: Ville Syrjälä
> > >
From: Jamie Fox
Mali-DP650 supports warming up the SMMU translations, by sending
requsts to the SMMU before a buffer is read.
There are two modes supported:
- PARTIAL: could be enabled when the buffer is composed of 4K or 64K
pages, the display hardware will send a configurable number of
re
Hi Dave,
Please pull this small drm/tilcdc suspend/resume code update for Linux v4.19.
Best regards and thanks,
Jyri
The following changes since commit 17b57b1883c1285f3d0dc2266e8f79286a7bef38:
Linux 4.19-rc6 (2018-09-30 07:15:35 -0700)
are available in the git repository at:
https://githu
On Mon, Sep 24, 2018 at 02:08:15PM -0700, Radhakrishna Sripada wrote:
> Use the newly added "max bpc" connector property to limit pipe bpp.
>
> V3: Use drm_connector_state to access the "max bpc" property
> V4: Initialize the drm property, add suuport to DP(Ville)
> V5: Use the property in the con
1 - 100 of 166 matches
Mail list logo
