On Tue, Feb 19, 2019 at 10:44 PM Frank Rowand wrote:
>
> On 2/19/19 7:39 PM, Brendan Higgins wrote:
> > On Mon, Feb 18, 2019 at 11:52 AM Frank Rowand
> > wrote:
> >>
> >> On 2/14/19 1:37 PM, Brendan Higgins wrote:
> >>> Add support for aborting/bailing out of test cases. Needed for
> >>>
https://bugs.freedesktop.org/show_bug.cgi?id=109794
--- Comment #1 from Hal Gentz ---
s/an investigation//
s/in an `eglInitialize` call/when we call `eglInitialize`/
s/happens once./initializes stuff once./
s/we all/we call/
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109794
Bug ID: 109794
Summary: LLVM not properly shutdown in `si_pipe.c`?
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
The pages backing the GEM objects are kept pinned in place as
long as they are alive, so they must not be allocated from the
MOVABLE zone. Blocking page migration for too long will cause
the VM subsystem headaches and will outright break CMA, as a
few pinned pages in CMA will lead to failure to
Hi Daniel, hi Dave,
sorry for being really late. We don't have something major to destage,
as per-process address spaces and softpin are still baking. So this
time around it's only small fixes and a change to not restrict etnaviv
to certain architectures. This has seen some coverage from the
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: 9bf083e6426b8df943f0da4a7ef8d8f407a26e9f
commit: 58560ce0c438137ef4dca63fabf58a16dbf35c19 [451/607] drm/amd/powerplay:
init microcode for smu11
reproduce:
# apt-get install sparse
git checkout
add memset dispatch test for gfx9
Change-Id: If607fbd9c6e49ca830a662adc24fe6b1e2a25bfb
Signed-off-by: Flora Cui
Tested-by: Rui Teng
---
tests/amdgpu/basic_tests.c | 215 -
1 file changed, 213 insertions(+), 2 deletions(-)
diff --git
add memcpy dispatch test for gfx9
Change-Id: If433434c5378f3b318209d4e28c19d7ce9cff1a2
Signed-off-by: Flora Cui
Tested-by: Rui Teng
---
tests/amdgpu/basic_tests.c | 129 +
1 file changed, 129 insertions(+)
diff --git a/tests/amdgpu/basic_tests.c
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: 9bf083e6426b8df943f0da4a7ef8d8f407a26e9f
commit: bf05726f078c37252b2052a74086e3b0eaf634de [473/607] drm/amd/powerplay:
implement notify_memory_pool_location function for smu11
config: mips-allmodconfig (attached as
https://bugzilla.kernel.org/show_bug.cgi?id=202445
--- Comment #19 from Clément Guérin (li...@protonmail.com) ---
I just built drm-fixes-5.0 including
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-5.0=d63716658ac16c515d1223a9fbf5edbf76b1b333
and this issue remains.
--
You are
I merged some fixes into drm-fixes, pushed it out, then saw tip
breaking, but I'm needed elsewhere, so if anyone can fix tip up or
tell me why I got a super messy commit, I'll owe you.
Thanks,
Dave.
___
dri-devel mailing list
On Fri, Feb 22, 2019 at 12:53 PM Thiago Jung Bauermann
wrote:
>
>
> Frank Rowand writes:
>
> > On 2/19/19 10:34 PM, Brendan Higgins wrote:
> >> On Mon, Feb 18, 2019 at 12:02 PM Frank Rowand
> >> wrote:
> >>
> >>> I have not read through the patches in any detail. I have read some of
> >>>
On Tue, Feb 19, 2019 at 10:46 PM Frank Rowand wrote:
>
> On 2/19/19 10:34 PM, Brendan Higgins wrote:
> > On Mon, Feb 18, 2019 at 12:02 PM Frank Rowand
> > wrote:
> >
> >> I have not read through the patches in any detail. I have read some of
> >> the code to try to understand the patches to
On Wed, Feb 20, 2019 at 12:45 PM Frank Rowand wrote:
>
> On 2/18/19 2:25 PM, Frank Rowand wrote:
> > On 2/15/19 2:56 AM, Brendan Higgins wrote:
> >> On Thu, Feb 14, 2019 at 6:05 PM Frank Rowand
> >> wrote:
> >>>
> >>> On 2/14/19 4:56 PM, Brendan Higgins wrote:
> On Thu, Feb 14, 2019 at
https://bugs.freedesktop.org/show_bug.cgi?id=109783
Andres changed:
What|Removed |Added
Version|unspecified |18.2
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=109793
Bug ID: 109793
Summary: I420/IYUV is not advertised in vaQueryImageFormats()
Product: Mesa
Version: 18.2
Hardware: Other
OS: All
Status: NEW
Severity:
Applied. thanks!
On Tue, Feb 26, 2019 at 12:36 AM YueHaibing wrote:
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/gpu/drm/amd/amdgpu/si_dpm.c: In function 'si_program_response_times':
> drivers/gpu/drm/amd/amdgpu/si_dpm.c:4101:29: warning:
> variable 'backbias_response_time'
Applied. thanks!
On Wed, Feb 20, 2019 at 3:05 AM YueHaibing wrote:
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c: In function
> 'update_gpuvm_pte':
> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c:840:20: warning:
> variable 'bo' set
Applied. Thanks!
On Tue, Feb 19, 2019 at 3:22 AM YueHaibing wrote:
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/gpu/drm/ttm/ttm_execbuf_util.c: In function
> 'ttm_eu_fence_buffer_objects':
> drivers/gpu/drm/ttm/ttm_execbuf_util.c:191:24: warning:
> variable 'bdev' set but
Applied. Sorry for the delay.
Alex
On Fri, Feb 22, 2019 at 10:36 AM Nathan Chancellor
wrote:
>
> On Mon, Dec 10, 2018 at 04:42:01PM -0700, Nathan Chancellor wrote:
> > Clang warns when an expression that equals zero is used as a null
> > pointer constant (in lieu of NULL):
> >
> >
https://bugs.freedesktop.org/show_bug.cgi?id=109265
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Generated using make headers_install.
This brings in the in/out fence support for explicit
synchronization.
v2: don't use experimental kernel branch
Signed-off-by: Gurchetan Singh
---
include/drm/virtgpu_drm.h | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git
Hi Daniel,
On Wed, 2019-02-27 at 06:13:45 -0800, Daniel Vetter wrote:
> On Tue, Feb 26, 2019 at 11:20 PM Hyun Kwon wrote:
> >
> > Hi Daniel,
> >
> > Thanks for the comment.
> >
> > On Tue, 2019-02-26 at 04:06:13 -0800, Daniel Vetter wrote:
> > > On Tue, Feb 26, 2019 at 12:53 PM Greg
Generated using make headers_install.
This brings in the in/out fence support for explicit
synchronization.
Signed-off-by: Gurchetan Singh
---
include/drm/virtgpu_drm.h | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/include/drm/virtgpu_drm.h
On Mon, Feb 18, 2019 at 2:56 PM Frank Rowand wrote:
>
> On 2/12/19 5:44 PM, Brendan Higgins wrote:
> > On Wed, Nov 28, 2018 at 12:56 PM Rob Herring wrote:
> >>
> >> On Wed, Nov 28, 2018 at 1:38 PM Brendan Higgins
> >> wrote:
> >>> ---
> >>> drivers/of/Kconfig|1 +
> >>>
On Wed, Feb 27, 2019 at 3:22 PM Laura Abbott wrote:
> On 2/25/19 6:36 AM, Andrew F. Davis wrote:
> > +
> > +dev_t dma_heap_devt;
> > +struct class *dma_heap_class;
>
> Can we make sure this gets reviewed by Greg sooner rather than
> later when we drop the RFC? I think the use of this here
> is
https://bugs.freedesktop.org/show_bug.cgi?id=109695
--- Comment #7 from Marek Olšák ---
(In reply to Daniel P. Berrange from comment #4)
> I'm curious what motivated this change to start with ? Even if QEMU was not
> enforcing seccomp filters, I think I'd consider it a bug for mesa to be
>
On 2/26/19 1:44 PM, Eric Biggers wrote:
From: Eric Biggers
If drm_gem_handle_create() fails in vgem_gem_create(), then the
drm_vgem_gem_object is freed twice: once when the reference is dropped
by drm_gem_object_put_unlocked(), and again by __vgem_gem_destroy().
This was hit by syzkaller
On 2/25/19 6:36 AM, Andrew F. Davis wrote:
This framework allows a unified userspace interface for dma-buf
exporters, allowing userland to allocate specific types of memory
for use in dma-buf sharing.
Each heap is given its own device node, which a user can allocate
a dma-buf fd from using the
https://bugs.freedesktop.org/show_bug.cgi?id=109695
--- Comment #6 from Marc-Andre Lureau ---
Sent a quick RFC for an env variable workaround on the ML "[PATCH] RFC:
Workaround for pthread_setaffinity_np() seccomp filtering".
--
You are receiving this mail because:
You are the assignee for the
On 02/26, Eric Biggers wrote:
> From: Eric Biggers
>
> If drm_gem_handle_create() fails in vkms_gem_create(), then the
> vkms_gem_object is freed twice: once when the reference is dropped by
> drm_gem_object_put_unlocked(), and again by the extra calls to
> drm_gem_object_release() and kfree().
https://bugs.freedesktop.org/show_bug.cgi?id=109265
--- Comment #5 from Timothy Arceri ---
You were right it was a bad bisect due to that patch breaking MSAA also. I
found the real issue, fix sent to the list.
https://patchwork.freedesktop.org/patch/288934/
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=109749
--- Comment #2 from bmil...@gmail.com ---
Fix was pushed to 5.0, should we mark this as resolved for now?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=108359
Jeremy Newton changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
Quoting Chris Wilson (2019-02-27 10:17:15)
> Quoting Daniel Vetter (2017-08-07 10:28:58)
> > On Fri, Aug 04, 2017 at 09:23:28AM +0100, Chris Wilson wrote:
> > > After an event is sent, we try to copy it into the user buffer of the
> > > first waiter in drm_read() and if the user buffer doesn't
On Wed, Feb 27, 2019 at 8:38 AM Andrew F. Davis wrote:
>
> On 2/26/19 5:40 PM, John Stultz wrote:
> > On Tue, Feb 26, 2019 at 11:21 AM John Stultz wrote:
> > I've updated the patches here:
> > kernel:
> > https://git.linaro.org/people/john.stultz/android-dev.git/log/?h=dev/dma-buf-heap
> >
Changes since first version:
- Moved reviewed patches to front:
- drm/bridge: sii902x: add input_bus_flags
- drm/bridge: sii902x: Set output mode to HDMI or DVI according to EDID
- drm/bridge: sii902x: pixel clock unit is 10kHz instead of 1kHz
- Added a new fix:
- drm/bridge: sii902x:
From: Tomi Valkeinen
The driver always sets InputBusFmt:EDGE to 0 (falling edge).
Add drm_bridge_timings's input_bus_flags to reflect that the bridge
samples on falling edges.
Signed-off-by: Tomi Valkeinen
Signed-off-by: Jyri Sarha
Reviewed-by: Andrzej Hajda
---
Set output mode to HDMI or DVI according to EDID HDMI signature.
Signed-off-by: Jyri Sarha
Reviewed-by: Andrzej Hajda
---
drivers/gpu/drm/bridge/sii902x.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/bridge/sii902x.c b/drivers/gpu/drm/bridge/sii902x.c
index
Implement HDMI audio support by using ASoC HDMI codec. The commit
implements the necessary callbacks and configuration for the HDMI
codec and registers a virtual platform device for the codec to attach.
Signed-off-by: Jyri Sarha
---
.../bindings/display/bridge/sii902x.txt | 36 +-
The pixel clock unit in the first two registers (0x00 and 0x01) of
sii9022 is 10kHz, not 1kHz as in struct drm_display_mode. Division by
10 fixes the issue.
Signed-off-by: Jyri Sarha
Reviewed-by: Andrzej Hajda
---
drivers/gpu/drm/bridge/sii902x.c | 5 +++--
1 file changed, 3 insertions(+), 2
"drm/bridge/sii902x: Fix EDID readback"-commit added a dependency to
I2C_MUX, but not indicate it in the Kconfig entry. Fix it by selecting
I2C_MUX for DRM_SII902X config option.
Fixes: 88664675239 ("drm/bridge/sii902x: Fix EDID readback")
Signed-off-by: Jyri Sarha
---
https://bugs.freedesktop.org/show_bug.cgi?id=109762
--- Comment #1 from Amadeusz ---
So as I half remembered it didn't happen in the past.
I did some internet searches and there are few similar bugs on this bugzilla:
https://bugzilla.freedesktop.org/show_bug.cgi?id=109461
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/video/fbdev/xen-fbfront.c: In function ‘xenfb_backend_changed’:
drivers/video/fbdev/xen-fbfront.c:678:6: warning: this statement may fall
On Wed, Feb 27, 2019 at 03:23:01PM -0500, Adam Jackson wrote:
> On Wed, 2019-02-27 at 19:14 +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Some monitors apparently forget to mark any mode as preferred in the
> > EDID. In this particular case we have a very generic looking ID
> >
Hi Qiang.
Two general comments:
- We are trying to avoid drmP.h in new drivers, please drop
- The use of idr is being replaced with XArray, see patch-set
posted by Matthew Wilcox.
Try to use XArray so we do not introduce a new user.
This was from a very quick looks at the driver.
In general
On Wed, 2019-02-27 at 19:14 +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Some monitors apparently forget to mark any mode as preferred in the
> EDID. In this particular case we have a very generic looking ID
> "PNP Model 0 Serial Number 4" / "LVDS 800x600" so a specific quirk
> doesn't
Hi Alexandre.
Nice patch, good to clean out unused code.
On Mon, Feb 25, 2019 at 10:25:33PM +0100, Alexandre Belloni wrote:
> Make the driver OF only as since AVR32 has been removed from the kernel,
> there are only OF enabled platform using it.
>
> Signed-off-by: Alexandre Belloni
Reviewed-by:
Hi Masahiro.
On Thu, Jan 31, 2019 at 12:56:39PM +0900, Masahiro Yamada wrote:
> Currently, the Kbuild core manipulates header search paths in a crazy
> way [1].
>
> To fix this mess, I want all Makefiles to add explicit $(srctree)/ to
> the search paths in the srctree. Some Makefiles are already
.snip..
> > -u64 drm_get_max_iomem(void)
> > +bool drm_need_swiotlb(int dma_bits)
> > {
> > struct resource *tmp;
> > resource_size_t max_iomem = 0;
> >
> > + /*
> > +* Xen paravirtual hosts require swiotlb regardless of requested dma
> > +* transfer size.
> > +*
> > +*
Hi Dave, Daniel,
A fix for freesync to prevent stuttering in certain cases. Freesync
was added in 5.0 so it would be nice to get this in. If not, I can
just send it to stable once 5.0 is released.
The following changes since commit a213c2c7e235cfc0e0a161a558f7fdf2fb3a624a:
drm/amdgpu:
On Tue, Feb 19, 2019 at 09:30:33PM -0800, 'Ira Weiny' wrote:
> From: Ira Weiny
>
> Resending these as I had only 1 minor comment which I believe we have covered
> in this series. I was anticipating these going through the mm tree as they
> depend on a cleanup patch there and the IB changes are
On Wed, Feb 27, 2019 at 12:04 PM Johan Jonker wrote:
>
> Thanks for your advice.
>
> On 2/25/19 5:59 PM, Rob Herring wrote:> On Fri, Feb 01, 2019 at
> 01:32:35PM +0100, Johan Jonker wrote:
> >> This patch adds a binding that describes the HDMI controller for
> >> rk3066.
> >
> > This is not using
On Tue, Feb 26, 2019 at 05:03:49PM +, Russell King - ARM Linux admin wrote:
> On Tue, Feb 26, 2019 at 11:31:15AM -0500, Sven Van Asbroeck wrote:
> > There is talk in the manual about "network mode", which could work by
> > changing
> > the LRCLK only at the first slot - thereby allowing
From: Ville Syrjälä
Looks like EDID_QUIRK_FIRST_DETAILED_PREFERRED never did anything.
Its counterpart in f86EdidModes.c is properly hooked up but somehow
that functionality was lost when it was copied into the kernel.
Assuming that another preferred mode didn't sneak in somehow
(is that even
From: Ville Syrjälä
Some monitors apparently forget to mark any mode as preferred in the
EDID. In this particular case we have a very generic looking ID
"PNP Model 0 Serial Number 4" / "LVDS 800x600" so a specific quirk
doesn't seem particularly wise. Also the quirk we have
Den 27.02.2019 15.44, skrev Gerd Hoffmann:
> Just run drm_prime_pages_to_sg() on the ttm pages list to get an
> sg_table for export. The pages list is created at object initialization
> time, so there should be no need to handle an unpopulated page list.
> Add a sanity check nevertheless.
>
>
Den 27.02.2019 15.44, skrev Gerd Hoffmann:
> Sync gem vm_node.start with ttm vm_node.start,
> then we can just call drm_gem_prime_mmap().
>
> Signed-off-by: Gerd Hoffmann
> ---
Acked-by: Noralf Trønnes
___
dri-devel mailing list
Den 27.02.2019 15.44, skrev Gerd Hoffmann:
> virtio-gpu objects never move around, so effectively they are pinned
> all the time. This makes the the implementation pretty easy ;)
>
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/virtio/virtgpu_prime.c | 6 +++---
> 1 file changed, 3
Den 27.02.2019 15.27, skrev Gerd Hoffmann:
> On Mon, Feb 25, 2019 at 03:42:30PM +0100, Noralf Trønnes wrote:
>> Use devm_drm_dev_init() and drop using tinydrm_device.
>>
>> v2: devm_drm_dev_register() was dropped so add driver release callbacks.
>>
>> Signed-off-by: Noralf Trønnes
>> ---
>>
On 2/26/19 5:40 PM, John Stultz wrote:
> On Tue, Feb 26, 2019 at 11:21 AM John Stultz wrote:
>>
>> On Tue, Feb 26, 2019 at 6:47 AM Andrew F. Davis wrote:
>>> On 2/26/19 12:20 AM, John Stultz wrote:
It boots w/ AOSP, and allocations seem to work, but there's something
wrong with the
Hi,
On 27-02-19 10:44, Heikki Krogerus wrote:
On Mon, Feb 25, 2019 at 02:20:37PM +0100, Hans de Goede wrote:
Use the new drm_kms_call_oob_hotplug_notifier_chain() function to load
drm/kms drivers know about DisplayPort over Type-C hotplug events.
Signed-off-by: Hans de Goede
I'm OK with
Hi,
On 27-02-19 12:16, Jani Nikula wrote:
On Wed, 27 Feb 2019, Heikki Krogerus wrote:
One thing that this series does not consider is the DP lane count
problem. The GPU drivers (i915 in this case) does not know is four,
two or one DP lanes in use.
Also, orientation.
The orientation should
Hi Neil,
AFBC 1.0 does not support (ignoring common prefix AFBC_FORMAT_MOD_)
BLOCK_SIZE_32x8, BLOCK_SIZE_64x4, BLOCK_SIZE_32x8_64x4
CBR, TILED, SC, DB and BCH modifiers.
AFBC 1.2 does not support BLOCK_SIZE_64x4, BLOCK_SIZE_32x8_64x4, DB and BCH
modifiers.
Beyond that it's very hard to say.
https://bugs.freedesktop.org/show_bug.cgi?id=109695
--- Comment #5 from Alex Deucher ---
(In reply to Daniel P. Berrange from comment #4)
>
> I'm curious what motivated this change to start with ? Even if QEMU was not
> enforcing seccomp filters, I think I'd consider it a bug for mesa to be
>
On Wed, Feb 27, 2019 at 01:16:27PM +0200, Jani Nikula wrote:
> On Wed, 27 Feb 2019, Heikki Krogerus wrote:
> > One thing that this series does not consider is the DP lane count
> > problem. The GPU drivers (i915 in this case) does not know is four,
> > two or one DP lanes in use.
>
> Also,
Hi Hans,
On Mon, Feb 25, 2019 at 02:20:34PM +0100, Hans de Goede wrote:
> Hi All,
>
> On some Cherry Trail devices, DisplayPort over Type-C is supported through
> a USB-PD microcontroller (e.g. a fusb302) + a mux to switch the superspeed
> datalines between USB-3 and DP (e.g. a pi3usb30532). The
On Mon, Feb 25, 2019 at 02:20:37PM +0100, Hans de Goede wrote:
> Use the new drm_kms_call_oob_hotplug_notifier_chain() function to load
> drm/kms drivers know about DisplayPort over Type-C hotplug events.
>
> Signed-off-by: Hans de Goede
I'm OK with this. I'll wait for the v2 and see if I can
https://bugs.freedesktop.org/show_bug.cgi?id=109695
--- Comment #4 from Daniel P. Berrange ---
(In reply to Ahzo from comment #0)
> The problematic code at src/util/u_queue.c:252 was added in the following
> commit:
> commit d877451b48a59ab0f9a4210fc736f51da5851c9a
> Author: Marek Olšák
> Date:
virtio-gpu objects never move around, so effectively they are pinned
all the time. This makes the the implementation pretty easy ;)
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_prime.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Just run drm_prime_pages_to_sg() on the ttm pages list to get an
sg_table for export. The pages list is created at object initialization
time, so there should be no need to handle an unpopulated page list.
Add a sanity check nevertheless.
Signed-off-by: Gerd Hoffmann
---
Gerd Hoffmann (3):
drm/virtio: implement prime mmap
drm/virtio: implement prime pin/unpin
drm/virtio: implement prime export
drivers/gpu/drm/virtio/virtgpu_drv.h | 1 +
drivers/gpu/drm/virtio/virtgpu_drv.c | 2 ++
drivers/gpu/drm/virtio/virtgpu_prime.c | 25
Sync gem vm_node.start with ttm vm_node.start,
then we can just call drm_gem_prime_mmap().
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_prime.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_prime.c
https://bugs.freedesktop.org/show_bug.cgi?id=109695
--- Comment #3 from Daniel P. Berrange ---
(In reply to Ahzo from comment #2)
> To check for the availability of the syscall, one can try it in a child
> process and see if the child is terminated by a signal, e.g. like this:
Afraid not,
Quoting Christian König (2019-02-27 04:17:01)
> Am 27.02.19 um 00:04 schrieb Dave Airlie:
> >>> At the end of the day, I don't really care that much. I get it, we
> >>> all have large projects with scarce resources. I just think a few
> >>> years down the road we'll all regret it as a community.
On Mon, Feb 25, 2019 at 03:42:32PM +0100, Noralf Trønnes wrote:
> This protects device resources from use after device removal.
>
> There are 3 ways for driver-device unbinding to happen:
> - The driver module is unloaded causing the driver to be unregistered.
> This can't happen as long as
On Mon, Feb 25, 2019 at 03:42:30PM +0100, Noralf Trønnes wrote:
> Use devm_drm_dev_init() and drop using tinydrm_device.
>
> v2: devm_drm_dev_register() was dropped so add driver release callbacks.
>
> Signed-off-by: Noralf Trønnes
> ---
> drivers/gpu/drm/tinydrm/hx8357d.c | 40 +--
>
On Mon, Feb 25, 2019 at 03:42:28PM +0100, Noralf Trønnes wrote:
> Add driver example that shows how devm_drm_dev_init() can be used.
>
> v2: Expand docs (Sam, Daniel)
Acked-by: Gerd Hoffmann
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
On Mon, Feb 25, 2019 at 03:42:27PM +0100, Noralf Trønnes wrote:
> This adds a resource managed (devres) version of drm_dev_init().
>
> v2: Remove devm_drm_dev_register() since we can't touch hw in devm
> release functions and drivers want to disable hw on driver module
> unload (Daniel
On Tue, Feb 26, 2019 at 11:20 PM Hyun Kwon wrote:
>
> Hi Daniel,
>
> Thanks for the comment.
>
> On Tue, 2019-02-26 at 04:06:13 -0800, Daniel Vetter wrote:
> > On Tue, Feb 26, 2019 at 12:53 PM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Sat, Feb 23, 2019 at 12:28:17PM -0800, Hyun Kwon wrote:
>
On Mon, Feb 25, 2019 at 03:42:26PM +0100, Noralf Trønnes wrote:
> This makes it safe to access drm_device->dev after the parent device has
> been removed/unplugged.
>
> Signed-off-by: Noralf Trønnes
Reviewed-by: Gerd Hoffmann
___
dri-devel mailing
On 26/02/2019 20:23, Nicolin Chen wrote:
> This reverts commit d222e42e88168fd67e6d131984b86477af1fc256.
>
> The original change breaks omap dss:
> omapdss_dispc 58001000.dispc:
> dispc_errata_i734_wa_init: dma_alloc_writecombine failed
>
> Let's revert it first and then find a
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 5ba6c9ff961a drm/vgem: Fix mmaping.
The bot has tested the following trees: v4.20.12, v4.19.25, v4.14.103, v4.9.160.
v4.20.12: Build OK!
v4.19.25: Build OK!
v4.14.103: Build OK!
https://bugzilla.kernel.org/show_bug.cgi?id=200695
--- Comment #27 from John Doe (anode@gmail.com) ---
My RX550 is successfully booted up with 4.20 kernels and newer, but my OS
freezes every minute for 30 secs if I open youtube or play game, and anything
doesn't work upon freeze - I couldn't
Hi Liviu,
On Tue, Feb 26, 2019 at 06:39:40PM +, Liviu Dudau wrote:
> On Thu, Feb 21, 2019 at 12:32:07PM +0200, Laurent Pinchart wrote:
> > As writeback jobs contain a framebuffer, drivers may need to prepare and
> > cleanup them the same way they can prepare and cleanup framebuffers for
> >
On 26.02.2019 17:59, Colin King wrote:
> From: Colin Ian King
>
> Don't populate the const array ti_sn_bridge_supply_names on the
> stack but instead make it static.
>
> Signed-off-by: Colin Ian King
Reviewed-by: Andrzej Hajda
--
Regards
Andrzej
> ---
> drivers/gpu/drm/bridge/ti-sn65dsi86.c
Am 27.02.19 um 00:04 schrieb Dave Airlie:
At the end of the day, I don't really care that much. I get it, we
all have large projects with scarce resources. I just think a few
years down the road we'll all regret it as a community.
AMD and others have also spent years tuning TTM for both UMA
On Wed, 27 Feb 2019, Heikki Krogerus wrote:
> One thing that this series does not consider is the DP lane count
> problem. The GPU drivers (i915 in this case) does not know is four,
> two or one DP lanes in use.
Also, orientation.
> I guess that is not a critical issue since there is a
On Fri, Jan 25, 2019 at 09:40:38AM +, Russell King - ARM Linux admin wrote:
> Hi,
>
> This series adds support for programming the SPD and vendor infoframes.
>
> It also adds support for pixel repeated modes - we were not rejecting
> these modes, but we also didn't have the implementation to
Quoting Daniel Vetter (2017-08-07 10:28:58)
> On Fri, Aug 04, 2017 at 09:23:28AM +0100, Chris Wilson wrote:
> > After an event is sent, we try to copy it into the user buffer of the
> > first waiter in drm_read() and if the user buffer doesn't have enough
> > room we put it back onto the list.
Op 26-02-2019 om 17:17 schreef Matt Roper:
> On Tue, Feb 26, 2019 at 08:26:36AM +0100, Maarten Lankhorst wrote:
>> Hey,
>>
>> Op 21-02-2019 om 01:28 schreef Matt Roper:
>>> Some display controllers can be programmed to present non-black colors
>>> for pixels not covered by any plane (or pixels
Hi Robin,
Sorry for the delay in reviewing this patch, I am drowning a bit this
week in meetings :)
On Mon, Feb 25, 2019 at 02:39:13PM +, Robin Murphy wrote:
> When __drm_atomic_helper_disable_all() tries to commit the disabled
> state, we end up in hdlcd_crtc_atomic_check() with a mode
https://bugs.freedesktop.org/show_bug.cgi?id=109692
--- Comment #16 from Michel Dänzer ---
The "suspicious RCU usage" looks related to the igb ethernet driver, not
amdgpu. Quite likely it's already fixed in later 5.0-rc releases.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=109789
Michel Dänzer changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=109790
--- Comment #5 from Michel Dänzer ---
*** Bug 109789 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
On 25/02/2019 at 22:25, Alexandre Belloni wrote:
> Make the driver OF only as since AVR32 has been removed from the kernel,
> there are only OF enabled platform using it.
>
> Signed-off-by: Alexandre Belloni
It looks good to me:
Acked-by: Nicolas Ferre
Thanks Alexandre.
Best regards,
Currently, all dma-bufs share the same anonymous inode. While we can count
how many dma-buf fds or mappings a process has, we can't get the size of
the backing buffers or tell if two entries point to the same dma-buf. And
in debugfs, we can get a per-buffer breakdown of size and reference count,
On Tue, Feb 26, 2019 at 12:01:55PM -0800, Tony Lindgren wrote:
> Looks like commit d222e42e8816 ("dma-contiguous: do not allocate a
> single page from CMA area") caused a regression at least for
> omap dss where we now get the following error on init:
>
> omapdss_dispc 58001000.dispc:
>
Replace explicit polling loop with equivalent call to
regmap_read_poll_timeout() for simplicity. No functional change
intended.
Signed-off-by: Andrey Smirnov
Cc: Archit Taneja
Cc: Andrzej Hajda
Cc: Laurent Pinchart
Cc: Chris Healy
Cc: Lucas Stach
Cc: dri-devel@lists.freedesktop.org
Cc:
Tc_wait_pll_lock() is always called as a follow-up for updating
PLLUPDATE and PLLEN bit of a given PLL control register. To simplify
things, merge the two operation into a single helper function
tc_pllupdate_pllen() and convert the rest of the code to use it. No
functional change intended.
1 - 100 of 121 matches
Mail list logo