Re: [PATCH v5 3/6] drm/i915/panelreplay: Initializaton and compute config for panel replay

On Tue, 2023-09-05 at 13:05 +0530, Animesh Manna wrote: > Modify existing PSR implementation to enable panel replay feature of > DP 2.0 > which is similar to PSR feature of EDP panel. There is different DPCD > address to check panel capability compare to PSR and vsc sdp header > is different. > >

[PATCH v6 0/5] drm/amdgpu: Rework coredump memory allocation

Hi, The patches of this set are a rework to alloc devcoredump dynamically and to move it to a better source file. Thanks, André Changelog: v5: https://lore.kernel.org/lkml/20230817182050.205925-1-andrealm...@igalia.com/ - Added Shashank Sharma R-b tag v4: https://lore.kernel.org/dri-d

[PATCH v6 2/5] drm/amdgpu: Rework coredump to use memory dynamically

Instead of storing coredump information inside amdgpu_device struct, move if to a proper separated struct and allocate it dynamically. This will make it easier to further expand the logged information. Signed-off-by: André Almeida Reviewed-by: Shashank Sharma --- v6: no change v5: no change v4:

[PATCH v6 1/5] drm/amdgpu: Allocate coredump memory in a nonblocking way

During a GPU reset, a normal memory reclaim could block to reclaim memory. Giving that coredump is a best effort mechanism, it shouldn't disturb the reset path. Change its memory allocation flag to a nonblocking one. Signed-off-by: André Almeida Reviewed-by: Christian König --- v5: no change ---

[PATCH v6 4/5] drm/amdgpu: Move coredump code to amdgpu_reset file

Giving that we use codedump just for device resets, move it's functions and structs to a more semantic file, the amdgpu_reset.{c, h}. Signed-off-by: André Almeida Reviewed-by: Shashank Sharma --- v6: no change v5: no change --- drivers/gpu/drm/amd/amdgpu/amdgpu.h| 9 --- drivers/gpu/dr

[PATCH v6 5/5] drm/amdgpu: Create version number for coredumps

Even if there's nothing currently parsing amdgpu's coredump files, if we eventually have such tools they will be glad to find a version field to properly read the file. Create a version number to be displayed on top of coredump file, to be incremented when the file format or content get changed.

[PATCH v6 3/5] drm/amdgpu: Encapsulate all device reset info

To better organize struct amdgpu_device, keep all reset information related fields together in a separated struct. Signed-off-by: André Almeida Reviewed-by: Shashank Sharma --- v6: no changes v5: new patch, as required by Shashank Sharma --- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 34

[PATCH 9/9] dma_buf: heaps: mtk_sec_heap: Add a new CMA heap

Create a new mtk_svp_cma heap from the CMA reserved buffer. When the first allocating buffer, use cma_alloc to prepare whole the CMA range, then send its range to TEE to protect and manage. For the later allocating, we just adds the cma_used_size. When SVP done, cma_release will release the buffe

[PATCH 8/9] dt-bindings: reserved-memory: MediaTek: Add reserved memory for SVP

This adds the binding for describing a CMA memory for MediaTek SVP(Secure Video Path). Signed-off-by: Yong Wu --- .../mediatek,secure_cma_chunkmem.yaml | 42 +++ 1 file changed, 42 insertions(+) create mode 100644 Documentation/devicetree/bindings/reserved-memory/mediat

[PATCH 7/9] dma-buf: heaps: mtk_sec_heap: Add dma_ops

Add the dma_ops for this secure heap. a) For secure buffer, cache_ops/mmap are not allowed, thus return EPERM for them. b) The secure buffer can't be accessed in kernel, thus it doesn't have va/dma_address for it. Use the dma_address property to save the "secure handle". Signed-off-by: Anan Sun S

[PATCH 6/9] dma-buf: heaps: mtk_sec_heap: Add tee service call for buffer allocating/freeing

Add TEE service call for secure memory allocating/freeing. Signed-off-by: Anan Sun Signed-off-by: Yong Wu --- drivers/dma-buf/heaps/mtk_secure_heap.c | 69 - 1 file changed, 68 insertions(+), 1 deletion(-) diff --git a/drivers/dma-buf/heaps/mtk_secure_heap.c b/drivers/

[PATCH 5/9] dma-buf: heaps: mtk_sec_heap: Initialise tee session

The TEE probe later than dma-buf heap, and PROBE_DEDER doesn't work here since this is not a platform driver, therefore initialise the TEE context/session while we allocate the first secure buffer. Signed-off-by: Yong Wu --- drivers/dma-buf/heaps/mtk_secure_heap.c | 61 +

[PATCH 4/9] dma-buf: heaps: Initialise MediaTek secure heap

