Well the driver load is interrupted for some reason.
Have you set any timeout for modprobe?
Regards,
Christian.
Am 12.01.24 um 09:11 schrieb Thomas Perrot:
Hello,
We are updating the kernel from the 6.1 to the 6.6 and we observe an
amdgpu’s regression with Radeon RX580 8GB and SiFive
Hello,
We are updating the kernel from the 6.1 to the 6.6 and we observe an
amdgpu’s regression with Radeon RX580 8GB and SiFive Unmatched:
“workqueue: Failed to create a rescuer kthread for wq 'amdgpu-reset-
dev': -EINTR
[drm:amdgpu_reset_create_reset_domain [amdgpu]] *ERROR* Failed to
allocate
Initialize a restricted heap. Currently just add a null heap, Prepare for
the later patches.
Signed-off-by: Yong Wu
---
drivers/dma-buf/heaps/Kconfig | 9
drivers/dma-buf/heaps/Makefile | 3 +-
drivers/dma-buf/heaps/restricted_heap.c | 67 +
Add the dma_ops for this restricted heap. For restricted buffer,
cache_ops/mmap are not allowed, thus return EPERM for them.
Signed-off-by: Yong Wu
---
drivers/dma-buf/heaps/restricted_heap.c | 103
1 file changed, 103 insertions(+)
diff --git
Hi,
On Thu, 12 Oct 2023 10:42:08 +0200, Alexander Stein wrote:
> The DE signal is active high on this display, fill in the missing
> bus_flags. This aligns panel_desc with its display_timing.
>
> Fixes: 9a2654c0f62a ("drm/panel: Add and fill drm_panel type field")
> Fixes: b3bfcdf8a3b6
Add "struct restricted_heap_ops". For the restricted memory, totally there
are two steps:
a) memory_alloc: Allocate the buffer in kernel;
b) memory_restrict: Restrict/Protect/Secure that buffer.
The memory_alloc is mandatory while memory_restrict is optinal since it may
be part of memory_alloc.
The purpose of this patchset is for MediaTek secure video playback, and
also to enable other potential uses of this in the future. The 'restricted
dma-heap' will be used to allocate dma_buf objects that reference memory
in the secure world that is inaccessible/unmappable by the non-secure
(i.e.
Add a binding for describing the dynamic restricted reserved memory range.
The memory range also will be defined in the TEE firmware. It means the TEE
will be configured with the same address/size that is being set in this
DT node. Regarding to the detail TEE command, Please search
Hi,
On Wed, 20 Dec 2023 10:48:53 +0800, yang.gua...@zte.com.cn wrote:
> dev_err_probe() can check if the error code is -EPROBE_DEFER
> and can return the error code, replacing dev_err() with it
> simplifies the code.
>
>
Thanks, Applied to https://anongit.freedesktop.org/git/drm/drm-misc.git
Hi,
On Mon, 25 Dec 2023 22:26:15 +0800, chenguanxi11...@163.com wrote:
> dev_err_probe() can check if the error code is -EPROBE_DEFER
> and can return the error code, replacing dev_err() with it
> simplifies the code.
>
>
Thanks, Applied to https://anongit.freedesktop.org/git/drm/drm-misc.git
On Fri, 12 Jan 2024 17:20:07 +0800
Yong Wu wrote:
> The purpose of this patchset is for MediaTek secure video playback, and
> also to enable other potential uses of this in the future. The 'restricted
> dma-heap' will be used to allocate dma_buf objects that reference memory
> in the secure
On Fri Jan 12, 2024 at 10:14 AM CET, Neil Armstrong wrote:
> On 12/01/2024 10:00, Luca Weiss wrote:
> > On Thu Jan 11, 2024 at 8:05 PM CET, Linus Walleij wrote:
> >> On Thu, Jan 11, 2024 at 4:28 PM Luca Weiss
> >> wrote:
> >>
> >>> In some internal documentation it says "LCD Driver IC"
Managarm mainly follows the Linux ABI, and so needs to be in the Linux
path when including needed headers here.
Signed-off-by: Alexander Richards
---
include/uapi/drm/drm.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/uapi/drm/drm.h b/include/uapi/drm/drm.h
index
On Wed, Jan 10, 2024 at 11:53:51AM +0100, Daniel Vetter wrote:
> On Tue, Jan 09, 2024 at 10:59:47PM -0800, Shradha Gupta wrote:
> > In drm_kms_helper_poll_disable() check if output polling
> > support is initialized before disabling polling.
> > For drivers like hyperv-drm, that do not initialize
On Fri, Jan 12, 2024 at 10:52 AM Luca Weiss wrote:
> Since there's zero indication Truly is involved in this panel in my
> documentation - much less the number 5P65 - I'm not going to add that.
OK then, I fold, thanks for looking into it.
Keep the Himax hx83112a file name and symbols.
> So in
https://bugzilla.kernel.org/show_bug.cgi?id=218368
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
On 08/01/2024 11:20, Maxime Ripard wrote:
Hi,
On Thu, Jan 04, 2024 at 05:00:49PM +0100, Jocelyn Falempe wrote:
This was initialy done for imx6, but should work on most drivers
using drm_fb_dma_helper.
Signed-off-by: Jocelyn Falempe
---
drivers/gpu/drm/drm_fb_dma_helper.c | 55
On Fri, Jan 12, 2024 at 10:41:14AM +0100, Daniel Vetter wrote:
> On Fri, Jan 12, 2024 at 05:20:11PM +0800, Yong Wu wrote:
> > Add the dma_ops for this restricted heap. For restricted buffer,
> > cache_ops/mmap are not allowed, thus return EPERM for them.
> >
> > Signed-off-by: Yong Wu
> > ---
>
On 12/01/2024 11:23, Linus Walleij wrote:
On Fri, Jan 12, 2024 at 10:52 AM Luca Weiss wrote:
Since there's zero indication Truly is involved in this panel in my
documentation - much less the number 5P65 - I'm not going to add that.
Ack
OK then, I fold, thanks for looking into it.
Keep
Hi Rob,
On 09/01/24 01:20, Rob Clark wrote:
From: Rob Clark
The msm tests should skip on non-msm hw, so I think it should be safe to
enable everywhere.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/ci/testlist.txt | 49 +
1 file changed, 49 insertions(+)
When lima_vm_map_bo fails, the resources need to be deallocated, or
there will be memleaks.
Fixes: 6aebc51d7aef ("drm/lima: support heap buffer creation")
Signed-off-by: Zhipeng Lu
---
drivers/gpu/drm/lima/lima_gem.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
On 10/01/2024 09:22, Alexander Stein wrote:
At least the pixelclock has a range which can vary. Convert fixed mode
into display timings so they can be overwritten in DT if necessary.
Signed-off-by: Alexander Stein
---
Changes in v2:
* Rebase to next-20240110
From: Neil Armstrong
Hi,
On Tue, 02 Jan 2024 17:15:43 +0100, Manuel Traut wrote:
> This adds support for the BOE TH101MB31IG002 LCD Panel used in PineTab2 [1]
> and
> PineTab-V [2] as well as the devictrees for the PineTab2 v0.1 and v2.0.
>
> The BOE LCD Panel patch was retrieved from [3].
Hi,
On Mon, 23 Oct 2023 13:55:58 +0200, Arnd Bergmann wrote:
> As with several other panel drivers, this fails to link without the DP
> helper library:
>
> ld: drivers/gpu/drm/panel/panel-raydium-rm692e5.o: in function
> `rm692e5_prepare':
> panel-raydium-rm692e5.c:(.text+0x11f4): undefined
On Fri, Dec 22, 2023 at 08:27:14PM -0500, Zack Rusin wrote:
> On Tue, Dec 19, 2023 at 11:15 AM Stefan Hoffmeister
> wrote:
> >
> >
> > Hi,
> >
> > vmwgfx implements drmPrimeFDToHandle in terms of the TTM resource manager.
> >
> > At the same time, the driver advertises
> >
> >
Hi Jani,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.7 next-20240112]
[If your patch is applied to the wrong git
On Thu, Jan 11, 2024 at 09:17:31PM -0800, Randy Dunlap wrote:
> The functions that were described in this section of
> drm-internals.rst were removed in NOV-2023, along with all of the
> kernel-doc comments in the source file. This now causes a
> docs build warning, so remove that section of the
Add a Mediatek restricted heap which uses TEE service call to restrict
buffer. Currently this restricted heap is NULL, Prepare for the later
patch. Mainly there are two changes:
a) Add a heap_init ops since TEE probe late than restricted heap, thus
initialize the heap when we require the buffer
Add TEE service call for MediaTek heap. We have a limited number of
hardware entries to protect memory, therefore we cannot protect memory
arbitrarily, and our secure memory management is actually inside OPTEE.
The kernel just tells the TEE what size I want and the TEE will return a
"secure
Create a new MediaTek CMA heap from the CMA reserved buffer.
In this heap, 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
On 03/01/2024 15:17, chenguanxi11...@163.com wrote:
From: Chen Haonan
dev_err_probe() can check if the error code is -EPROBE_DEFER
and can return the error code, replacing dev_err() with it
simplifies the code.
Signed-off-by: Chen Haonan
---
drivers/gpu/drm/panel/panel-samsung-s6d16d0.c |
On Wed, Jan 10, 2024 at 08:11:55PM -0800, Randy Dunlap wrote:
> Fix spelling mistakes as reported by codespell.
>
> Signed-off-by: Randy Dunlap
> Cc: Sumit Semwal
> Cc: linux-me...@vger.kernel.org
> Cc: dri-devel@lists.freedesktop.org
> Cc: Christian König
> Cc: linaro-mm-...@lists.linaro.org
On Sun, Dec 24, 2023 at 02:29:24AM +0800, Jason-JH.Lin wrote:
> Add secure buffer control flow to mtk_drm_gem.
>
> When user space takes DRM_MTK_GEM_CREATE_ENCRYPTED flag and size
> to create a mtk_drm_gem object, mtk_drm_gem will find a matched size
> dma buffer from secure dma-heap and bind it
On Thu Jan 11, 2024 at 8:05 PM CET, Linus Walleij wrote:
> On Thu, Jan 11, 2024 at 4:28 PM Luca Weiss wrote:
>
> > In some internal documentation it says "LCD Driver IC" "HX83112A" and I
> > don't see any reference to Truly 5P65 anywhere.
>
> In the Android directory I pointed to I see this file:
nikula%40intel.com
> patch subject: [PATCH 3/6] drm/amdgpu: prefer snprintf over sprintf
> config: sparc64-allmodconfig
> (https://download.01.org/0day-ci/archive/20240112/202401121126.i9vgrvmb-...@intel.com/config)
> compiler: sparc64-linux-gcc (GCC) 13.2.0
> reproduce (this is
Hi Andrew,
Le jeudi 11 janvier 2024 à 11:30 -0600, Andrew Davis a écrit :
> On 1/11/24 3:20 AM, Paul Cercueil wrote:
> > Hi Andrew,
> >
> > Le lundi 08 janvier 2024 à 15:12 -0600, Andrew Davis a écrit :
> > > On 12/19/23 11:50 AM, Paul Cercueil wrote:
> > > > [V4 was: "iio: Add buffer write()
Try to fill up VRAM as well by setting the busy flag on GTT allocations.
This fixes the issue that when VRAM was evacuated for suspend it's never
filled up again unless the application is restarted.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 6 ++
1
Previously we would never try to move a BO into the preferred placements
when it ever landed in a busy placement since those were considered
compatible.
Rework the whole handling and finally unify the idle and busy handling.
ttm_bo_validate() is now responsible to try idle placement first and
On 12/01/2024 10:00, Luca Weiss wrote:
On Thu Jan 11, 2024 at 8:05 PM CET, Linus Walleij wrote:
On Thu, Jan 11, 2024 at 4:28 PM Luca Weiss wrote:
In some internal documentation it says "LCD Driver IC" "HX83112A" and I
don't see any reference to Truly 5P65 anywhere.
In the Android directory
Hi,
On Wed, 10 Jan 2024 09:22:45 +0100, Alexander Stein wrote:
> At least the pixelclock has a range which can vary. Convert fixed mode
> into display timings so they can be overwritten in DT if necessary.
>
>
Thanks, Applied to https://anongit.freedesktop.org/git/drm/drm-misc.git
Hi,
On Fri, 05 Jan 2024 07:53:00 +0100, Artur Weber wrote:
> Two small one-line patches to address a mixup in the Samsung S6D7AA0
> panel driver and the Samsung Galaxy Tab 3 8.0 board it was initially
> added for.
>
>
Thanks, Applied to https://anongit.freedesktop.org/git/drm/drm-misc.git
Hi,
On Mon, 08 Jan 2024 15:29:00 +0530, Ritesh Kumar wrote:
> Add support for the 1080x2408 Novatek NT36672E LCD DSI mode panel
> found on the Qualcomm QCM6490 MTP board.
>
> The driver will come with the uncompressed video mode support.
>
Thanks, Applied to
On Fri, Jan 12, 2024 at 05:20:11PM +0800, Yong Wu wrote:
> Add the dma_ops for this restricted heap. For restricted buffer,
> cache_ops/mmap are not allowed, thus return EPERM for them.
>
> Signed-off-by: Yong Wu
> ---
> drivers/dma-buf/heaps/restricted_heap.c | 103
>
Seems to be unused.
Signed-off-by: Christian König
---
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h| 1 -
drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c | 28 --
2 files changed, 29 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
Only convert it to ENOMEM in ttm_bo_validate.
This allows ttm_bo_validate to distinct between an out of memory
situation and just out of space in a placement domain.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff
From: Somalapuram Amaranath
Instead of a list of separate busy placement add flags which indicate
that a placement should only be used when there is room or if we need to
evict.
v2: add missing TTM_PL_FLAG_IDLE for i915
v3: fix auto build test ERROR on drm-tip/drm-tip
v4: fix some typos pointed
Hi guys,
same as the last time. Things I've changed:
Implemented the requirements from Zack to correctly fill in the busy
placements for VMWGFX.
Renamed the placement flags to desired and fallback as suggested by
Michel.
Rebased on drm-tip instead of drm-misc-next and fixed XE as well.
Please
On Thu, Jan 04, 2024 at 05:00:46PM +0100, Jocelyn Falempe wrote:
> +/**
> + * drm_panic_init() - Initialize drm-panic subsystem
> + *
> + * register the panic notifier
> + */
> +void drm_panic_init(void)
> +{
> + atomic_notifier_chain_register(_notifier_list,
> +
Hi Linus,
please pull the fbdev changes for kernel 6.8-rc1.
Three fbdev drivers (~8500 lines of code) will be dropped:
The Carillo Ranch fbdev driver is for an Intel product which was never shipped,
and for the intelfb and the amba-clcd drivers the drm drivers can be used
instead.
The other
After commit e6c0de5f4450 ("drm/msm/dpu: try multirect based on mdp clock
limits")
merged, 120Hz is working on xiaomi,elish panels, so feature it.
Signed-off-by: Jianhua Lu
---
drivers/gpu/drm/panel/panel-novatek-nt36523.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
Hi Jani,
On Mi, 2024-01-10 at 19:39 +0200, Jani Nikula wrote:
> This will trade the W=1 warning -Wformat-overflow to
> -Wformat-truncation. This lets us enable -Wformat-overflow subsystem
> wide.
>
> Cc: Philipp Zabel
> Signed-off-by: Jani Nikula
Reviewed-by: Philipp Zabel
regards
Philipp
Am 12.01.24 um 14:05 schrieb Daniel Vetter:
On Wed, Jan 10, 2024 at 08:11:55PM -0800, Randy Dunlap wrote:
Fix spelling mistakes as reported by codespell.
Signed-off-by: Randy Dunlap
Cc: Sumit Semwal
Cc: linux-me...@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org
Cc: Christian König
Cc:
Hi Dave,
On Thu, Dec 14, 2023 at 02:43:37PM +, Dave Stevenson wrote:
> On Thu, 7 Dec 2023 at 15:50, Maxime Ripard wrote:
> >
> > The i915 driver has a property to force the RGB range of an HDMI output.
> > The vc4 driver then implemented the same property with the same
> > semantics. KWin
On Fri, Jan 12, 2024 at 3:42 AM Vignesh Raman
wrote:
>
> Hi Rob,
>
>
> On 09/01/24 01:20, Rob Clark wrote:
> > From: Rob Clark
> >
> > The msm tests should skip on non-msm hw, so I think it should be safe to
> > enable everywhere.
> >
> > Signed-off-by: Rob Clark
> > ---
> >
Hej,
debug dma code is not happy with virtio gpu (arm64 VM):
[ 305.881733] [ cut here ]
[ 305.883117] DMA-API: virtio-pci :07:00.0: mapping sg segment longer than
device claims to support [len=262144] [max=65536]
[ 305.885976] WARNING: CPU: 8 PID: 2002 at
On 1/12/2024 6:00 AM, Jianhua Lu wrote:
After commit e6c0de5f4450 ("drm/msm/dpu: try multirect based on mdp clock
limits")
merged, 120Hz is working on xiaomi,elish panels, so feature it.
Signed-off-by: Jianhua Lu
Reviewed-by: Jessica Zhang
---
On Thu, 2024-01-04 at 22:16 +0200, Jani Nikula wrote:
> hdmi-codec.h does not appear to directly need drm/drm_edid.h for
> anything. Remove it.
>
> There are some files that get drm/drm_edid.h by proxy; include it
> where
> needed.
>
> v2-v4: Fix build (kernel test robot )
>
> Cc: Rob Clark
>
On Fri, Jan 12, 2024 at 02:44:57PM +0100, Daniel Vetter wrote:
> On Thu, Jan 04, 2024 at 05:00:50PM +0100, Jocelyn Falempe wrote:
> > Add support for the drm_panic module, which displays a user-friendly
> > message to the screen when a kernel panic occurs.
> >
> > Signed-off-by: Jocelyn Falempe
On Wed, Jan 10, 2024 at 12:39 PM Jani Nikula wrote:
>
> This will trade the W=1 warning -Wformat-overflow to
> -Wformat-truncation. This lets us enable -Wformat-overflow subsystem
> wide.
>
> Cc: Alex Deucher
> Cc: Christian König
> Cc: Pan, Xinhui
> Cc: amd-...@lists.freedesktop.org
>
Hi Maxime
On Fri, 12 Jan 2024 at 13:59, Maxime Ripard wrote:
>
> Hi Dave,
>
> On Thu, Dec 14, 2023 at 02:43:37PM +, Dave Stevenson wrote:
> > On Thu, 7 Dec 2023 at 15:50, Maxime Ripard wrote:
> > >
> > > The i915 driver has a property to force the RGB range of an HDMI output.
> > > The vc4
Prefer the parsed results for is_hdmi and has_audio in display info over
calling drm_detect_hdmi_monitor() and drm_detect_monitor_audio(),
respectively.
Conveniently, this also removes the need to use edid_blob_ptr.
Cc: Karol Herbst
Cc: Lyude Paul
Cc: Danilo Krummrich
Cc:
Prefer the parsed results for is_hdmi and has_audio in display info over
calling drm_detect_hdmi_monitor() and drm_detect_monitor_audio(),
respectively.
Cc: Alex Deucher
Cc: Christian König
Cc: Pan, Xinhui
Cc: amd-...@lists.freedesktop.org
Signed-off-by: Jani Nikula
---
amdgpu_connector_edid() copies the EDID from edid_blob_ptr as a side
effect if amdgpu_connector->edid isn't initialized. However, everywhere
that the returned EDID is used, the EDID should have been set
beforehands.
Only the drm EDID code should look at the EDID property, anyway, so stop
using
Add a helper to get the EDID property for sysfs property show. This
hides all the edid_blob_ptr usage within drm_edid.c.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_crtc_internal.h | 2 ++
drivers/gpu/drm/drm_edid.c | 33 +
Accessing the EDID via edid_blob_ptr causes chicken-and-egg
problems. Keep edid_blob_ptr as the userspace interface that should be
accessed via dedicated functions.
Signed-off-by: Jani Nikula
---
include/drm/drm_connector.h | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
radeon_connector_edid() copies the EDID from edid_blob_ptr as a side
effect if radeon_connector->edid isn't initialized. However, everywhere
that the returned EDID is used, the EDID should have been set
beforehands.
Only the drm EDID code should look at the EDID property, anyway, so stop
using
Jani Nikula (6):
drm/nouveau: convert to using is_hdmi and has_audio from display info
drm/radeon: convert to using is_hdmi and has_audio from display info
drm/radeon: remove radeon_connector_edid() and stop using
edid_blob_ptr
drm/amdgpu: remove amdgpu_connector_edid() and stop
On Thu, Jan 04, 2024 at 05:00:46PM +0100, Jocelyn Falempe wrote:
> This module displays a user friendly message when a kernel panic
> occurs. It currently doesn't contain any debug information,
> but that can be added later.
>
> v2
> * Use get_scanout_buffer() instead of the drm client API.
>
On Thu, Jan 04, 2024 at 05:00:50PM +0100, Jocelyn Falempe wrote:
> Add support for the drm_panic module, which displays a user-friendly
> message to the screen when a kernel panic occurs.
>
> Signed-off-by: Jocelyn Falempe
> ---
> drivers/gpu/drm/tiny/simpledrm.c | 15 +++
> 1 file
On Thu, Jan 04, 2024 at 05:00:44PM +0100, Jocelyn Falempe wrote:
> This introduces a new drm panic handler, which displays a message when a
> panic occurs.
> So when fbcon is disabled, you can still see a kernel panic.
>
> This is one of the missing feature, when disabling VT/fbcon in the
On 12/01/2024 15:00, Daniel Vetter wrote:
On Thu, Jan 04, 2024 at 05:00:44PM +0100, Jocelyn Falempe wrote:
This introduces a new drm panic handler, which displays a message when a panic
occurs.
So when fbcon is disabled, you can still see a kernel panic.
This is one of the missing feature,
On Tue, Jan 9, 2024 at 5:26 PM Nathan Chancellor wrote:
>
> This series updates all instances of LLVM Phabricator and Bugzilla links
> to point to GitHub commits directly and LLVM's Bugzilla to GitHub issue
> shortlinks respectively.
>
> I split up the Phabricator patch into BPF selftests and the
On Thu, Jan 04, 2024 at 05:00:49PM +0100, Jocelyn Falempe wrote:
> This was initialy done for imx6, but should work on most drivers
> using drm_fb_dma_helper.
>
> Signed-off-by: Jocelyn Falempe
> ---
> drivers/gpu/drm/drm_fb_dma_helper.c | 55 +
>
On Fri, Jan 12, 2024 at 02:41:53PM +0100, Daniel Vetter wrote:
> > + fb = plane->state->fb;
> > + /* Only support linear modifier */
> > + if (fb->modifier != DRM_FORMAT_MOD_LINEAR)
> > + continue;
> > +
> > + /* Check if color format is
The aca_bank_hwip_is_matched() function is type bool. This error path
return -EINVAL which is cast to true, but it should return false
instead.
Fixes: 22a4fa4709e3 ("drm/amdgpu: implement RAS ACA driver framework")
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/amd/amdgpu/amdgpu_aca.c | 2 +-
This code was shuffled around but the return wasn't updated. It should
return "ret" instead of "ctrl".
Fixes: 4ae3a20102b2 ("nouveau/gsp: don't free ctrl messages on errors")
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/nouveau/nvkm/engine/disp/r535.c | 2 +-
1 file changed, 1
On Fri, Jan 12, 2024 at 1:21 AM Yong Wu wrote:
>
> Add "struct restricted_heap_ops". For the restricted memory, totally there
> are two steps:
> a) memory_alloc: Allocate the buffer in kernel;
> b) memory_restrict: Restrict/Protect/Secure that buffer.
> The memory_alloc is mandatory while
dw-mipi-dsi based drivers such as dw-mipi-dsi-rockchip or dw_mipi_dsi-stm
depend on dw_mipi_dsi_probe() to initialize the dw_mipi_dsi driver
structure (dmd pointer). This structure is only initialized once
dw_mipi_dsi_probe() returns, creating the link between the locally created
structure and the
When waiting for a syncobj timeline point whose fence has not yet been
submitted with the WAIT_FOR_SUBMIT flag, a callback is registered using
drm_syncobj_fence_add_wait and the thread is put to sleep until the
timeout expires. If the fence is submitted before then,
drm_syncobj_add_point will wake
SVGA requires surfaces to fit within graphics memory (max_mob_pages) which
means that modes with a final buffer size that would exceed graphics memory
must be pruned otherwise creation will fail.
Additionally, device commands which use multiple graphics resources must
have all their resources fit
The pull request you sent on Thu, 11 Jan 2024 05:49:21 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2024-01-10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/cf65598d5909acf5e7b7dc9e21786e386356bc81
Thank you!
--
Deet-doot-dot, I am a bot.
On Fri, Jan 12, 2024 at 7:57 AM Rob Clark wrote:
>
> On Fri, Jan 12, 2024 at 3:42 AM Vignesh Raman
> wrote:
> >
> > Hi Rob,
> >
> >
> > On 09/01/24 01:20, Rob Clark wrote:
> > > From: Rob Clark
> > >
> > > The msm tests should skip on non-msm hw, so I think it should be safe to
> > > enable
Hi,
I just comment on this example, but it applies almost the same for all other
.dtsi changes.
> Am 08.01.2024 um 19:32 schrieb Andrew Davis :
>
> Add SGX GPU device entry to base OMAP4 dtsi file.
>
> Signed-off-by: Andrew Davis
> ---
> arch/arm/boot/dts/ti/omap/omap4.dtsi | 9 +
> 1
On Wed, 10 Jan 2024 at 11:49, Dave Airlie wrote:
>
> Let me know if there are any issues,
Your testing is seriously lacking.
This doesn't even build. The reason seems to be that commit
b49e894c3fd8 ("drm/i915: Replace custom intel runtime_pm tracker with
ref_tracker library") changed the
Hi Dave, Sima,
Fixes for 6.8.
The following changes since commit e54478fbdad20f2c58d0a4f99d01299ed8e7fe9c:
Merge tag 'amd-drm-next-6.8-2024-01-05' of
https://gitlab.freedesktop.org/agd5f/linux into drm-next (2024-01-09 09:07:50
+1000)
are available in the Git repository at:
The pull request you sent on Fri, 12 Jan 2024 16:48:41 +0100:
> http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git
> tags/fbdev-for-6.8-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d97a78423c33f68ca6543de510a409167baed6f5
Thank you!
--
Assign device of node to bridge prior registering it. This will
make said bridge discoverable by separate crtc driver.
Signed-off-by: Anatoliy Klymenko
---
drivers/gpu/drm/xlnx/zynqmp_dp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/xlnx/zynqmp_dp.c
Patches 1/4,2/4,3/4 are minor fixes.
DPSUB requires input live video format to be configured.
Patch 4/4: The DP Subsystem requires the input live video format to be
configured. In this patch we are assuming that the CRTC's bus format is fixed
and comes from the device tree. This is a proposed
Filter out status register against interrupts' mask.
Some events are being reported via DP status register, even if
corresponding interrupts have been disabled. Avoid processing
of such events in interrupt handler context.
Signed-off-by: Anatoliy Klymenko
---
drivers/gpu/drm/xlnx/zynqmp_dp.c |
Expect external video timing in live video input mode, program
DPSUB accordingly.
Signed-off-by: Anatoliy Klymenko
---
drivers/gpu/drm/xlnx/zynqmp_disp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xlnx/zynqmp_disp.c
b/drivers/gpu/drm/xlnx/zynqmp_disp.c
Live video input format is expected to be set as
"bus-format" property in connected remote endpoint.
Program live video input format DPSUB registers.
Set display layer mode in layer creation context.
Signed-off-by: Anatoliy Klymenko
---
drivers/gpu/drm/xlnx/zynqmp_disp.c | 109
On Fri, Jan 12, 2024 at 4:13 PM Jeffrey Kardatzke wrote:
> On Fri, Jan 12, 2024 at 3:51 PM John Stultz wrote:
> >
> > On Fri, Jan 12, 2024 at 3:27 PM Jeffrey Kardatzke
> > wrote:
> > > On Fri, Jan 12, 2024 at 2:52 PM John Stultz wrote:
> > > > I know part of this effort here is to start to
On Fri, Jan 12, 2024 at 2:52 PM John Stultz wrote:
>
> On Fri, Jan 12, 2024 at 1:21 AM Yong Wu wrote:
> >
> > Add "struct restricted_heap_ops". For the restricted memory, totally there
> > are two steps:
> > a) memory_alloc: Allocate the buffer in kernel;
> > b) memory_restrict:
On Fri, Jan 12, 2024 at 3:27 PM Jeffrey Kardatzke wrote:
> On Fri, Jan 12, 2024 at 2:52 PM John Stultz wrote:
> > On Fri, Jan 12, 2024 at 1:21 AM Yong Wu wrote:
> > > diff --git a/drivers/dma-buf/heaps/restricted_heap.h
> > > b/drivers/dma-buf/heaps/restricted_heap.h
> > > index
On Fri, Jan 12, 2024 at 3:51 PM John Stultz wrote:
>
> On Fri, Jan 12, 2024 at 3:27 PM Jeffrey Kardatzke
> wrote:
> > On Fri, Jan 12, 2024 at 2:52 PM John Stultz wrote:
> > > On Fri, Jan 12, 2024 at 1:21 AM Yong Wu wrote:
> > > > diff --git a/drivers/dma-buf/heaps/restricted_heap.h
> > > >
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 8d04a7e2ee3fd6aabb8096b00c64db0d735bc874 Add linux-next specific
files for 20240112
Error/Warning: (recently discovered and may have been fixed)
WARNING: modpost: vmlinux: section mismatch
This is mainly a preparatory patch to use memfd_pin_folios() API
for pinning folios. Using folios instead of pages makes sense as
the udmabuf driver needs to handle both shmem and hugetlb cases.
However, the function vmap_udmabuf() still needs a list of pages;
so, we collect all the head pages
Currently, some drivers (e.g, Udmabuf) that want to longterm-pin
the pages/folios associated with a memfd, do so by simply taking a
reference on them. This is not desirable because the pages/folios
may reside in Movable zone or CMA block.
Therefore, having drivers use memfd_pin_folios() API
This helper is the folio equivalent of check_and_migrate_movable_pages().
Therefore, all the rules that apply to check_and_migrate_movable_pages()
also apply to this one as well. Currently, this helper is only used by
memfd_pin_folios().
This patch also includes changes to rename and convert the
Since the memfd pages associated with a udmabuf may be migrated
as part of udmabuf create, we need to verify the data coherency
after successful migration. The new tests added in this patch try
to do just that using 4k sized pages and also 2 MB sized huge
pages for the memfd.
Successful
1 - 100 of 105 matches
Mail list logo
