dri-devel February 2021

dri-devel@lists.freedesktop.org

314 participants
684 discussions

[PATCH] drm/kmb: remove unneeded semicolon
by Yang Li 02 Feb '21

02 Feb '21

Eliminate the following coccicheck warning: ./drivers/gpu/drm/kmb/kmb_dsi.c:281:3-4: Unneeded semicolon ./drivers/gpu/drm/kmb/kmb_dsi.c:301:3-4: Unneeded semicolon ./drivers/gpu/drm/kmb/kmb_dsi.c:318:3-4: Unneeded semicolon ./drivers/gpu/drm/kmb/kmb_dsi.c:337:3-4: Unneeded semicolon ./drivers/gpu/drm/kmb/kmb_dsi.c:361:2-3: Unneeded semicolon Reported-by: Abaci Robot <abaci(a)linux.alibaba.com> Signed-off-by: Yang Li <yang.lee(a)linux.alibaba.com> --- drivers/gpu/drm/kmb/kmb_dsi.c |… [View More]

1 0

[PATCH v5 0/8] drm/mediatek: add support for mediatek SOC MT8192
by Hsin-Yi Wang 02 Feb '21

02 Feb '21

This series are based on kernel/git/chunkuang.hu/linux.git mediatek-drm-next and following patch: ("soc: mediatek: add mtk mutex support for MT8183") https://patchwork.kernel.org/project/linux-mediatek/patch/20210129092209.25… This series also depends on component support in mmsys[1]: - [v4,06/10] soc: mediatek: mmsys: add component OVL_2L2 - [v4,07/10] soc: mediatek: mmsys: add component POSTMASK - [v4,08/10] soc: mediatek: mmsys: add component RDMA4 [1] https://patchwork.kernel.org/project/… [View More]

2 12

[PATCH v2 0/2] drm: aspeed: Support more chip families
by Joel Stanley 02 Feb '21

02 Feb '21

The out of tree vendor driver was recently updated to support the ast2400 and ast2600. These patches begin to add that support to the mainline driver. With these two cleanups it should be easier to support different families of BMC system on chip with this driver. I will merge them through drm-misc once they have been reviewed. v2 fixes review from Jeremy. Thanks! Joel Stanley (2): drm/aspeed: Look up syscon by phandle drm/aspeed: Use dt matching for default register values drivers/… [View More]

1 2

[PATCH 0/2] drm: aspeed: Support more chip families
by Joel Stanley 02 Feb '21

02 Feb '21

The out of tree vendor driver was recently updated to support the ast2400 and ast2600. These patches begin to add that support to the mainline driver. With these two cleanups it should be easier to support different families of BMC system on chip with this driver. I will merge them through drm-misc once they have been reviewed. Joel Stanley (2): drm/aspeed: Look up syscon by phandle drm/aspeed: Use dt matching for default register values drivers/gpu/drm/aspeed/aspeed_gfx.h | 7 +--… [View More]

2 6

Re: [PATCH 1/1] dma-buf: heaps: Map system heap pages as managed by linux vm
by Suren Baghdasaryan 02 Feb '21

02 Feb '21

On Thu, Jan 28, 2021 at 1:13 AM Christoph Hellwig <hch(a)infradead.org> wrote: > > On Thu, Jan 28, 2021 at 12:38:17AM -0800, Suren Baghdasaryan wrote: > > Currently system heap maps its buffers with VM_PFNMAP flag using > > remap_pfn_range. This results in such buffers not being accounted > > for in PSS calculations because vm treats this memory as having no > > page structs. Without page structs there are no counters representing > > how many processes … [View More]are mapping a page and therefore PSS calculation > > is impossible. > > Historically, ION driver used to map its buffers as VM_PFNMAP areas > > due to memory carveouts that did not have page structs [1]. That > > is not the case anymore and it seems there was desire to move away > > from remap_pfn_range [2]. > > Dmabuf system heap design inherits this ION behavior and maps its > > pages using remap_pfn_range even though allocated pages are backed > > by page structs. > > Clear VM_IO and VM_PFNMAP flags when mapping memory allocated by the > > system heap and replace remap_pfn_range with vm_insert_page, following > > Laura's suggestion in [1]. This would allow correct PSS calculation > > for dmabufs. > > > > [1] https://driverdev-devel.linuxdriverproject.narkive.com/v0fJGpaD/using-ion-m… > > [2] http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-Octo… > > (sorry, could not find lore links for these discussions) > > > > Suggested-by: Laura Abbott <labbott(a)kernel.org> > > Signed-off-by: Suren Baghdasaryan <surenb(a)google.com> > > --- > > drivers/dma-buf/heaps/system_heap.c | 6 ++++-- > > 1 file changed, 4 insertions(+), 2 deletions(-) > > > > diff --git a/drivers/dma-buf/heaps/system_heap.c b/drivers/dma-buf/heaps/system_heap.c > > index 17e0e9a68baf..0e92e42b2251 100644 > > --- a/drivers/dma-buf/heaps/system_heap.c > > +++ b/drivers/dma-buf/heaps/system_heap.c > > @@ -200,11 +200,13 @@ static int system_heap_mmap(struct dma_buf *dmabuf, struct vm_area_struct *vma) > > struct sg_page_iter piter; > > int ret; > > > > + /* All pages are backed by a "struct page" */ > > + vma->vm_flags &= ~VM_PFNMAP; > > Why do we clear this flag? It shouldn't even be set here as far as I > can tell. Thanks for the question, Christoph. I tracked down that flag being set by drm_gem_mmap_obj() which DRM drivers use to "Set up the VMA to prepare mapping of the GEM object" (according to drm_gem_mmap_obj comments). I also see a pattern in several DMR drivers to call drm_gem_mmap_obj()/drm_gem_mmap(), then clear VM_PFNMAP and then map the VMA (for example here: https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/rockchip/roc…). I thought that dmabuf allocator (in this case the system heap) would be the right place to set these flags because it controls how memory is allocated before mapping. However it's quite possible that I'm missing the real reason for VM_PFNMAP being set in drm_gem_mmap_obj() before dma_buf_mmap() is called. I could not find the answer to that, so I hope someone here can clarify that. [View Less]