Initialise a mtk_svp heap. Currently just add a null heap, Prepare for the later patches. Signed-off-by: Yong Wu --- drivers/dma-buf/heaps/Kconfig | 8 ++ drivers/dma-buf/heaps/Makefile | 1 + drivers/dma-buf/heaps/mtk_secure_heap.c | 99 + 3 files ch

[PATCH 3/9] dma-heap: Provide accessors so that in-kernel drivers can allocate dmabufs from specific heaps

From: John Stultz This allows drivers who don't want to create their own DMA-BUF exporter to be able to allocate DMA-BUFs directly from existing DMA-BUF Heaps. There is some concern that the premise of DMA-BUF heaps is that userland knows better about what type of heap memory is needed for a pip

[PATCH 2/9] dma-heap: Add proper kref handling on dma-buf heaps

From: John Stultz Add proper refcounting on the dma_heap structure. While existing heaps are built-in, we may eventually have heaps loaded from modules, and we'll need to be able to properly handle the references to the heaps Also moves minor tracking into the heap structure so we can properly f

[PATCH 1/9] dma-buf: heaps: Deduplicate docs and adopt common format

From: "T.J. Mercier" The docs for dma_heap_get_name were incorrect, and since they were duplicated in the implementation file they were wrong there too. The docs formatting was inconsistent so I tried to make it more consistent across functions since I'm already in here doing cleanup. Remove mu

[PATCH 0/9] dma-buf: heaps: Add MediaTek secure heap

This patchset consists of two parts, the first is from John and TJ. It adds some heap interfaces, then our kernel users could allocate buffer from special heap. The second part is adding MTK secure heap for SVP (Secure Video Path). A total of two heaps are added, one is mtk_svp and the other is mtk

Re: [PATCH v2 2/5] kernel: kexec: copy user-array safely

On 09/08/23 at 09:59pm, Philipp Stanner wrote: > Currently, there is no overflow-check with memdup_user(). > > Use the new function memdup_array_user() instead of memdup_user() for > duplicating the user-space array safely. > > Suggested-by: David Airlie > Signed-off-by: Philipp Stanner > --- >

[PATCH] drm/amd/display: fix replay_mode kernel-doc warning

Fix the typo in the kernel-doc for @replay_mode to prevent kernel-doc warnings: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:623: warning: Incorrect use of kernel-doc format: * @replay mode: Replay supported drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:626: warning: Function p

Re: [PATCH] drm/simpledrm: Add support for multiple "power-domains"

pledrm_device_create(struct drm_driver *drv, if (ret) return ERR_PTR(ret); ret = simpledrm_device_init_regulators(sdev); + if (ret) + return ERR_PTR(ret); + ret = simpledrm_device_attach_genpd(sdev); if (ret) return ERR_PTR(ret); --- base-commit: 15d30b46573d75f5cb58cfacded8ebab9c76a2b0 change-id: 20230910-simpledrm-multiple-power-domains-f41efa6ad9bc Best regards,

Re: [PATCH] drm: fix doc warnings related to drm connector

On 9/9/23 23:37, Bragatheswaran Manickavel wrote: >>On Sun, 10 Sept 2023 at 09:29, Randy Dunlap >> wrote: >>On 9/9/23 20:54, Bagas Sanjaya wrote: >>> On Sat, Sep 09, 2023 at 04:33:43PM +0530, Bragatheswaran Manickavel wrote: Addressing drm dp/hdmi connector rel

Re: [git pull] drm CI integration

The pull request you sent on Thu, 31 Aug 2023 11:00:20 +1000: > git://anongit.freedesktop.org/drm/drm tags/topic/drm-ci-2023-08-31-1 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/1548b060d6f32a00a2f7e2c11328205fb66fc4fa Thank you! -- Deet-doot-dot, I am a bot. http

Re: [PATCH] drm/simpledrm: Add support for multiple "power-domains"

On 2023-09-10 18:39:39 +0200, Janne Grunau via B4 Relay wrote: > From: Janne Grunau > > Multiple power domains need to be handled explicitly in each driver. The > driver core can not handle it automatically since it is not aware of > power sequencing requirements the hardware might have. This is

Re: [git pull] drm CI integration

On Wed, 30 Aug 2023 at 18:00, Dave Airlie wrote: > > This is a PR to add drm-ci support files to the upstream tree. So I finally had no other pull requests pending, and spent some time looking at this, and I see nothing offensive. I did wonder how this then expands to having more than one subsys

Re: [PATCH] drm/simpledrm: Add support for multiple "power-domains"

: 15d30b46573d75f5cb58cfacded8ebab9c76a2b0 patch link: https://lore.kernel.org/r/20230910-simpledrm-multiple-power-domains-v1-1-f8718aefc685%40jannau.net patch subject: [PATCH] drm/simpledrm: Add support for multiple "power-domains" config: loongarch-allyesconfig (https://download.01.o

Re: [PATCH 00/11] add missing of_node_put

Hello: This patch was applied to netdev/net.git (main) by David S. Miller : On Thu, 7 Sep 2023 11:55:10 +0200 you wrote: > Add of_node_put on a break out of an of_node loop. > > --- > > arch/powerpc/kexec/file_load_64.c|8 ++-- > arch/powerpc/platforms/powermac/low

[PATCH] drm/simpledrm: Add support for multiple "power-domains"

ev) +{ + return 0; +} +#endif + /* * Modesetting */ @@ -651,6 +754,9 @@ static struct simpledrm_device *simpledrm_device_create(struct drm_driver *drv, if (ret) return ERR_PTR(ret); ret = simpledrm_device_init_regulators(sdev); + if (ret) + r

