Am Sa., 5. Juni 2021 um 14:18 Uhr schrieb Bernard Zhao :
>
> NULL check before kvfree functions is not needed.
>
> Signed-off-by: Bernard Zhao
> ---
> drivers/gpu/drm/etnaviv/etnaviv_gem_prime.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/etnaviv/etn
Am Sa., 5. Juni 2021 um 14:24 Uhr schrieb Bernard Zhao :
>
> NULL check before kvfree functions is not needed.
>
> Signed-off-by: Bernard Zhao
> ---
> drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c | 12
> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm
Am 04.06.21 um 19:30 schrieb Ville Syrjälä:
On Fri, Jun 04, 2021 at 07:17:23PM +0200, Werner Sembach wrote:
This commits implements the "active bpc" drm property for the Intel GPU driver.
Signed-off-by: Werner Sembach
---
drivers/gpu/drm/i915/display/intel_display.c | 13 +
dr
Am 04.06.21 um 19:26 schrieb Ville Syrjälä:
On Fri, Jun 04, 2021 at 07:17:21PM +0200, Werner Sembach wrote:
Add a new general drm property "active bpc" which can be used by graphic drivers
to report the applied bit depth per pixel back to userspace.
While "max bpc" can be used to change the c
Ah, yes. I've forgot to include the infiniband subdir in the automated
rename. I should have done that treewide.
Going to provide a fix in a minute, sorry for the noise.
Christian.
Am 07.06.21 um 04:33 schrieb Stephen Rothwell:
Hi all,
After merging the drm-misc tree, today's linux-next buil
On Saturday, 5 June 2021 10:41:03 AM AEST Shakeel Butt wrote:
> External email: Use caution opening links or attachments
>
>
> On Fri, Jun 4, 2021 at 1:49 PM Liam Howlett wrote:
> >
> > * Shakeel Butt [210525 19:45]:
> > > On Tue, May 25, 2021 at 11:40 AM Liam Howlett
wrote:
> > > >
> > > [..
On Sat, Jun 5, 2021 at 1:48 AM Will Deacon wrote:
>
> Hi Claire,
>
> On Thu, May 27, 2021 at 08:58:30PM +0800, Claire Chang wrote:
> > This series implements mitigations for lack of DMA access control on
> > systems without an IOMMU, which could result in the DMA accessing the
> > system memory at
Hi all,
After merging the drm-misc tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/infiniband/core/umem_dmabuf.c: In function 'ib_umem_dmabuf_map_pages':
drivers/infiniband/core/umem_dmabuf.c:69:10: error: implicit declaration of
function 'dma_resv_get_excl'; d
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
between commits:
b453e42a6e8b ("drm/amdgpu: Add new placement for preemptible SG BOs")
19a1d9350be6 ("drm/amdgpu: flush gart changes after all BO recovery")
from the drm and a
From: Saravana Kannan
On sunxi boards that use HDMI output, HDMI device probe keeps being
avoided indefinitely with these repeated messages in dmesg:
platform 1ee.hdmi: probe deferral - supplier 1ef.hdmi-phy
not ready
There's a fwnode_link being created with fw_devlink=on between
01.06.2021 07:21, Dmitry Osipenko пишет:
> This series adds memory bandwidth management to the NVIDIA Tegra DRM driver,
> which is done using interconnect framework. It fixes display corruption that
> happens due to insufficient memory bandwidth.
>
> Changelog:
>
> v18: - Moved total peak bandwid
If an error occurs after a successful 'uvesafb_init_mtrr()' call, it must
be undone by a corresponding 'arch_phys_wc_del()' call, as already done in
the remove function.
This has been added in the remove function in commit 63e28a7a5ffc
("uvesafb: Clean up MTRR code")
Fixes: 8bdb3a2d7df4 ("uvesafb
As the name implies if testing all fences is requested we
should indeed test all fences and not skip the exclusive
one because we see shared ones.
Signed-off-by: Christian König
---
drivers/dma-buf/dma-resv.c | 33 -
1 file changed, 12 insertions(+), 21 deletions(
We no longer need to add the exclusive fence as shared fence as
welldrm/amdgpu: drop workaround for adding page table clears as shared
fence
We no longer need to add the exclusive fence as shared fence as well..
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 8 +---
As discussed with Daniel we want to drop the rule that all
shared fences must signal after the exclusive fence.
This means that drivers also need to to sync to the
exclusive fence when a shared one is present.
Signed-off-by: Christian König
---
drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +-
1
Hi Daniel,
as discussed here are the patches which change the handle around exclusive
fence handling.
The main problem seems to have been the dma_resv_test_signaled() function which
ignored the exclusive fence when shared fences where present. This was already
rather inconsistent since dma_fen
Am 02.06.21 um 22:34 schrieb Jason Ekstrand:
On Wed, Jun 2, 2021 at 6:17 AM Christian König
wrote:
The functions can be called both in _rcu context as well
as while holding the lock.
Signed-off-by: Christian König
---
drivers/dma-buf/dma-buf.c | 3 +--
drivers/dma-buf/
Am 02.06.21 um 22:22 schrieb Jason Ekstrand:
On Wed, Jun 2, 2021 at 6:17 AM Christian König
wrote:
When the comment needs to state explicitly that this is doesn't get a reference
to the object then the function is named rather badly.
Rename the function and use it in even more places.
Signed-
18 matches
Mail list logo