2 3

should we do GSoC 2021?
by Trevor Woerner 01 Feb '21

01 Feb '21

Hi everyone, There are discussions regarding whether or not we want to participate in GSoC this year. Org applications are open now until Feb 19. Last year at the GSoC Mentor Summit (Oct 2020) it was announced that changes were coming to GSoC 2021: - the amount of time a student is expected to spend on a project is halved - stipends are halved - overall duration is shortened to 10 weeks - lowered eligibility requirements As a result, project expectations are supposed to be reduced as well. … [View More]

1 0

[PATCH v2] drm/panel: simple: add SGD GKTW70SDAD1SD
by Oliver Graute 01 Feb '21

01 Feb '21

Add support for the Solomon Goldentek Display Model: GKTW70SDAD1SD to panel-simple. The panel spec from Variscite can be found at: https://www.variscite.com/wp-content/uploads/2017/12/VLCD-CAP-GLD-RGB.pdf Signed-off-by: Oliver Graute <oliver.graute(a)gmail.com> Cc: Marco Felsch <m.felsch(a)pengutronix.de> Cc: Fabio Estevam <festevam(a)gmail.com> --- v2: - changed bpc to 6 - set max value of pixelclock - increased hfront_porch and hback_porch - dropped connector-type … [View More]

2 2

[PATCH] drm/v3d/v3d_sched: fix scheduler callbacks return status
by Christian König 01 Feb '21

01 Feb '21

Looks like this was not correctly adjusted. Signed-off-by: Christian König <christian.koenig(a)amd.com> Fixes: a6a1f036c74e ("drm/scheduler: Job timeout handler returns status (v3)") --- drivers/gpu/drm/v3d/v3d_sched.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/v3d/v3d_sched.c b/drivers/gpu/drm/v3d/v3d_sched.c index ef2338a294ca..ceb33f8e4379 100644 --- a/drivers/gpu/drm/v3d/v3d_sched.c +++ b/drivers/gpu/drm/v3d/v3d_sched.c @@ -259,7 … [View More]

3 2

Re: linux-next: Tree for Feb 1 (drivers/gpu/drm/i915/i915_gem.c)
by Randy Dunlap 01 Feb '21

01 Feb '21

On 2/1/21 1:14 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20210129: > still seeing this one: on x86_64: ../drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_freeze_late’: ../drivers/gpu/drm/i915/i915_gem.c:1182:2: error: implicit declaration of function ‘wbinvd_on_all_cpus’; did you mean ‘wrmsr_on_cpus’? [-Werror=implicit-function-declaration] wbinvd_on_all_cpus(); Full randconfig file is attached. -- ~Randy Reported-by: Randy Dunlap <rdunlap(a)infradead.org>

1 0

[PATCH 3/3] video: fbdev: fix the out-of-bounds access cr_data->bak
by Wenjia Zhao 01 Feb '21

01 Feb '21

The size of cr_data->bak is CURSOR_SIZE/4, however the access size in the is CURSOR_SIZE in the loop. It causes the out-of-bounds access. Signed-off-by: Wenjia Zhao <driverfuzzing(a)gmail.com> --- drivers/video/fbdev/via/viafbdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/fbdev/via/viafbdev.c b/drivers/video/fbdev/via/viafbdev.c index 22deb34..ef217cc 100644 --- a/drivers/video/fbdev/via/viafbdev.c +++ b/drivers/video/fbdev/via/viafbdev.c @@ -… [View More]

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2021