[Bug 217896] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2985 thread Xwayland:cs0 pid 3129

https://bugzilla.kernel.org/show_bug.cgi?id=217896 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Reso

[Bug 217896] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2985 thread Xwayland:cs0 pid 3129

https://bugzilla.kernel.org/show_bug.cgi?id=217896 sander44 (ionut_n2...@yahoo.com) changed: What|Removed |Added Kernel Version||6.5.2 -- You may repl

[Bug 217896] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2985 thread Xwayland:cs0 pid 3129

https://bugzilla.kernel.org/show_bug.cgi?id=217896 --- Comment #2 from sander44 (ionut_n2...@yahoo.com) --- Created attachment 305079 --> https://bugzilla.kernel.org/attachment.cgi?id=305079&action=edit dmesg -- You may reply to this email to add a comment. You are receiving this mail because

[Bug 217896] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2985 thread Xwayland:cs0 pid 3129

https://bugzilla.kernel.org/show_bug.cgi?id=217896 --- Comment #1 from sander44 (ionut_n2...@yahoo.com) --- Created attachment 305078 --> https://bugzilla.kernel.org/attachment.cgi?id=305078&action=edit journalctl -- You may reply to this email to add a comment. You are receiving this mail be

[Bug 217896] New: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2985 thread Xwayland:cs0 pid 3129

https://bugzilla.kernel.org/show_bug.cgi?id=217896 Bug ID: 217896 Summary: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2985 thread Xwayland:cs0 pid 3129 Product: Drivers Ve

Re: [syzbot] [mm?] kernel BUG in filemap_unaccount_folio

On 9/10/2023 3:02 PM, Kasireddy, Vivek wrote: > Hi Fengwei, > >> >> Add udmabuf maintainers. >> >> On 9/7/2023 2:51 AM, syzbot wrote: >>> Hello, >>> >>> syzbot found the following issue on: >>> >>> HEAD commit:db906f0ca6bb Merge tag 'phy-for-6.6' of git://git.kernel.o.. >>> git tree:

[Bug 217892] [amdgpu]: system freezes when trying to turn back on monitor

https://bugzilla.kernel.org/show_bug.cgi?id=217892 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Reso

[PATCH v2] drm/ssd130x: Store the HW buffer in the driver-private CRTC state

The commit 45b58669e532 ("drm/ssd130x: Allocate buffer in the plane's .atomic_check() callback") moved the allocation of the intermediate and HW buffers from the encoder's .atomic_enable callback, to the plane's .atomic_check callback. This was suggested by Maxime Ripard, because drivers aren't al

Re: [PATCH] drm: fix doc warnings related to drm connector

On Sun, 10 Sept 2023 at 09:29, Randy Dunlap wrote: >On 9/9/23 20:54, Bagas Sanjaya wrote: >> On Sat, Sep 09, 2023 at 04:33:43PM +0530, Bragatheswaran Manickavel wrote: >>> Addressing drm dp/hdmi connector related kernel documentation >>> warning and add more information about these values. >> >> W

Re: [PATCH v2 1/5] string.h: add array-wrappers for (v)memdup_user()

On Fri, Sep 8, 2023 at 11:02 PM Philipp Stanner wrote: > > Currently, user array duplications are sometimes done without an > overflow check. Sometimes the checks are done manually; sometimes the > array size is calculated with array_size() and sometimes by calculating > n * size directly in code.

RE: [syzbot] [mm?] kernel BUG in filemap_unaccount_folio

Hi Fengwei, > > Add udmabuf maintainers. > > On 9/7/2023 2:51 AM, syzbot wrote: > > Hello, > > > > syzbot found the following issue on: > > > > HEAD commit:db906f0ca6bb Merge tag 'phy-for-6.6' of git://git.kernel.o.. > > git tree: upstream > > console+strace: https://syzkaller.appspot.