Hello Thomas Hellström,
Commit bb8aa27eff6f ("drm/ttm, drm_xe, Implement
ttm_lru_walk_for_evict() using the guarded LRU iteration") from Jun
23, 2025 (linux-next), leads to the following (unpublished) Smatch
static checker warning:
drivers/gpu/drm/ttm/ttm_bo_util.c:991 __ttm_bo_lru_cursor
DRM checks EDID block count against allocated size in drm_edid_valid
function. We have to allocate the right EDID size instead of the max
size to prevent the EDID to be reported as invalid.
Fixes: 7c585f9a71aa ("drm/bridge: anx7625: use struct drm_edid more")
Signed-off-by: Loic Poulain
---
driv
Currently, an interrupt can be triggered during a GPU reset, which can
lead to GPU hangs and NULL pointer dereference in an interrupt context
as shown in the following trace:
[ 314.035040] Unable to handle kernel NULL pointer dereference at virtual
address 00c0
[ 314.043822] Mem a
On Sat, Jun 28, 2025 at 7:59 AM Abdun Nihaal wrote:
>
> The error handling in fbtft_framebuffer_alloc() mixes managed allocation
> and plain allocation, and performs error handling in an order different
> from the order in fbtft_framebuffer_release().
>
> Fix them by moving vmem allocation closer
Hi Daniel,
On 27/06/25 19:34, Daniel Almeida wrote:
[...]
diff --git a/drivers/gpu/drm/tyr/driver.rs b/drivers/gpu/drm/tyr/driver.rs
new file mode 100644
index
..2443620e10620585eae3d57978e64d2169a1b2d1
--- /dev/null
+++ b/drivers/gpu/drm/tyr/driver.rs
Em Sat, 28 Jun 2025 08:30:21 +0700
Bagas Sanjaya escreveu:
> [also Cc'ing Mauro]
>
> On Fri, Jun 27, 2025 at 05:27:18PM +0530, Kevin Paul Reddy Janagari wrote:
> > Functions drm_format_info, drm_modeset_lock, drm_ioctl_flags are not being
> > indexed in the documentation because there are struct
Make video port registers nonvolatile. As DSP_CTRL register is written
to twice due to gamma LUT enable bit which is set outside of the main
DSP_CTRL initialization within atomic_enable (for rk356x case it is also
necesarry to always disable gamma LUT before writing a new LUT) there is
a chance tha
On Fri, Jun 20, 2025 at 05:31:04PM +0800, Yongbang Shi wrote:
> From: Baihan Li
>
> Add colorbar disable operation and move hdcp opreation behind the reset
> controller operation.
Two items => two commits
You missed the 'why' part of the commit message.
>
> Fixes: 3c7623fb5bb6 ("drm/hisilicon/
On Fri, Jun 20, 2025 at 05:31:03PM +0800, Yongbang Shi wrote:
> From: Baihan Li
>
> When using command rmmod and insmod, there is no showing in second time
> insmoding. Because DP controller won't send HPD signals, if connection
> doesn't change or controller isn't reset. So add reset before unre
On Fri, Jun 20, 2025 at 05:31:02PM +0800, Yongbang Shi wrote:
> From: Baihan Li
>
> Our chip support KVM over IP feature, so hibmc driver need to support
> displaying without any connectors plugged in. Deleting the detect_ctx()
> of VGA to make it connected when no connector is detected.
I think
On Fri, Jun 20, 2025 at 05:31:01PM +0800, Yongbang Shi wrote:
> From: Baihan Li
>
> If VGA and DP connected together, there will be only one can get crtc.
> Add encoder possible_clones to support two connectors enable.
>
> Fixes: 0ab6ea261c1f ("drm/hisilicon/hibmc: add dp module in hibmc")
> Fix
On Fri, Jun 20, 2025 at 05:31:00PM +0800, Yongbang Shi wrote:
> From: Baihan Li
>
> If DP is connected, add mode check and BW check in mode_valid_ctx() to
> ensure DP's cfg is usable.
>
> Fixes: f9698f802e50 ("drm/hisilicon/hibmc: Restructuring the header dp_reg.h")
> Signed-off-by: Baihan Li
>
On Fri, Jun 20, 2025 at 05:30:58PM +0800, Yongbang Shi wrote:
> From: Baihan Li
>
> When hibmc loaded failed, the driver use hibmc_unload to free the
> resource, but the mutexes in mode.config are not init, which will
> access an NULL pointer. Just change goto statement to return, because
> hibnc
On Fri, Jun 20, 2025 at 05:30:57PM +0800, Yongbang Shi wrote:
> From: Baihan Li
>
> The local variable is passed in request_irq (), and there will be use
> after free problem, which will make request_irq failed. Using the global
> irq name instead of it to fix.
>
> Fixes: b11bc1ae4658 ("drm/hisi
On Fri, Jun 20, 2025 at 05:30:55PM +0800, Yongbang Shi wrote:
> From: Baihan Li
>
> Currently the driver missed to clean the i2c adapter when vdac init failed.
> It may cause resource leak.
>
> Fixes: a0d078d06e516 ("drm/hisilicon: Features to support reading resolutions
> from EDID")
> Signed-
On 2025-06-25 11:34, Robin Murphy wrote:
On 2025-06-25 9:42 am, Marek Szyprowski wrote:
On 25.06.2025 09:39, Kaustabh Chakraborty wrote:
On 2025-06-24 17:12, Robin Murphy wrote:
On 2025-06-18 3:02 pm, Kaustabh Chakraborty wrote:
Since bcb81ac6ae3c (iommu: Get DT/ACPI parsing into the proper
p
g
(https://download.01.org/0day-ci/archive/20250628/202506282240.aqa0j5m3-...@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project
e04c938cc08a90ae60440ce22d072ebc69d67ee8)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20250628/2
On Sat, Jun 28, 2025 at 3:06 PM Daniel Almeida
wrote:
>
> The branch I shared is drm-misc-next plus a few dependencies, i.e.: 10 commits
> total if I counted it correctly - all of which have been sent to the list
> already and most of which have seen a quite a few iterations. I should have
> expli
The drm_test_framebuffer_free() test creates a framebuffer on the stack
without properly initializing the filp_head list, causing the following
warning when drm_framebuffer_free() checks it:
[ 144.996969] drm-kunit-mock-device
drm_test_framebuffer_free.drm-kunit-mock-device: [drm]
drm_WARN_ON(\
On 6/28/25 5:02 AM, Dmitry Baryshkov wrote:
> Handle two cases for Adreno 7xx:
> - Adreno 702 follows A610 and A619 example and has clocks in the GPU
> node.
> - Newer 7xx GPUs use a different pattern for the compatibles and did not
> match currently.
>
> Signed-off-by: Dmitry Baryshkov
> ---
Hi,
On Sat, 28 Jun 2025 10:05:11 -0300
Daniel Almeida wrote:
> Anyway, I thought that having a branch would be more tidy than listing them,
> as
> the branch shows in what order they're applied and etc. For example, the patch
> for read_poll_timeout was cherry-picked from Fujita's v12 series, a
On 6/25/25 8:46 PM, Rob Clark wrote:
Conversion to DRM GPU VA Manager[1], and adding support for Vulkan Sparse
Memory[2] in the form of:
1. A new VM_BIND submitqueue type for executing VM MSM_SUBMIT_BO_OP_MAP/
MAP_NULL/UNMAP commands
2. A new VM_BIND ioctl to allow submitting batches of one
Hi Miguel,
> On 28 Jun 2025, at 06:44, Miguel Ojeda
> wrote:
>
> Hi Daniel,
>
> Some procedural notes and general comments, and please note that some
> may apply several times.
>
> On Sat, Jun 28, 2025 at 12:35 AM Daniel Almeida
> wrote:
>>
>> Signed-off-by: Rob Herring
>>
>> Signed-off-b
On Fri, Jun 27, 2025 at 04:03:16PM +0530, Ling Xu wrote:
> Add "gdsp" as the new supported label for GDSP fastrpc domain.
>
> Signed-off-by: Ling Xu
> ---
> Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
NAK, nothing improved. You got comme
On Wed, Jun 25, 2025 at 10:30:07PM +0530, Badal Nilawar wrote:
> +/**
> + * struct late_bind_component_ops - ops for Late Binding services.
> + * @owner: Module providing the ops
> + * @push_config: Sends a config to FW.
> + */
> +struct late_bind_component_ops {
> + struct module *owner;
I do
On Wed, Jun 25, 2025 at 10:30:07PM +0530, Badal Nilawar wrote:
> --- /dev/null
> +++ b/drivers/misc/mei/late_bind/mei_late_bind.c
> @@ -0,0 +1,281 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright (C) 2025 Intel Corporation
> + */
> +#include
> +#include
> +#include
> +#include
>
On 27/06/2025 13:34, Thomas Zimmermann wrote:
> Hi
>
> Am 27.06.25 um 10:08 schrieb Krzysztof Kozlowski:
>> On Mon, Jun 23, 2025 at 08:44:45AM +0200, Luca Weiss wrote:
>>> Document the interconnects property which is a list of interconnect
>>> paths that is used by the framebuffer and therefore ne
On 27/06/2025 11:48, Luca Weiss wrote:
> Hi Krzysztof,
>
> On Fri Jun 27, 2025 at 10:08 AM CEST, Krzysztof Kozlowski wrote:
>> On Mon, Jun 23, 2025 at 08:44:45AM +0200, Luca Weiss wrote:
>>> Document the interconnects property which is a list of interconnect
>>> paths that is used by the framebuff
Hi Louis,
On 6/27/25 19:45, Louis Chauvet wrote:
Some YUV format uses 16 bit values, so change the helper function for
conversion to support those new formats.
Signed-off-by: Louis Chauvet
Reviewed-by: Maíra Canal
Best Regards,
- Maíra
---
drivers/gpu/drm/vkms/tests/vkms_format_test.c
Hi Daniel,
Some procedural notes and general comments, and please note that some
may apply several times.
On Sat, Jun 28, 2025 at 12:35 AM Daniel Almeida
wrote:
>
> Signed-off-by: Rob Herring
>
> Signed-off-by: Daniel Almeida
No newline.
> [2]: https://gitlab.freedesktop.org/panfrost/linux/-
On Sat, Jun 28, 2025 at 2:13 AM Daniel Almeida
wrote:
>
> Also, for some reason the Clippy lint did not save me this time.
Hmm... it should -- I tried to build it and Clippy reports it. There
is also another warning too [1].
I see the compiler reporting [2] too.
By the way, do you need to depen
Javier Martinez Canillas writes:
> The commit d391c5827107 ("drivers/firmware: move x86 Generic System
> Framebuffers support") moved the sysfb*.c source files from arch/x86
> to drivers/firmware, because the logic wasn't x86 specific and could
> be used by other architectures.
>
> But the driver
Rob Clark writes:
> On Fri, Jun 27, 2025 at 12:10 PM Javier Martinez Canillas
> wrote:
>>
>> Laurent Pinchart writes:
>>
>> > On Fri, Jun 27, 2025 at 09:39:37AM -0700, Rob Clark wrote:
>> >> On Mon, Feb 26, 2024 at 5:43 AM Jacopo Mondi wrote:
>> >> >
>> >> > Add FourCC definitions for the 48-bi
33 matches
Mail list logo
