On 12/11/2024 5:46 PM, Dmitry Baryshkov wrote:
> On Wed, Dec 11, 2024 at 08:46:16AM +0800, Xiangxu Yin wrote:
>>
>>
>> On 12/10/2024 11:09 PM, Dmitry Baryshkov wrote:
>>> On Thu, Dec 05, 2024 at 08:31:24PM +0200, Dmitry Baryshkov wrote:
On Thu, Dec 05, 2024 at 09:26:47PM +0800, Xiangxu Yin
First of all, do appreciate taking the time to explain your positions
much more verbosely this time.
Quoting Christian König (2024-12-10 16:03:14)
> Am 10.12.24 um 12:57 schrieb Joonas Lahtinen:
>
> Quoting Christian König (2024-12-10 12:00:48)
>
> Am 10.12.24 um 10:33 schrieb Joonas
Hi Karol,
Thank you for the patch.
On Wed, Dec 11, 2024 at 01:20:26PM +0100, Karol Przybylski wrote:
> This patch fixes a potential integer overflow in the zynqmp_dp_rate_get()
> function.
>
> The issue comes up when the expression
> drm_dp_bw_code_to_link_rate(dp->test.bw_code) * 1 is eva
Looking at both i915 and nouveau DP drivers, both are setting the first
LTTPR (if found) in transparent mode first and then in non-transparent
mode, just like the DP v2.0 specification mentions in section 3.6.6.1.
Being part of the standard, setting the LTTPR in a specific operation mode
can be ea
LTTPRs operating modes are defined by the DisplayPort standard and the
generic framework now provides a helper to switch between them, which
is handling the explicit disabling of non-transparent mode and its
disable->enable sequence mentioned in the DP Standard v2.0 section
3.6.6.1.
So use the new
LTTPRs operating modes are defined by the DisplayPort standard and the
generic framework now provides a helper to switch between them, which
is handling the explicit disabling of non-transparent mode and its
disable->enable sequence mentioned in the DP Standard v2.0 section
3.6.6.1.
So use the new
Link Training Tunable PHY Repeaters (LTTPRs) are defined in DisplayPort
1.4a specification. As the name suggests, these PHY repeaters are
capable of adjusting their output for link training purposes.
According to the DisplayPort standard, LTTPRs have two operating
modes:
- non-transparent - it re
According to the DisplayPort standard, LTTPRs have two operating
modes:
- non-transparent - it replies to DPCD LTTPR field specific AUX
requests, while passes through all other AUX requests
- transparent - it passes through all AUX requests.
Switching between this two modes is done by the DPT
Hi Stefan,
On 02/12/24 09:03, Stefan Wahren wrote:
From: Dave Stevenson
It is permitted on situations such as system resume for plane->state
to be non-NULL, and that should be handled by freeing it. Do so.
Signed-off-by: Dave Stevenson
Signed-off-by: Stefan Wahren
Was this patch applied?
[Public]
> From: Koenig, Christian
> Sent: Wednesday, December 11, 2024 3:16
> Am 10.12.24 um 18:59 schrieb Yunxiang Li:
> > Tracking the state of a GEM object for shared stats is quite difficult
> > since the handle_count is managed behind driver's back. So instead
> > considers GEM object share
Hi Maíra,
Am 11.12.24 um 14:19 schrieb Maíra Canal:
Hi Stefan,
On 02/12/24 09:03, Stefan Wahren wrote:
From: Dave Stevenson
It is permitted on situations such as system resume for plane->state
to be non-NULL, and that should be handled by freeing it. Do so.
Signed-off-by: Dave Stevenson
Si
Hi Iago,
On 09/12/24 04:20, Iago Toral wrote:
Thanks Maíra!
Acked-by: Iago Toral Quiroga
Thanks for your review! Applied to misc/kernel.git (drm-misc-next).
Best Regards,
- Maíra
El vie, 06-12-2024 a las 12:39 -0300, Maíra Canal escribió:
This commit fixes several miscellaneous document
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on staging/staging-next staging/staging-linus
drm/drm-next drm-exynos/exynos-drm-next linus/master v6.13-rc2 next-20241211]
[If your patch is applied to the
Uprev IGT to the latest version and update expectation files.
Signed-off-by: Vignesh Raman
---
v1:
- Pipeline link -
https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1327810
Will update the flake bug report link after v1 is reviewed.
---
drivers/gpu/drm/ci/gitlab-ci.yml
On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote:
> +/**
> + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode
> + * @aux: DisplayPort AUX channel
> + * @enable: Enable or disable transparent mode
> + *
> + * Returns 0 on success or a negative error code on failure.
Hi Stefan,
On 11/12/24 11:07, Stefan Wahren wrote:
Hi Maíra,
Am 11.12.24 um 14:19 schrieb Maíra Canal:
Hi Stefan,
On 02/12/24 09:03, Stefan Wahren wrote:
From: Dave Stevenson
It is permitted on situations such as system resume for plane->state
to be non-NULL, and that should be handled by
On Wed, Dec 11, 2024 at 11:05:52AM +0800, Liu Ying wrote:
> On 12/11/2024, Rob Herring wrote:
> > On Mon, Dec 09, 2024 at 11:39:05AM +0800, Liu Ying wrote:
> >> Freescale i.MX8qxp Display Controller is implemented as construction set of
> >> building blocks with unified concept and standardized int
On Wed, Dec 11, 2024 at 03:04:15PM +0200, Abel Vesa wrote:
> +static void msm_dp_display_lttpr_init(struct msm_dp_display_private *dp)
> +{
> + int lttpr_count;
> +
> + if (drm_dp_read_lttpr_common_caps(dp->aux, dp->panel->dpcd,
> + dp->lttpr_caps))
>
Am 11.12.24 um 15:02 schrieb Li, Yunxiang (Teddy):
[Public]
From: Koenig, Christian
Sent: Wednesday, December 11, 2024 3:16
Am 10.12.24 um 18:59 schrieb Yunxiang Li:
Tracking the state of a GEM object for shared stats is quite difficult
since the handle_count is managed behind driver's back.
On Fri, Dec 06, 2024 at 11:32:37AM +0200, Tomi Valkeinen wrote:
> From: Tomi Valkeinen
>
> Extend the Renesas DU display bindings to support the r8a779h0 V4M.
>
> Note that we remove the requirement for two ports from the global part
> of the bindings, as each conditional part defines the number
On Wednesday, 11 December 2024 01:34:34 EST Andy Yan wrote:
> Hi Detlev,
>
> At 2024-12-11 02:40:14, "Detlev Casanova"
wrote:
> >Hi Andy,
> >
> >On Monday, 9 December 2024 07:29:18 EST Andy Yan wrote:
> >> From: Andy Yan
> >>
> >> There are two AXI bus in vop2, windows attached on the same bus
Hi Dimitry,
Thanks for the review.
On Wed, Dec 11, 2024 at 5:44 PM Dmitry Baryshkov
wrote:
>
> On Mon, Dec 09, 2024 at 02:46:32PM +0800, Xin Ji wrote:
> > When user enabled HDCP feature, upper layer will set HDCP content
> > to DRM_MODE_CONTENT_PROTECTION_DESIRED. Next, anx7625 will update
> > H
[Public]
> From: Koenig, Christian
> Sent: Wednesday, December 11, 2024 10:03
> Am 11.12.24 um 15:02 schrieb Li, Yunxiang (Teddy):
> > [Public]
> >
> >> From: Koenig, Christian
> >> Sent: Wednesday, December 11, 2024 3:16 Am 10.12.24 um 18:59 schrieb
> >> Yunxiang Li:
> >>> Tracking the state of
Hi Vignesh,
thanks for the patch.
On Wed, 11 Dec 2024 11:28:05 -0300 Vignesh Raman wrote ---
> Uprev IGT to the latest version and update expectation files.
>
> Signed-off-by: Vignesh Raman vignesh.ra...@collabora.com>
> ---
>
> v1:
> - Pipeline link -
> https://gitlab.
Hi Neil,
On Wed, Dec 11, 2024 at 6:31 AM Krzysztof Kozlowski wrote:
>
> On Tue, Dec 10, 2024 at 07:57:04AM -0300, Fabio Estevam wrote:
> > From: Fabio Estevam
> >
> > The AUO G084SN05 V9 is an 8.4" 800x600 LVDS display.
> >
> > Add a compatible entry for this LVDS display model.
> >
> > Signed-o
This patch series enables display of the size of driver-owned shmem BO's that
aren't
exposed to userspace through a DRM handle.
Discussion of previous revision can be found here [1].
Changelog:
v4:
- Remove unrelated formating fix
- Moved calculating overall size of a group's kernel BO's into
This will display the sizes of kenrel BO's bound to an open file, which are
otherwise not exposed to UM through a handle.
The sizes recorded are as follows:
- Per group: suspend buffer, protm-suspend buffer, syncobjcs
- Per queue: ringbuffer, profiling slots, firmware interface
- For all heaps
A previous commit enabled display of driver-internal kernel BO sizes
through the device file's fdinfo interface.
Expand the description of the relevant driver-specific key:value pairs
with the definitions of the new drm-*-internal ones.
Signed-off-by: Adrián Larumbe
---
Documentation/gpu/pantho
Hi Adrián,
On 11/12/2024 16:34, Adrián Larumbe wrote:
A previous commit enabled display of driver-internal kernel BO sizes
through the device file's fdinfo interface.
Expand the description of the relevant driver-specific key:value pairs
with the definitions of the new drm-*-internal ones.
Sig
Hi Marek,
On 09.12.2024 22:51, Marek Vasut wrote:
On 12/9/24 10:27 AM, Nikolaus Voss wrote:
On 07.12.2024 12:46, Marek Vasut wrote:
On 12/4/24 11:40 AM, Nikolaus Voss wrote:
LDB clock has to be a fixed multiple of the pixel clock.
As LDB and pixel clock are derived from different clock source
Hello,
This patch set implements initial support for performance counter
sampling in Panthor, as a follow-up for Adrián Larumbe's patch
set [1].
Existing performance counter workflows, such as those in game
engines, and user-space power models/governor implementations
require the ability to simul
This change adds the IOCTL to query data about the performance counter
setup. Some of this data was available via previous DEV_QUERY calls,
for instance for GPU info, but exposing it via PERF_INFO
minimizes the overhead of creating a single session to just the one
aggregate IOCTL.
To better align
Signed-off-by: Lukas Zapolskas
---
drivers/gpu/drm/panthor/panthor_drv.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/panthor/panthor_drv.c
b/drivers/gpu/drm/panthor/panthor_drv.c
index 2848ab442d10..ef081a383fa9 100644
--- a/drivers/gpu/drm/panthor/pant
Added the panthor_perf system initialization and unplug code to allow
for the handling of userspace sessions to be added in follow-up patches.
Signed-off-by: Lukas Zapolskas
---
drivers/gpu/drm/panthor/panthor_device.c | 7 +++
drivers/gpu/drm/panthor/panthor_device.h | 5 +-
drivers/gpu/drm/p
This patch implements the PANTHOR_PERF_CONTROL ioctl series, and
a PANTHOR_GET_UOBJ wrapper to deal with the backwards and forwards
compatibility of the uAPI.
Stub function definitions are added to ensure the patch builds on its own,
and will be removed later in the series.
Signed-off-by: Lukas Z
This patch extends the DEV_QUERY ioctl to return information about the
performance counter setup for userspace, and introduces the new
ioctl DRM_PANTHOR_PERF_CONTROL in order to allow for the sampling of
performance counters.
The new design is inspired by the perf aux ringbuffer, with the insert
a
From: Adrián Larumbe
The sampler aggregates counter and set requests coming from userspace
and mediates interactions with the FW interface, to ensure that user
sessions cannot override the global configuration.
>From the top-level interface, the sampler supports two different types
of samples: c
Signed-off-by: Lukas Zapolskas
---
drivers/gpu/drm/panthor/panthor_device.c | 3 +
drivers/gpu/drm/panthor/panthor_perf.c | 86
drivers/gpu/drm/panthor/panthor_perf.h | 2 +
3 files changed, 91 insertions(+)
diff --git a/drivers/gpu/drm/panthor/panthor_device.c
b/
To allow for combining the requests from multiple userspace clients, an
intermediary layer between the HW/FW interfaces and userspace is
created, containing the information for the counter requests and
tracking of insert and extract indices. Each session starts inactive and
must be explicitly activ
Hi Marek,
On 09.12.2024 22:46, Marek Vasut wrote:
On 12/9/24 9:46 AM, Nikolaus Voss wrote:
and store the panel's timing in EDID EEPROM.
Oh, that is a new one. Does the EDID EEPROM store the entirety of
'struct display_timing {}' somehow , or is that a custom format ?
Well, sort of ;-). VESA
Hi,
On 11/12/2024 17:29, Fabio Estevam wrote:
Hi Neil,
On Wed, Dec 11, 2024 at 6:31 AM Krzysztof Kozlowski wrote:
On Tue, Dec 10, 2024 at 07:57:04AM -0300, Fabio Estevam wrote:
From: Fabio Estevam
The AUO G084SN05 V9 is an 8.4" 800x600 LVDS display.
Add a compatible entry for this LVDS d
Hi Mihail,
On 11.12.2024 16:40, Mihail Atanassov wrote:
> Hi Adrián,
>
> On 11/12/2024 16:34, Adrián Larumbe wrote:
> > A previous commit enabled display of driver-internal kernel BO sizes
> > through the device file's fdinfo interface.
> >
> > Expand the description of the relevant driver-speci
On Wed, Dec 11, 2024 at 12:15:07PM +0200, Cristian Ciocaltea wrote:
> The RK3588 specific implementation is currently quite limited in terms
> of handling the full range of display modes supported by the connected
> screens, e.g. 2560x1440@75Hz, 2048x1152@60Hz, 1024x768@60Hz are just a
> few of the
On Tue, Dec 10, 2024 at 04:16:46PM +0200, Dmitry Baryshkov wrote:
> Reduce boilerplate code and move calls to
> drm_atomic_helper_connector_hdmi_check() to the drm_bridge_connector.
> Initially the drm_bridge_connector didn't use HDMI state helpers
> directly, so each driver had to call that functi
On Wed, Dec 04, 2024 at 01:17:17PM +0200, Raag Jadav wrote:
> + misc maintainers
>
> On Tue, Dec 03, 2024 at 11:18:00AM +0100, Christian König wrote:
> > Am 03.12.24 um 06:00 schrieb Raag Jadav:
> > > On Mon, Dec 02, 2024 at 10:07:59AM +0200, Raag Jadav wrote:
> > > > On Fri, Nov 29, 2024 at 10:40
Add backlight controllers attached via Apple DWI 2-wire interface.
Signed-off-by: Nick Chan
---
.../bindings/leds/backlight/apple,dwi-bl.yaml | 57 +++
1 file changed, 57 insertions(+)
create mode 100644
Documentation/devicetree/bindings/leds/backlight/apple,dwi-bl.yaml
diff -
Add MAINTAINERS entries for the driver.
Signed-off-by: Nick Chan
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 17daa9ee9384..3a7dec3f9a5a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2196,6 +2196,7 @@ F:
Documentation/devicetree/b
On Wed, Dec 11, 2024 at 03:42:27PM +0100, Johan Hovold wrote:
> On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote:
>
> > +/**
> > + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode
> > + * @aux: DisplayPort AUX channel
> > + * @enable: Enable or disable transparent
On Tue, Nov 19, 2024 at 02:56:12PM +0100, Thomas Hellström wrote:
> On Tue, 2024-10-15 at 20:24 -0700, Matthew Brost wrote:
> > Add SVM range invalidation vfunc.
> >
> > v2:
> > - Don't run invalidation if VM is closed
> > - Cycle notifier lock in xe_svm_close
> > - Drop xe_gt_tlb_invalidation_
From: Imre Deak
[ Upstream commit 2b245c97b1af5d8f04c359e0826cb5a5c81ef704 ]
After an out-of-memory error the reception state should be reset, so
that the next attempt receiving a message doesn't fail (due to getting a
start-of-message packet, while the reception state has already the
start-of-m
From: Imre Deak
[ Upstream commit e54b00086f7473dbda1a7d6fc47720ced157c6a8 ]
While receiving an MST up request message from one thread in
drm_dp_mst_handle_up_req(), the MST topology could be removed from
another thread via drm_dp_mst_topology_mgr_set_mst(false), freeing
mst_primary and setting
From: Imre Deak
[ Upstream commit 2b245c97b1af5d8f04c359e0826cb5a5c81ef704 ]
After an out-of-memory error the reception state should be reset, so
that the next attempt receiving a message doesn't fail (due to getting a
start-of-message packet, while the reception state has already the
start-of-m
From: Imre Deak
[ Upstream commit e54b00086f7473dbda1a7d6fc47720ced157c6a8 ]
While receiving an MST up request message from one thread in
drm_dp_mst_handle_up_req(), the MST topology could be removed from
another thread via drm_dp_mst_topology_mgr_set_mst(false), freeing
mst_primary and setting
From: Imre Deak
[ Upstream commit 2b245c97b1af5d8f04c359e0826cb5a5c81ef704 ]
After an out-of-memory error the reception state should be reset, so
that the next attempt receiving a message doesn't fail (due to getting a
start-of-message packet, while the reception state has already the
start-of-m
On Tue, Nov 19, 2024 at 03:26:32PM +0100, Thomas Hellström wrote:
> On Tue, 2024-10-15 at 20:25 -0700, Matthew Brost wrote:
> > Add (re)bind to SVM page fault handler. To facilitate add support
> > function to VM layer which (re)binds a SVM range. Also teach PT layer
> > to
> > understand (re)binds
On Wed, Dec 11, 2024 at 11:50:26AM -0800, Abhinav Kumar wrote:
> Similar to the r_pipe sspp protect, add a check to protect
> the pipe state prints to avoid NULL ptr dereference for cases when
> the state is dumped without a corresponding atomic_check() where the
> pipe->sspp is assigned.
>
> Fixe
On 12/10/2024 23:28, Lizhi Hou wrote:
On 12/10/24 16:28, Mario Limonciello wrote:
On 12/6/2024 15:59, Lizhi Hou wrote:
Add SET_STATE ioctl to configure device power mode for aie2 device.
Three modes are supported initially.
POWER_MODE_DEFAULT: Enable clock gating and set DPM (Dynamic Power
Ma
Quoting Dmitry Baryshkov (2024-12-05 10:47:08)
> On Tue, Dec 03, 2024 at 03:50:58PM -0800, Stephen Boyd wrote:
> >
> > The easiest way to imagine this is that we took the usb-c-connector and
> > jammed an HDMI dongle in there with some glue so that it can never be
> > removed. There isn't any USB g
Quoting Dmitry Baryshkov (2024-12-02 02:06:35)
> diff --git a/drivers/gpu/drm/msm/dp/dp_catalog.h
> b/drivers/gpu/drm/msm/dp/dp_catalog.h
> index
> 13486c9c8703748e69e846be681951368df0a29e..2c500dc0898edfe1d6bdac2eedf3c1b78056cf6b
> 100644
> --- a/drivers/gpu/drm/msm/dp/dp_catalog.h
> +++ b/driv
Quoting Dmitry Baryshkov (2024-12-02 02:06:36)
> diff --git a/drivers/gpu/drm/msm/dp/dp_aux.c b/drivers/gpu/drm/msm/dp/dp_aux.c
> index
> bc8d46abfc619d669dce339477d58fb0c464a3ea..46e8a2e13ac1d1249fbad9b50a6d64c52d51cf38
> 100644
> --- a/drivers/gpu/drm/msm/dp/dp_aux.c
> +++ b/drivers/gpu/drm/msm
Call encoder mode_set() when connectors are changed. This avoids issues
for cases where the connectors are changed but CRTC mode is not.
---
Changes in v3:
- BUILD_BUG_ON() for encoders and connectors array size check (Dmitry)
- Added more descriptive, file-specific names for helper functions
(D
Quoting Dmitry Baryshkov (2024-12-02 02:06:32)
> The msm_dp_utils_pack_sdp_header() accepts an unlimited-size u32 pointer
> for the header output, while it expects a two-element array. It performs
> a sizeof check which is always true on 64-bit platforms (since
> sizeof(u32*) is 8) and is always fa
Quoting Dmitry Baryshkov (2024-12-02 02:06:33)
> The msm_dp_panel_dump_regs() and msm_dp_catalog_dump_regs() are not
> called anywhere. If there is a necessity to dump registers, the
> snapshotting should be used instead. Drop these two functions.
>
> Signed-off-by: Dmitry Baryshkov
> ---
Reviewe
Quoting Dmitry Baryshkov (2024-12-11 13:16:56)
> On Wed, 11 Dec 2024 at 23:11, Stephen Boyd wrote:
> >
> > It is pure DP. Maybe we can have a google,cros-ec-usbc-hdmi compatible
> > string here because this is a weird design.
>
> Just google,cros-ec-hdmi for the corresponding connector?
>
Sure.
On Wed, 11 Dec 2024 at 23:11, Stephen Boyd wrote:
>
> Quoting Dmitry Baryshkov (2024-12-05 10:47:08)
> > On Tue, Dec 03, 2024 at 03:50:58PM -0800, Stephen Boyd wrote:
> > >
> > > The easiest way to imagine this is that we took the usb-c-connector and
> > > jammed an HDMI dongle in there with some
Add a subtest to check that modeset is called when the connector is
changed
Signed-off-by: Jessica Zhang
---
Changes in v3:
- Use BUILD_BUG_ON to check connectors and encoders array sizes (Dmitry)
- Renamed functions to be more test-specific (Dmitry)
- Added comment description for test (Dmitry)
Quoting Dmitry Baryshkov (2024-12-02 02:06:31)
> Rather than printing random garbage from stack and pretending that it is
> the default safe_to_exit_level, set the variable beforehand.
>
> Fixes: d13e36d7d222 ("drm/msm/dp: add audio support for Display Port on MSM")
> Reported-by: kernel test robot
From: Abhinav Kumar
In certain use-cases, a CRTC could switch between two encoders
and because the mode being programmed on the CRTC remains
the same during this switch, the CRTC's mode_changed remains false.
In such cases, the encoder's mode_set also gets skipped.
Skipping mode_set on the encod
On Wed, Dec 11, 2024 at 07:58:05PM +0530, Vignesh Raman wrote:
> Uprev IGT to the latest version and update expectation files.
>
> Signed-off-by: Vignesh Raman
> ---
>
> v1:
> - Pipeline link -
> https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1327810
> Will update the flake
Op 04-12-2024 om 16:45 schreef Jocelyn Falempe:
Move the color conversions, blit and fill functions to drm_draw.c,
so that they can be re-used by drm_log.
drm_draw is internal to the drm subsystem, and shouldn't be used by
gpu drivers.
Signed-off-by: Jocelyn Falempe
Reviewed-by: Thomas Zimmerma
On Mon, Dec 02, 2024 at 11:44:47AM +0100, Thomas Hellström wrote:
> On Tue, 2024-10-15 at 20:25 -0700, Matthew Brost wrote:
> > Add XE_BO_FLAG_SYSTEM_ALLOC to indicate BO is tied to SVM range.
> >
> > Add XE_BO_FLAG_SKIP_CLEAR to indicate BO does not need to cleared.
> >
> > v2:
> > - Take VM re
On 11/29/2024 5:55 PM, Dmitry Baryshkov wrote:
Virtual wide planes give high amount of flexibility, but it is not
always enough:
In parallel multirect case only the half of the usual width is supported
for tiled formats. Thus the whole width of two tiled multirect
rectangles can not be greate
Hi Dave, Simona,
Fixes for 6.13.
The following changes since commit 73dae652dcac776296890da215ee7dec357a1032:
drm/amdgpu: rework resume handling for display (v2) (2024-12-03 18:19:23
-0500)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git
tags/amd-dr
On Tue, 10 Dec 2024 at 22:02, Easwar Hariharan
wrote:
>
> Commit b35108a51cf7 ("jiffies: Define secs_to_jiffies()") introduced
> secs_to_jiffies(). As the value here is a multiple of 1000, use
> secs_to_jiffies() instead of msecs_to_jiffies to avoid the multiplication.
>
> This is converted using
On Wed, Dec 11, 2024 at 06:23:03PM +0100, Heiko Stübner wrote:
> Am Mittwoch, 11. Dezember 2024, 18:07:57 CET schrieb Maxime Ripard:
> > On Wed, Dec 11, 2024 at 12:15:07PM +0200, Cristian Ciocaltea wrote:
> > > The RK3588 specific implementation is currently quite limited in terms
> > > of handling
On Wed, Dec 11, 2024 at 03:42:27PM +0100, Johan Hovold wrote:
> On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote:
>
> > +/**
> > + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode
> > + * @aux: DisplayPort AUX channel
> > + * @enable: Enable or disable transparent
On Wed, Dec 11, 2024 at 12:25:07AM -0300, André Almeida wrote:
> Hi,
>
> The goal of this work is to find a nice way to allow amdgpu to perform
> async page flips in the overlay plane as well, not only on the primary
> one. Currently, when using the atomic uAPI, this is the only type of
> plane al
On Mon, Dec 02, 2024 at 01:40:20PM +0100, Thomas Hellström wrote:
> On Tue, 2024-10-15 at 20:25 -0700, Matthew Brost wrote:
> > Used to show we can bounce memory multiple times.
> >
> > Signed-off-by: Matthew Brost
> > ---
> > drivers/gpu/drm/xe/xe_module.c | 7 +++
> > drivers/gpu/drm/xe/xe
Similar to the r_pipe sspp protect, add a check to protect
the pipe state prints to avoid NULL ptr dereference for cases when
the state is dumped without a corresponding atomic_check() where the
pipe->sspp is assigned.
Fixes: 31f7148fd370 ("drm/msm/dpu: move pstate->pipe initialization to
dpu_pla
On Wed, Nov 20, 2024 at 05:05:32AM +0200, Gwan-gyeong Mun wrote:
>
>
> On 10/16/24 6:25 AM, Matthew Brost wrote:
> > +/**
> > + * xe_devm_add: Remap and provide memmap backing for device memory
> > + * @tile: tile that the memory region belongs to
> > + * @mr: memory region to remap
> > + *
> > +
On Mon, Dec 02, 2024 at 01:27:24PM +0100, Thomas Hellström wrote:
> On Tue, 2024-10-15 at 20:25 -0700, Matthew Brost wrote:
> > Wire xe_bo_move to GPUSVM migration to SRAM with trylocking of mmap
> > lock.
> >
> > v2:
> > - Use xe_svm_bo_evict
> > - Drop bo->range
> >
> > Signed-off-by: Matthew
On Mon, Dec 02, 2024 at 01:37:46PM +0100, Thomas Hellström wrote:
> On Tue, 2024-10-15 at 20:25 -0700, Matthew Brost wrote:
> > Useful to experiment with notifier size and how it affects
> > performance.
> >
> > Signed-off-by: Matthew Brost
> > ---
> > drivers/gpu/drm/xe/xe_module.h | 1 +
> > d
On Mon, Dec 02, 2024 at 01:06:33PM +0100, Thomas Hellström wrote:
> On Tue, 2024-10-15 at 20:25 -0700, Matthew Brost wrote:
> > Migration is implemented with range granularity, with VRAM backing
> > being
> > a VM private TTM BO (i.e., shares dma-resv with VM). The lifetime of
> > the
> > TTM BO is
Hi Helen / Vignesh
On 12/4/2024 12:33 PM, Helen Mae Koike Fornazier wrote:
On Wed, 04 Dec 2024 16:21:26 -0300 Abhinav Kumar wrote ---
> Hi Helen
>
> On 12/4/2024 11:14 AM, Helen Mae Koike Fornazier wrote:
> > Hi Abhinav,
> >
> > Thanks for your patch.
> >
> >
> >
>
On 12/6/2024 1:16 AM, Konrad Dybcio wrote:
> On 26.11.2024 3:06 PM, Akhil P Oommen wrote:
>> From: Jie Zhang
>>
>> Add gpu and gmu nodes for qcs615 chipset.
>>
>> Signed-off-by: Jie Zhang
>> Signed-off-by: Akhil P Oommen
>> ---
>> arch/arm64/boot/dts/qcom/qcs615.dtsi | 86
>> ++
Hi Dave and Sima,
Here goes our first drm-intel-next round targeting 6.14.
One drm/print change coming from here. The rest is mostly
display changes and one GSC FW update for ARL platforms.
Thanks,
Rodrigo.
drm-intel-next-2024-12-11:
Core Changes:
- drm/print: add drm_print_hex_dump()
Driver
Apple SoCs come with a 2-wire interface named DWI. On some iPhones, iPads
and iPod touches the backlight controller is connected via this interface.
This series adds a backlight driver for backlight controllers connected
this way.
Changes since v3:
- $ref to common.yaml in bindings
- (and then add
Am Mittwoch, 11. Dezember 2024, 18:07:57 CET schrieb Maxime Ripard:
> On Wed, Dec 11, 2024 at 12:15:07PM +0200, Cristian Ciocaltea wrote:
> > The RK3588 specific implementation is currently quite limited in terms
> > of handling the full range of display modes supported by the connected
> > screens
Am Mittwoch, 11. Dezember 2024, 18:47:44 CET schrieb Maxime Ripard:
> On Wed, Dec 11, 2024 at 06:23:03PM +0100, Heiko Stübner wrote:
> > Am Mittwoch, 11. Dezember 2024, 18:07:57 CET schrieb Maxime Ripard:
> > > On Wed, Dec 11, 2024 at 12:15:07PM +0200, Cristian Ciocaltea wrote:
> > > > The RK3588 s
Add driver for backlight controllers attached via Apple DWI 2-wire
interface, which is found on some Apple iPhones, iPads and iPod touches
with a LCD display.
Although there is an existing apple_bl driver, it is for backlight
controllers on Intel Macs attached via PCI, which is completely differen
Hi Dave, Sima,
A handful of fixes for the weekly release candidate cycle:
One fix for a performance regression in DSB register programming and also
in the same area a partial fix for the legacy LUT and DSB interaction.
Then there is a fix for a null pointer dereference in the GuC error state
ca
On Wed, Nov 20, 2024 at 09:04:20AM +0100, Thomas Hellström wrote:
> On Tue, 2024-11-19 at 15:08 -0800, Matthew Brost wrote:
> > On Tue, Nov 19, 2024 at 05:45:27PM +0100, Thomas Hellström wrote:
> > > On Tue, 2024-10-15 at 20:25 -0700, Matthew Brost wrote:
> > > > Add functions which migrate to / fr
On Wed, Dec 11, 2024 at 08:50:02PM +0800, Xiangxu Yin wrote:
>
>
> On 12/11/2024 5:46 PM, Dmitry Baryshkov wrote:
> > On Wed, Dec 11, 2024 at 08:46:16AM +0800, Xiangxu Yin wrote:
> >>
> >>
> >> On 12/10/2024 11:09 PM, Dmitry Baryshkov wrote:
> >>> On Thu, Dec 05, 2024 at 08:31:24PM +0200, Dmitry
On 11/12/2024 17:02, Adrián Larumbe wrote:
Hi Mihail,
On 11.12.2024 16:40, Mihail Atanassov wrote:
Hi Adrián,
On 11/12/2024 16:34, Adrián Larumbe wrote:
A previous commit enabled display of driver-internal kernel BO sizes
through the device file's fdinfo interface.
Expand the description
On Tue, Nov 19, 2024 at 03:45:33PM +0100, Thomas Hellström wrote:
> On Tue, 2024-10-15 at 20:25 -0700, Matthew Brost wrote:
> > Add basic SVM garbage collector which can destroy an SVM range upon
> > an
> > MMU UNMAP event.
> >
> > v2:
> > - Flush garbage collector in xe_svm_close
> >
> > Signed
From: Imre Deak
[ Upstream commit e54b00086f7473dbda1a7d6fc47720ced157c6a8 ]
While receiving an MST up request message from one thread in
drm_dp_mst_handle_up_req(), the MST topology could be removed from
another thread via drm_dp_mst_topology_mgr_set_mst(false), freeing
mst_primary and setting
On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote:
> According to the DisplayPort standard, LTTPRs have two operating
> modes:
> - non-transparent - it replies to DPCD LTTPR field specific AUX
>requests, while passes through all other AUX requests
> - transparent - it passes through a
On Wed, Dec 11, 2024 at 01:51:51PM -0800, Abhinav Kumar wrote:
>
>
> On 11/29/2024 5:55 PM, Dmitry Baryshkov wrote:
> > Virtual wide planes give high amount of flexibility, but it is not
> > always enough:
> >
> > In parallel multirect case only the half of the usual width is supported
> > for t
Quoting Dmitry Baryshkov (2024-12-02 02:06:38)
> Move panel-related functions to dp_panel.c, following up the cleanup
> done by the rest of the submodules.
>
> Signed-off-by: Dmitry Baryshkov
> ---
Reviewed-by: Stephen Boyd
Quoting Dmitry Baryshkov (2024-12-02 02:06:34)
> Having I/O regions inside a msm_dp_catalog_private() results in extra
> layers of one-line wrappers for accessing the data. Move I/O region base
> and size to the globally visible struct msm_dp_catalog.
>
> Signed-off-by: Dmitry Baryshkov
> ---
Rev
1 - 100 of 234 matches
Mail list logo
