On Fri, Aug 16, 2024 at 09:59:31AM GMT, Aravind Iddamsetty wrote:
On 14/08/24 19:54, Lucas De Marchi wrote:
On Wed, Aug 14, 2024 at 12:16:41PM GMT, Aravind Iddamsetty wrote:
i see that this is even called from xe_guc_exec_queue_lr_cleanup which is for
long running queue
from various call path
On 14/08/24 19:54, Lucas De Marchi wrote:
> On Wed, Aug 14, 2024 at 12:16:41PM GMT, Aravind Iddamsetty wrote:
> i see that this is even called from xe_guc_exec_queue_lr_cleanup which is
> for long running queue
> from various call paths need to check in what scenarios those happen.
>
Hi Linus,
Weekly drm fixes, mostly amdgpu and xe. The larger amdgpu fix is for a
new IP block introduced in rc1, so should be fine. The xe fixes
contain some missed fixes from the end of the previous round along
with some fixes which required precursor changes, but otherwise
everything seems fine,
Hi, Jason:
Jason-JH.Lin 於 2024年7月3日 週三 下午6:33寫道：
>
> In mtk_crtc_ddp_config(), mtk_crtc will use some configuration flags to
> generate instructions to cmdq_handle, such as:
> state->pending_config
> mtk_crtc->pending_planes
> plane_state->pending.config
> mtk_crtc->pending_async_planes
>
Ping ...
thanks
xiaolei
From: Wang, Xiaolei
Sent: Wednesday, August 7, 2024 9:33 AM
To: l.st...@pengutronix.de ;
linux+etna...@armlinux.org.uk ;
christian.gmei...@gmail.com ; airl...@gmail.com
; dan...@ffwll.ch
Cc: etna...@lists.freedesktop.org ;
dri-devel@lis
On Fri, 16 Aug 2024 at 10:53, Danilo Krummrich wrote:
>
> On Fri, Aug 16, 2024 at 06:19:23AM +1000, Dave Airlie wrote:
> > From: Dave Airlie
> >
> > Currently, enabling SG_DEBUG in the kernel will cause nouveau to hit a
> > BUG() on startup, when the iommu is enabled:
> >
> > kernel BUG at includ
On Wed, 14 Aug 2024 17:32:53 +0100 Pavel Begunkov wrote:
> > This is where I get a bit confused. Jakub did mention that it is
> > desirable for core to verify that the driver did the right thing,
> > instead of trusting that a driver did the right thing without
> > verifying. Relying on a flag from
On Tue, 13 Aug 2024 21:13:08 + Mina Almasry wrote:
> +EXPORT_SYMBOL(page_pool_mem_providers);
not sure if this export is needed, but it doesn't appear to be needed
by this patch?
On Fri, Aug 16, 2024 at 06:19:23AM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> Currently, enabling SG_DEBUG in the kernel will cause nouveau to hit a
> BUG() on startup, when the iommu is enabled:
>
> kernel BUG at include/linux/scatterlist.h:187!
> invalid opcode: [#1] PREEMPT SMP NO
On Tue, 13 Aug 2024 21:13:05 + Mina Almasry wrote:
> + if (NL_REQ_ATTR_CHECK(info->extack, attr, tb,
> + NETDEV_A_QUEUE_ID)) {
> + err = -EINVAL;
> + goto err_unlock;
> + }
> +
> + if (
On Tue, 13 Aug 2024 21:13:05 + Mina Almasry wrote:
> +int dev_get_max_mp_channel(const struct net_device *dev)
> +{
> + int i, max = -1;
I presume the bug from yesterday is self evident once reported? :)
> + ASSERT_RTNL();
> +
> + for (i = 0; i < dev->real_num_rx_queues; i++)
> +
On 8/13/24 19:33, Zack Rusin wrote:
> On Mon, Aug 12, 2024 at 3:16 PM Maaz Mombasawala
> wrote:
>>
>> This series introduces basic support for userspace managed surfaces. The
>> lifetime and id's of these surfaces is managed by userspace submitted
>> commands instead of relying on the kernel to ma
LGTM.
Reviewed-by: Maaz Mombasawala
--
Maaz Mombasawala
On Sun, 04 Aug 2024 08:40:04 +0300, Dmitry Baryshkov wrote:
> A set of fixes that target stability of the SM8350 platform.
>
>
Applied, thanks!
[09/11] arm64: dts: qcom: sm8350: add MDSS registers interconnect
commit: 5e1cf9f1f397a3d24dc6b06eda069be954504a16
[10/11] arm64: dts: qcom:
On Fri, 16 Aug 2024 at 06:45, Timur Tabi wrote:
>
> On Fri, 2024-08-16 at 06:19 +1000, Dave Airlie wrote:
> > Fix this by using the non-coherent allocator instead, I think there
> > might be a better answer to this, but it involve ripping up some of
> > APIs using sg lists.
>
> Thanks for fixing t
On Fri, 2024-08-16 at 06:19 +1000, Dave Airlie wrote:
> Fix this by using the non-coherent allocator instead, I think there
> might be a better answer to this, but it involve ripping up some of
> APIs using sg lists.
Thanks for fixing this, but what is the relationshio between non-coherent
DMA and
On Sun, 04 Aug 2024 08:40:04 +0300, Dmitry Baryshkov wrote:
> A set of fixes that target stability of the SM8350 platform.
>
>
Applied, thanks!
[11/11] arm64: defconfig: build CONFIG_REGULATOR_QCOM_REFGEN as module
commit: 115c14ee54aae1d61d2405f9b31f67c1e8947f4e
Best regards,
--
Bj
On Mon, 05 Aug 2024 19:08:01 +0200, Bartosz Golaszewski wrote:
> Add DT bindings, relevant DT defines, DTS nodes and driver changes
> required to enable the remoteprocs on sa8775p.
>
> To: Bjorn Andersson
> To: Mathieu Poirier
> To: Rob Herring
> To: Krzysztof Kozlowski
> To: Conor Dooley
>
From: Dave Airlie
Currently, enabling SG_DEBUG in the kernel will cause nouveau to hit a
BUG() on startup, when the iommu is enabled:
kernel BUG at include/linux/scatterlist.h:187!
invalid opcode: [#1] PREEMPT SMP NOPTI
CPU: 7 PID: 930 Comm: (udev-worker) Not tainted 6.9.0-rc3Lyude-Test+ #3
Hi,
On Wed, Aug 14, 2024 at 2:48 PM Stefan Wahren wrote:
>
> >> You're saying that your
> >> registers get saved _unless_ the power domain gets turned off, right?
> On BCM2835 there is no need to store the registers because there is no
> power management supported by USB core except of the power
On Mon, 05 Aug 2024 19:08:01 +0200, Bartosz Golaszewski wrote:
> Add DT bindings, relevant DT defines, DTS nodes and driver changes
> required to enable the remoteprocs on sa8775p.
>
> To: Bjorn Andersson
> To: Mathieu Poirier
> To: Rob Herring
> To: Krzysztof Kozlowski
> To: Conor Dooley
>
On Wed, Aug 14, 2024 at 07:59:47PM +0200, Andi Shyti wrote:
> The cast from "long" to "unsigned long" is unnecessary. Remove
> it.
I don't believe we can be that bold in this statement.
Some static analyzer tools might not agree and tell that
if the start or end are negative values we could have
u
Sparse reported following warning:
'''
drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn314/dcn314_fpu.c:36:30:
warning: symbol 'dcn3_14_ip' was not declared. Should it be static?
'''
Since the symbol dcn3_14_ip is not exported,it is declared as static.
Signed-off-by: Dipendra Khadka
---
drive
On Thu, Aug 15, 2024 at 1:48 PM Christian Heusel wrote:
>
> Hello Zack,
>
> the user rdkehn (in CC) on the Arch Linux Forums reports that after
> updating to the 6.10.4 stable kernel inside of their VM Workstation the
> driver crashes with the error attached below. This error is also present
> on
sparse reportef following warnings:
'''
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_pmo/dml2_pmo_dcn4.c:614:53:
warning: Using plain integer as NULL pointer
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_pmo/dml2_pmo_dcn4.c:615:58:
warning: Using plain integer as N
Hello Zack,
the user rdkehn (in CC) on the Arch Linux Forums reports that after
updating to the 6.10.4 stable kernel inside of their VM Workstation the
driver crashes with the error attached below. This error is also present
on the latest mainline release 6.11-rc3.
We have bisected the issue toge
Am Donnerstag, 15. August 2024, 19:26:54 CEST schrieb Cristian Ciocaltea:
> On 8/15/24 5:21 PM, Heiko Stübner wrote:
> > Am Donnerstag, 8. August 2024, 13:58:02 CEST schrieb Cristian Ciocaltea:
> >> Move rockchip_drm_platform_driver unregistration after its sub-drivers,
> >> which ensures all drive
On Sat, 15 Jun 2024 17:03:51 +, Jonas Karlman wrote:
> This prepares and enable use of HDMI2.0 modes, e.g. 4K@60Hz, on RK3228,
> RK3328, RK3399 and RK356x.
>
> Patch 1-3 fixes some issues to help support use of high-resolution modes.
>
> Patch 4 fixes reading of EDID on RK3328 when using a fo
On 8/15/24 5:21 PM, Heiko Stübner wrote:
> Am Donnerstag, 8. August 2024, 13:58:02 CEST schrieb Cristian Ciocaltea:
>> Move rockchip_drm_platform_driver unregistration after its sub-drivers,
>> which ensures all drivers are unregistered in the reverse order used
>> when they were registered.
>
> a
On Wed, Aug 14, 2024 at 01:00:35PM +0300, Jani Nikula wrote:
> Use the mem_is_zero() helper where possible.
>
> Conversion done using cocci:
>
> | @@
> | expression PTR;
> | expression SIZE;
> | @@
> |
> | <...
> | (
> | - memchr_inv(PTR, 0, SIZE) == NULL
> | + mem_is_zero(PTR, SIZE)
> | |
> |
On Wed, Aug 14, 2024 at 01:00:34PM +0300, Jani Nikula wrote:
> Almost two thirds of the memchr_inv() usages check if the memory area is
> all zeros, with no interest in where in the buffer the first non-zero
> byte is located. Checking for !memchr_inv(s, 0, n) is also not very
> intuitive or discov
Make sure that for external buffers mapping goes through the dma_buf
interface instead of trying to access pages directly.
External buffers might not provide direct access to readable/writable
pages so to make sure the bo's created from external dma_bufs can be
read dma_buf interface has to be use
The kms paths keep a persistent map active to read and compare the cursor
buffer. These maps can race with each other in simple scenario where:
a) buffer "a" mapped for update
b) buffer "a" mapped for compare
c) do the compare
d) unmap "a" for compare
e) update the cursor
f) unmap "a" for update
At
Permanently set the connector status to 'connected'. Return BMC modes
for connector if no display is attached to the physical DP connector.
Otherwise use EDID modes as before.
If the status of the physical connector changes, the driver still
generates a hotplug event. DRM clients will then reconfi
Permanently set the connector status to 'connected'. Return BMC modes
for connector if no display is attached to the physical DP connector.
Otherwise use EDID modes as before.
If the status of the physical connector changes, the driver still
generates a hotplug event. DRM clients will then reconfi
Convert DP501 support to struct drm_edid and its helpers. Simplifies
and modernizes the EDID handling.
The driver reads 4 bytes at once, but the overall read length is now
variable. Therefore update the EDID read loop to never return more than
the requested bytes.
v2:
- fix reading EDID data
Sig
Remove the CRTC handling in the ASTDP detect_ctx helper and enable
power while the detecting the display. Unconditionally wait a few
milliseconds after switching power. Simplifies the code and makes it
more robust.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ast/ast_dp.c | 19 ++
Permanently set the connector status to 'connected'. Return BMC modes
for connector if no display is attached to the physical DP connector.
Otherwise use EDID modes as before.
If the status of the physical connector changes, the driver still
generates a hotplug event. DRM clients will then reconfi
Add transparent BMC support to all outputs. If the user disconnects
the physical display, each output will now return display modes for
the BMC. Makes the BMC connector obsolete, so remove it.
The benefit of the new approach is that is works with any userspace.
Most userspace compositors have prob
Move the modesetting code for the various transmitter chips into
their own source files before adding BMC support. No functional
changes.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Jocelyn Falempe
---
drivers/gpu/drm/ast/Makefile | 4 +-
drivers/gpu/drm/ast/ast_dp.c | 214 +
Ast's BMC connector tracks the status of an underlying physical
connector and updates the BMC status accordingly. This functionality
works around GNOME's settings app, which cannot handle multiple
outputs on the same CRTC.
The workaround is now obsolete as all code for physical outputs
handle BMC
The modeset mutex protects EDID retrival from concurrent modeset
operations. Acquire the lock in ast_astdp_read_edid(). Prepares the
code for conversion to struct drm_edid.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Jocelyn Falempe
---
drivers/gpu/drm/ast/ast_dp.c | 24 ++
Permanently set the connector status to 'connected'. Return BMC modes
for connector if no display is attached to the physical DP connector.
Otherwise use EDID modes as before.
If the status of the physical connector changes, the driver still
generates a hotplug event. DRM clients will then reconfi
Convert ASTDP support to struct drm_edid and its helpers. Simplifies
and modernizes the EDID handling.
The driver reads 4 bytes at once, but the overall read length is now
variable. Therefore update the EDID read loop to never return more than
the requested bytes.
The device does not seem to supp
Add struct ast_connector to track a connector's physical status. With
the upcoming BMC support, the physical status can be different from the
reported status.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ast/ast_dp.c | 7 ++-
drivers/gpu/drm/ast/ast_dp501.c | 11 +--
dr
On 15/08/2024 10:49, Griffin Kroah-Hartman wrote:
This reverts commit bab2f5e8fd5d2f759db26b78d9db57412888f187.
Joel reported that this commit breaks userspace and stops sensors in
SDM845 from working. Also breaks other qcom SoC devices running postmarketOS.
Cc: stable
Cc: Ekansh Gupta
Cc:
5.10-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit ecde5db1598aecab54cc392282c15114f526f05f upstream.
Compute the i2c timeout in jiffies from a value in milliseconds. The
original values of 2 jiffies equals 2 milliseco
Hi Louis,
Most of the code extracted in this patch was previously introduced by
you in patches that I didn't apply yet. Therefore, I believe you could
just add the code in vkms_formats.c in the original series.
Best Regards,
- Maíra
On 8/14/24 06:08, Louis Chauvet wrote:
The vkms_format.h head
On 14/08/2024 12:21, Mary Guillemard wrote:
> Extend the uAPI with a new job requirement flag for cycle
> counters. This requirement is used by userland to indicate that a job
> requires cycle counters or system timestamp to be propagated. (for use
> with write value timestamp jobs)
>
> We cannot
On 14/08/2024 12:21, Mary Guillemard wrote:
> Expose system timestamp and frequency supported by the GPU.
>
> Mali uses an external timer as GPU system time. On ARM, this is wired to
> the generic arch timer so we wire cntfrq_el0 as device frequency.
>
> This new uAPI will be used in Mesa to impl
Hi Louis,
I'd make this patch more incremental. First, send me a patch based on
drm-misc-next with the new documentation for the things that already
exists. Then, when you add a new field, you add the documentation with
it.
On 8/14/24 05:47, Louis Chauvet wrote:
Add documentation around vkms_ou
5.4-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit ecde5db1598aecab54cc392282c15114f526f05f upstream.
Compute the i2c timeout in jiffies from a value in milliseconds. The
original values of 2 jiffies equals 2 millisecon
Am Donnerstag, 8. August 2024, 13:58:02 CEST schrieb Cristian Ciocaltea:
> Move rockchip_drm_platform_driver unregistration after its sub-drivers,
> which ensures all drivers are unregistered in the reverse order used
> when they were registered.
are you sure about that?
I.e. currently rockchip_d
On 8/14/24 05:46, Louis Chauvet wrote:
The meaning of index was not clear. Replace them with crtc_index to
clearly indicate its usage.
Signed-off-by: Louis Chauvet
IMHO no need for this patch, especially considering that you are going
to change those lines anyway in a future series.
I'd just
On 8/14/24 05:46, Louis Chauvet wrote:
Some newlines were missing around comments.
Signed-off-by: Louis Chauvet
Applied to drm/misc/drm-misc-next!
Best Regards,
- Maíra
---
drivers/gpu/drm/vkms/vkms_drv.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/
5.15-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit ecde5db1598aecab54cc392282c15114f526f05f upstream.
Compute the i2c timeout in jiffies from a value in milliseconds. The
original values of 2 jiffies equals 2 milliseco
Hi Louis,
On 8/14/24 05:46, Louis Chauvet wrote:
This series does not introduce functionnal changes, only some
documentation and renaming to clarify the code.
This series is based on [1].
[1]:
https://lore.kernel.org/all/20240814-writeback_line_by_line-v2-0-36541c717...@bootlin.com/
There i
Hi Dave and Sima,
Here goes another round of drm-xe-fixes.
The amount of patches is higher for this round, but not
because we have more fixes merged this week, but because
of me and because a few fixes are depending on some
other prep/refactor patches, now merged.
1. As I had told you last week,
5.15-stable review patch. If anyone has any objections, please let me know.
--
From: Zack Rusin
commit e58337100721f3cc0c7424a18730e4f39844934f upstream.
Introduce a version of the fence ops that on release doesn't remove
the fence from the pending list, and thus doesn't requi
Hi, Javier:
Javier Carrasco 於 2024年6月25日 週二 上午12:44寫道：
>
> The main fix is a possible memory leak on an early exit in the
> for_each_child_of_node() loop. That fix has been divided into a patch
> that can be backported (a simple of_node_put()), and another one that
> uses the scoped variant of th
On Thu, Aug 15, 2024 at 11:37:17AM GMT, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the drm-xe tree got a conflict in:
drivers/gpu/drm/xe/display/xe_display.c
between commit:
769b081c18b9 ("drm/i915/opregion: convert to struct intel_display")
from the drm-intel tree and com
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit ecde5db1598aecab54cc392282c15114f526f05f upstream.
Compute the i2c timeout in jiffies from a value in milliseconds. The
original values of 2 jiffies equals 2 milliseco
Hi Dave, Sima,
here's the weekly PR for drm-misc-fixes. It resolves an OOB access
in v3d and a few minor errors.
Best regards
Thomas
drm-misc-fixes-2024-08-15:
Short summary of fixes pull:
panel:
- dt-bindings style fixes
panel-orientation:
- add quirk for Any Loki Max
- add quirk for Any Loki
On Mon, 24 Jun 2024, Daniel Vetter wrote:
> On Tue, May 14, 2024 at 03:55:08PM +0300, Jani Nikula wrote:
>> Prefer the struct drm_edid based functions for reading the EDID and
>> updating the connector.
>>
>> The functional change is that the CEC physical address gets invalidated
>> when the EDID
On Mon, 12 Aug 2024, Jani Nikula wrote:
> drm_edid_block_valid() is no longer used outside of drm_edid.c. Make it
> static.
>
> Acked-by: Zhi Wang
> Signed-off-by: Jani Nikula
Both pushed to drm-misc-next with Sima's R-b on patch 2.
BR,
Jani.
>
> ---
>
> Cc: Zhenyu Wang
> Cc: Zhi Wang
> Cc
The definition of msm_atomic_state_clear() and msm_atomic_state_free()
has been removed since commit c21c731d93e8 ("drm/msm: Don't subclass
drm_atomic_state anymore").
Also, the definition of msm_dsi_host_set_src_pll() has been removed
since commit 9b077c1581cf ("drm/msm/dsi: stop setting clock pa
On Mon, 5 Aug 2024 13:08:56 +0200, Alex Bee wrote:
> HDMI analyser shows that the AVI infoframe is no being longer send.
>
> The switch to the HDMI connector api should have used the frame content
> which is now given in the buffer parameter, but instead still uses the
> (now) empty and superfluou
On Wed, 07 Aug 2024 14:07:22 +0300, Cristian Ciocaltea wrote:
> The Rockchip RK3588 SoC family integrates the Synopsys DesignWare HDMI
> 2.1 Quad-Pixel (QP) TX controller, which is a new IP block, quite
> different from those used in the previous generations of Rockchip SoCs.
>
> The controller su
On Sat, 13 Jul 2024 22:52:05 +0200, Christophe JAILLET wrote:
> 'struct drm_encoder_helper_funcs' is not modified in these drivers.
>
> Constifying this structure moves some data to a read-only section, so
> increase overall security.
>
> On a x86_64, with allmodconfig:
> Before:
> ==
>te
On Mon, 24 Jun 2024 17:40:47 -0300, Val Packett wrote:
> This tiny patch series makes the changes required to enable the RGB
> display output on the Rockchip RK3066 SoC. Final version as discussed.
>
> Val Packett (2):
> drm/rockchip: vop: clear DMA stop bit on RK3066
> drm/rockchip: vop: enab
On Tue, 13 Aug 2024 00:15:07 +0300, Cristian Ciocaltea wrote:
> This series provides a few patches to cleanup/improve the Rockchip DW
> HDMI platform driver.
>
> Note the patches were initially sent as part of [1], in an attempt to
> add support for the RK3588 HDMI TX Controller, but were removed
On Thu, 4 Jul 2024 01:32:20 +0200, Dragan Simic wrote:
> Clean up a few logged messages, which were previously worded as rather
> incomplete sentences separated by periods. This was both a bit unreadable
> and grammatically incorrect, so convert them into partial sentences separated
> (or connecte
On 13/08/2024 19:47, Rob Clark wrote:
On Tue, Aug 13, 2024 at 6:57 AM Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Currently it is not well defined what is drm-memory- compared to other
categories.
In practice the only driver which emits these keys is amdgpu and in them
exposes the current
Hi Dominique, hi Lucas,
On 17.06.24 6:32 PM, Lucas Stach wrote:
> Hi Dominique,
>
> Am Montag, dem 17.06.2024 um 15:16 +0900 schrieb Dominique MARTINET:
>> Adam Ford wrote on Sat, Feb 03, 2024 at 10:52:50AM -0600:
>>> From: Lucas Stach
>>>
>>> Add a simple wrapper driver for the DWC HDMI bridge
Am 15.08.24 um 10:07 schrieb Tomi Valkeinen:
Hi,
On 15/08/2024 10:59, Thomas Zimmermann wrote:
Ping. This patch still needs an ack.
Am 31.07.24 um 14:17 schrieb Thomas Zimmermann:
Replace FB_BLANK_ constants with their counterparts from the
backlight subsystem. The values are identical, so
Hi,
On 15/08/2024 10:59, Thomas Zimmermann wrote:
Ping. This patch still needs an ack.
Am 31.07.24 um 14:17 schrieb Thomas Zimmermann:
Replace FB_BLANK_ constants with their counterparts from the
backlight subsystem. The values are identical, so there's no
change in functionality or semantics.
On Wed, 07 Aug 2024 17:27:21 +0200,
Takashi Iwai wrote:
>
> Hi,
>
> we still keep the legacy vmalloc ALSA PCM helper API since there is
> only a single user of it, namely, the DRM dw-hdmi bridge driver.
> In the past, I attempted to change the buffer management of the
> driver, but due to the lac
Ping. This patch still needs an ack.
Am 31.07.24 um 14:17 schrieb Thomas Zimmermann:
Replace FB_BLANK_ constants with their counterparts from the
backlight subsystem. The values are identical, so there's no
change in functionality or semantics.
Signed-off-by: Thomas Zimmermann
Cc: Jyri Sarha
78 matches
Mail list logo
