On Wed, 25 Jun 2025 10:26:12 +0530, Dharma Balasubiramani wrote:
> The LVDS controller was hardcoded to JEIDA mapping, which leads to
> distorted output on panels expecting VESA mapping.
>
> Update the driver to dynamically select the appropriate mapping and
> pixel size based on the panel's adver
Remove the final dependencies on fbdev from the backlight subsystem.
This is really just the include of in ,
but it has some fallout in other code.
Patches 1 to 14 fix all the implicit includes that come from fb.h
throughout the kernel. It's all trivial, but touches various drivers.
Maintainers a
On Wed, Jun 25, 2025 at 10:26:10AM +0530, Dharma Balasubiramani wrote:
> Replace legacy .enable and .disable callbacks with their atomic
> counterparts .atomic_enable and .atomic_disable.
>
> Also, add turn off the serialiser inside atomic_disable().
>
> Signed-off-by: Dharma Balasubiramani
As
If the panel-simple driver is probed from a panel-dpi compatible, the
driver will use an empty panel_desc structure as a descriminant. It
will then allocate and fill another panel_desc as part of its probe.
However, that allocation needs to happen after the panel_simple
structure has been allocate
The empty panel_dpi struct was only ever used as a discriminant, but
it's kind of a hack, and with the reworks done in the previous patches,
we shouldn't need it anymore.
Let's get rid of it.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/panel/panel-simple.c | 27 ++-
In order to fix the regession introduced by commit de04bb0089a9
("drm/panel/panel-simple: Use the new allocation in place of
devm_kzalloc()"), we need to move the panel_desc lookup into the common
panel_simple_probe() function.
There's two callers for that function, the probe implementations of th
Commit de04bb0089a9 ("drm/panel/panel-simple: Use the new allocation in
place of devm_kzalloc()") moved the call to drm_panel_init into the
devm_drm_panel_alloc(), which needs a connector type to initialize
properly.
In the panel-dpi compatible case, the passed panel_desc structure is an
empty one
This will be especially useful for generic panels (like panel-simple)
which can take different code path depending on if they are MIPI-DSI
devices or platform devices.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/drm_mipi_dsi.c | 3 ++-
include/drm/drm_mipi_dsi.h | 3 +++
2 files changed
On Tue, Jun 24, 2025 at 03:13:05PM -0500, Anusha Srivatsa wrote:
> Currently driver is checking for desc == &panel_dpi to do the DPI
> specific panel desc allocations. This looks hacky.
I guess, but it's also the least of our concerns for Francesco regression.
> The panel allocation in panel_simp
bridge ops into 2.
- Update commit messages accordingly.
- Link to v4:
https://lore.kernel.org/r/20250624-microchip-lvds-v4-0-937d42a42...@microchip.com
Changes in v4:
- Split the commits into 3.
- Drop
- Link to v3:
https://lore.kernel.org/r/20250624-microchip-lvds-v3-1-c3c6f1e40
Hello Anusha,
thanks for quickly addressing this issue!
On Tue, 24 Jun 2025 15:13:05 -0500
Anusha Srivatsa wrote:
> Currently driver is checking for desc == &panel_dpi to do the DPI
> specific panel desc allocations. This looks hacky.
>
> The panel allocation in panel_simple_probe() breaks due
With the introduction of DBANC framework, the connector is no longer
initialised in bridge_attach if that flag is set by the display
controller.
This series does some cleanup for legacy !(DRM_BRIDGE_ATTACH_NO_CONNECTOR)
usecase and adds fixes for DRM_BRIDGE_ATTACH_NO_CONNECTOR usecase.
v3 patch l
On 18/06/2025 15:47, Maíra Canal wrote:
Add a test to submit a single job against a scheduler with the timeout
configured and verify that if the job is still running, the timeout
handler will skip the reset and allow the job to complete.
Signed-off-by: Maíra Canal
---
drivers/gpu/drm/schedu
Include to declare various OF helpers. Avoids dependency
on backlight header to include it.
Signed-off-by: Thomas Zimmermann
---
drivers/video/backlight/as3711_bl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/video/backlight/as3711_bl.c
b/drivers/video/backlight/as3711_bl.c
ind
Replace legacy .enable and .disable callbacks with their atomic
counterparts .atomic_enable and .atomic_disable.
Also, add turn off the serialiser inside atomic_disable().
Signed-off-by: Dharma Balasubiramani
---
drivers/gpu/drm/bridge/microchip-lvds.c | 13 +
1 file changed, 9 inse
The LVDS controller was hardcoded to JEIDA mapping, which leads to
distorted output on panels expecting VESA mapping.
Update the driver to dynamically select the appropriate mapping and
pixel size based on the panel's advertised media bus format. This
ensures compatibility with both JEIDA and VESA
pm_runtime_get_sync() and clk_prepare_enable() must be outside the atomic
context, hence move the sleepable operations accordingly.
- atomic_pre_enable() handles pm_runtime and clock preparation
- atomic_enable() enables the serializer based on panel format
- atomic_disable() turns off the seriali
Drop the unused drm_panel field from the mchp_lvds structure, and remove
the unnecessary port device node lookup, as devm_drm_of_get_bridge()
already performs the required checks internally.
Signed-off-by: Dharma Balasubiramani
---
drivers/gpu/drm/bridge/microchip-lvds.c | 16
1
On 24/06/25 4:32 pm, Maxime Ripard wrote:
> On Tue, Jun 24, 2025 at 02:54:15PM +0530, Dharma Balasubiramani wrote:
>> Modernize the bridge ops to use atomic_enable/disable.
>>
>> Signed-off-by: Dharma Balasubiramani
>> ---
>> drivers/gpu/drm/bridge/microchip-lvds.c | 26 ++---
Hi,
On 24/06/2025 11:04, Jayesh Choudhary wrote:
> TIDSS uses crtc_* fields to propagate its registers and set the
> clock rates. So set the CRTC modesetting timing parameters with
> the adjusted mode when needed, to set correct values.
>
> Cc: Tomi Valkeinen
> Signed-off-by: Jayesh Choudhary
>
Hi Amir,
On Tue, Jun 24, 2025 at 8:54 AM Amirreza Zarrabi
wrote:
>
> Hi Jens,
>
> On 6/10/2025 11:13 PM, Jens Wiklander wrote:
> > Add support in the OP-TEE backend driver for protected memory
> > allocation. The support is limited to only the SMC ABI and for secure
> > video buffers.
> >
> > OP-
Hi
Am 24.06.25 um 15:17 schrieb Christian König:
On 19.06.25 14:15, Thomas Zimmermann wrote:
Instead of testing import_attach for imported GEM buffers, invoke
drm_gem_is_imported() to do the test.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 2 +-
dri
On Tue, Jun 24, 2025 at 02:54:14PM +0530, Dharma Balasubiramani wrote:
> Drop the drm_panel field of the mchp_lvds struct as it is unused.
>
> Signed-off-by: Dharma Balasubiramani
> ---
> drivers/gpu/drm/bridge/microchip-lvds.c | 7 ---
> 1 file changed, 7 deletions(-)
>
> diff --git a/driv
On Tue Jun 24, 2025 at 2:31 PM CEST, Onur wrote:
> On Tue, 24 Jun 2025 10:20:48 +0200
> "Benno Lossin" wrote:
>
>> On Tue Jun 24, 2025 at 7:34 AM CEST, Onur wrote:
>> > Should we handle this in the initial implementation or leave it for
>> > follow-up patches after the core abstraction of ww_mutex
Hi Biju,
On Thu, Jun 19, 2025 at 6:05 AM Biju Das wrote:
>
> Hi Prabhakar,
>
> > -Original Message-
> > From: Biju Das
> > Sent: 18 June 2025 14:26
> > Subject: RE: [PATCH v6 1/4] clk: renesas: rzv2h-cpg: Add support for DSI
> > clocks
> >
> > Hi Prabhakar,
> >
> > > -Original Messag
On Tue, Jun 24, 2025 at 04:27:21PM +0300, Dmitry Baryshkov wrote:
> On Thu, Jun 19, 2025 at 10:40:26AM +0530, Ekansh Gupta wrote:
> > During rpmsg_probe, fastrpc device nodes are created first, then
> > channel specific resources are initialized, followed by
> > of_platform_populate, which triggers
On Tue, Jun 24, 2025 at 03:23:22PM +0200, Danilo Krummrich wrote:
> Implement From for u32 for all enum types used within the register!()
> macro.
>
> This avoids a conflict with [1] as reported in [2].
>
> Cc: Alexandre Courbot
> Cc: Miguel Ojeda
> Link:
> https://lore.kernel.org/r/20250615-p
DRM clients expose information through usage stats as documented in
Documentation/gpu/drm-usage-stats.rst (available online at
https://docs.kernel.org/gpu/drm-usage-stats.html). Add a tool like
PMU, similar to the hwmon PMU, that exposes DRM information.
v4: Rebase over changes like the auto merge
On Fri, Jun 20, 2025 at 01:37:45PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> When KMSAN is enabled, this function causes has a rather excessive stack
> usage:
>
> drivers/gpu/drm/i915/display/skl_watermark.c:2977:1: error: stack frame size
> (1432) exceeds limit (1408) in 'skl_comp
On Tue, Jun 24, 2025 at 03:23:23PM +0200, Danilo Krummrich wrote:
> Fix all warnings caused by `clippy::cast_lossless`, which is going to be
> enabled by [1].
>
> Cc: Alexandre Courbot
> Cc: Miguel Ojeda
> Link:
> https://lore.kernel.org/r/20250615-ptr-as-ptr-v12-5-f43b02458...@gmail.com [1]
>
On Tue, Jun 24, 2025 at 04:38:25PM +0100, Greg KH wrote:
> On Tue, Jun 24, 2025 at 04:36:35PM +0100, Greg KH wrote:
> > On Tue, Jun 24, 2025 at 04:27:21PM +0300, Dmitry Baryshkov wrote:
> > > On Thu, Jun 19, 2025 at 10:40:26AM +0530, Ekansh Gupta wrote:
> > > > During rpmsg_probe, fastrpc device no
DRM clients expose information through usage stats as documented in
Documentation/gpu/drm-usage-stats.rst (available online at
https://docs.kernel.org/gpu/drm-usage-stats.html). Add a tool like
PMU, similar to the hwmon PMU, that exposes DRM information. For
example on a tigerlake laptop:
```
$ per
Add perf_pmus__scan_for_event that only reads sysfs for pmus that
could contain a given event.
Signed-off-by: Ian Rogers
---
tools/perf/util/parse-events.c | 33 ---
tools/perf/util/pmus.c | 77 ++
tools/perf/util/pmus.h | 2 +
3 files
The test opens any DRM devices so that the shell has fdinfo files
containing the DRM data. The test then uses perf stat to make sure the
events can be read.
Signed-off-by: Ian Rogers
---
tools/perf/tests/shell/drm_pmu.sh | 78 +++
1 file changed, 78 insertions(+)
cre
On 24/06/2025 20:55, Andrei Lalaev wrote:
On 18.04.25 18:48, Jocelyn Falempe wrote:
On 32bits ARM, u64/u64 is not supported [1], so change the algorithm
to use a simple fifo with decimal digits as u8 instead.
This is slower but should compile on all architecture.
Link:
https://lore.kernel.org/
On Tue, 24 Jun 2025 10:20:48 +0200
"Benno Lossin" wrote:
> On Tue Jun 24, 2025 at 7:34 AM CEST, Onur wrote:
> > Should we handle this in the initial implementation or leave it for
> > follow-up patches after the core abstraction of ww_mutex has landed?
>
> Since you're writing these abstractions
On 6/24/25 4:21 AM, Thomas Zimmermann wrote:
Am 23.06.25 um 20:47 schrieb Mario Limonciello:
From: Mario Limonciello
The x86 specific check for whether a framebuffer belongs to a device
works for display devices as well as VGA devices. Callers to
video_is_primary_device() can benefit from c
On 19.06.25 14:15, Thomas Zimmermann wrote:
> Instead of testing import_attach for imported GEM buffers, invoke
> drm_gem_is_imported() to do the test.
>
> Signed-off-by: Thomas Zimmermann
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 2 +-
> drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
On Tue, 24 Jun 2025 at 12:57, Yongxing Mou wrote:
>
>
>
> On 2025/6/19 19:33, Dmitry Baryshkov wrote:
> > [initially I responded off-list by mistake, sorry for the confusion and
> > possible duplicates]
> >
> > On 19/06/2025 12:26, Yongxing Mou wrote:
> >>
> >>
> >> On 2025/6/16 22:41, Dmitry Bary
The GPU hard reset sequence calls pm_runtime_force_suspend() and
pm_runtime_force_resume(), which according to their documentation should
only be used during system-wide PM transitions to sleep states.
The main issue though is that depending on some internal runtime PM
state as seen by pm_runtime_
On Fri, Jun 20, 2025 at 01:18:18PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> An earlier patch fixed a build failure with clang, but I still see the
> same problem with some configurations using gcc:
>
> drivers/gpu/drm/i915/i915_pmu.c: In function 'config_mask':
> include/linux/compi
On Sat, 2025-06-21 at 16:05 +0200, Lukas Wunner wrote:
> On Sat, Jun 21, 2025 at 03:51:44PM +0200, Ben Hutchings wrote:
> > On Sat, 2025-06-21 at 14:29 +0200, Lukas Wunner wrote:
> > > On Sat, Jun 21, 2025 at 02:07:40PM +0200, Ben Hutchings wrote:
> > > > On Sat, 2025-06-21 at 11:40 +0200, Lukas Wu
From: Taotao Chen
Change the address_space_operations callbacks write_begin() and
write_end() to take struct kiocb * as the first argument instead of
struct file *.
Update all affected function prototypes, implementations, call sites,
and related documentation across VFS, filesystems, and block
From: Taotao Chen
Set the FOP_DONTCACHE flag in ext4_file_operations to indicate that
ext4 supports IOCB_DONTCACHE handling in buffered write paths.
Part of a series refactoring address_space_operations write_begin and
write_end callbacks to use struct kiocb for passing write context and
flags.
On Tue, Jun 24, 2025 at 11:22:25PM +0200, Beata Michalska wrote:
> With the Opaque, the expectations are that Rust should not
> make any assumptions on the layout or invariants of the wrapped
> C types. That runs rather counter to ioctl arguments, which must
> adhere to certain data-layout constrai
Am 23.06.25 um 20:47 schrieb Mario Limonciello:
From: Mario Limonciello
When compiled without CONFIG_VIDEO the architecture specific
implementations of video_is_primary_device() include prototypes and
assume that video-common.c will be linked. Guard against this so that the
fallback inline i
From: Rob Clark
[ Upstream commit f681c2aa8676a890eacc84044717ab0fd26e058f ]
put_unused_fd() doesn't free the installed file, if we've already done
fd_install(). So we need to also free the sync_file.
Signed-off-by: Rob Clark
Patchwork: https://patchwork.freedesktop.org/patch/653583/
Signed-o
From: Mario Limonciello
When compiled without CONFIG_VIDEO the architecture specific
implementations of video_is_primary_device() include prototypes and
assume that video-common.c will be linked. Guard against this so that the
fallback inline implementation that returns false will be used when
co
From: Mario Limonciello
The inline pci_is_display() helper does the same thing. Use it.
Reviewed-by: Lu Baolu
Reviewed-by: Daniel Dadap
Reviewed-by: Simona Vetter
Suggested-by: Bjorn Helgaas
Signed-off-by: Mario Limonciello
---
drivers/iommu/intel/iommu.c | 2 +-
1 file changed, 1 inserti
On Tue, Jun 24, 2025 at 04:23:31PM +0200, Christian König wrote:
> On 24.06.25 16:03, Riana Tauro wrote:
> > Hi Christian
> >
> > On 6/24/2025 5:56 PM, Christian König wrote:
> >> On 23.06.25 12:01, Riana Tauro wrote:
> >>> A device is declared wedged when it is non-recoverable from
> >>> the driv
On Tue, Jun 24, 2025 at 05:14:25PM -0400, Rodrigo Vivi wrote:
> On Fri, Jun 20, 2025 at 01:36:38PM +0200, Arnd Bergmann wrote:
> > From: Arnd Bergmann
> >
> > The igt_vma_pin1() function has a rather high stack usage, which gets
> > in the way of reducing the default warning limit:
> >
> > In fi
On Tue, Jun 24, 2025 at 05:11:50PM -0400, Rodrigo Vivi wrote:
> On Fri, Jun 20, 2025 at 01:18:18PM +0200, Arnd Bergmann wrote:
While merging this I adjusted the subject to be drm/i915
> > From: Arnd Bergmann
> >
> > An earlier patch fixed a build failure with clang, but I still see the
> > same
On Tue, Jun 24, 2025 at 01:20:51PM +0200, Danilo Krummrich wrote:
> On Tue, Jun 24, 2025 at 01:09:12PM +0200, Beata Michalska wrote:
> > On Tue, Jun 24, 2025 at 11:59:25AM +0200, Danilo Krummrich wrote:
> > > On 6/24/25 11:32 AM, Beata Michalska wrote:
> > > > From: Danilo Krummrich
> > > >
> > >
With the Opaque, the expectations are that Rust should not
make any assumptions on the layout or invariants of the wrapped
C types. That runs rather counter to ioctl arguments, which must
adhere to certain data-layout constraits. By using Opaque,
ioctl handlers are forced to use unsafe code where n
On Fri, Jun 20, 2025 at 01:36:38PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> The igt_vma_pin1() function has a rather high stack usage, which gets
> in the way of reducing the default warning limit:
>
> In file included from drivers/gpu/drm/i915/i915_vma.c:2285:
> drivers/gpu/drm/i91
Include to declare struct of_count_phandle_with_args().
Avoids dependency on backlight header to include it.
Signed-off-by: Thomas Zimmermann
---
drivers/video/backlight/led_bl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/video/backlight/led_bl.c b/drivers/video/backlight/led_b
Hi,
On Mon, Jun 23, 2025 at 9:48 PM Jayesh Choudhary wrote:
>
> By default, HPD was disabled on SN65DSI86 bridge. When the driver was
> added (commit "a095f15c00e27"), the HPD_DISABLE bit was set in pre-enable
> call which was moved to other function calls subsequently.
> Later on, commit "c312b0
From: Mario Limonciello
This series started out as changes to VGA arbiter to try to handle a case
of a system with 2 GPUs that are not VGA devices [1]. This was discussed
but decided not to overload the VGA arbiter for non VGA devices.
Instead move the x86 specific detection of framebuffer reso
From: Mario Limonciello
vga_is_firmware_default() checks firmware resources to find the owner
framebuffer resources to find the firmware PCI device. This is an
open coded implementation of screen_info_pci_dev(). Switch to using
screen_info_pci_dev() instead.
Suggested-by: Thomas Zimmermann
Si
From: Mario Limonciello
On systems with multiple GPUs there can be uncertainty which GPU is the
primary one used to drive the display at bootup. In order to disambiguate
this add a new sysfs attribute 'boot_display' that uses the output of
video_is_primary_device() to populate whether a PCI devic
From: Mario Limonciello
The inline pci_is_display() helper does the same thing. Use it.
Reviewed-by: Daniel Dadap
Reviewed-by: Simona Vetter
Suggested-by: Bjorn Helgaas
Signed-off-by: Mario Limonciello
---
drivers/gpu/vga/vga_switcheroo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
imple_parse_panel_timing_node(dev, panel, &dt);
- }
if (desc->connector_type == DRM_MODE_CONNECTOR_LVDS) {
/* Optional data-mapping property for overriding bus format */
---
base-commit: 10357824151262636fda879845f8b64553541106
change-id: 20250624-b4-simple-panel-regression-8ae3ba282fe2
Best regards,
--
Anusha Srivatsa
From: Taotao Chen
Replace the write_begin/write_end loop in
i915_gem_object_create_shmem_from_data() with call to kernel_write().
This function initializes shmem-backed GEM objects. kernel_write()
simplifies the code by removing manual folio handling.
Part of a series refactoring address_space_
On Tue, Jun 24, 2025 at 11:59:25AM +0200, Danilo Krummrich wrote:
> On 6/24/25 11:32 AM, Beata Michalska wrote:
> > From: Danilo Krummrich
> >
> > Following the removal of `Opaque` for ioctl arguments in the DRM
> > framework, this patch updates the affected driver code to use typed
> > reference
On Tue, 2025-06-24 at 15:01 -0400, M Henning wrote:
> We did no such error checking before this series (in fact, most of
> these options have almost no error checking). Are you saying you want
> to see this added in this patch series?
You have a good point, but I think your change, in effect, nece
add support to add a directory for each client-id
with root at the dri level. Since the clients are
unique and not just related to one single drm device,
so it makes more sense to add all the client based
nodes with root as dri.
Also create a symlink back to the parent drm device
from each client.
On Thu, Jun 19, 2025 at 9:19 PM Anusha Srivatsa wrote:
> Put the panel reference returned by of_drm_find_panel()
> back when driver is no longer using it.
>
> Signed-off-by: Anusha Srivatsa
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
On Tue, Jun 24, 2025 at 1:28 PM Timur Tabi wrote:
> Instead of removing it, I think we should rename it to indicate whether
> GSP-RM is required. You
> cannot boot Ada or later without GSP-RM, so on those platforms,
> nouveau.config=NvGspRm=0 should be
> ignored, and a pr_warn should be issued
Hello Tomi,
On 18/06/25 15:29, Tomi Valkeinen wrote:
While trying to get the cdns-dsi to work on Toradex's AM69 Aquila
platform, I hit multiple issues in the driver. Basicaly nothing worked
for with the board.
This series fixes those issues. While I itch to make much larger changes
to the cdns-
Make the header self contained for including.
Signed-off-by: Thomas Zimmermann
---
include/linux/fbcon.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/include/linux/fbcon.h b/include/linux/fbcon.h
index 2382dec6d6ab..81f0e698acbf 100644
--- a/include/linux/fbcon.h
+++ b/include/linu
Include to avoid dependency on backlight header to
include it.
Signed-off-by: Thomas Zimmermann
---
drivers/video/backlight/backlight.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/video/backlight/backlight.c
b/drivers/video/backlight/backlight.c
index 9dc93c5e480b..1e9b7e85d99a
On Mon, 2025-06-23 at 18:04 -0400, Mel Henning wrote:
> diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/priv.h
> b/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/priv.h
> index 4f14e85fc69e..c3494b7ac572 100644
> --- a/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/priv.h
> +++ b/drivers/gpu/drm/nouveau/nvk
On 2025-06-18 3:02 pm, Kaustabh Chakraborty wrote:
Since bcb81ac6ae3c (iommu: Get DT/ACPI parsing into the proper probe path),
The Samsung Exynos 7870 DECON device (with patches [1], [2], and [3]) seems
to not work anymore. Upon closer inspection, I observe that there is an
IOMMU crash.
[2.9
From: Taotao Chen
This patch series refactors the address_space_operations write_begin()
and write_end() callbacks to take struct kiocb * as their first argument,
allowing IOCB flags such as IOCB_DONTCACHE to propagate to filesystem’s
buffered write path.
Ext4 is updated to implement handling of
From: Taotao Chen
Add support for the IOCB_DONTCACHE flag in ext4_write_begin() and
ext4_da_write_begin(). When set in the kiocb, the FGP_DONTCACHE bit
is passed to the page cache lookup, preventing written pages from
being retained in the cache.
Only the handling logic is implemented here; the
On Wednesday, 18 June 2025 14:16:42 Central European Summer Time Thomas
Zimmermann wrote:
> Include to declare struct of_device_id.
> Avoids dependency on backlight header to include it.
>
> Signed-off-by: Thomas Zimmermann
> ---
> drivers/video/backlight/ktd2801-backlight.c | 1 +
> 1 file ch
On 2025-06-06 7:28 am, Tomeu Vizoso wrote:
The NPU cores have their own access to the memory bus, and this isn't
cache coherent with the CPUs.
Add IOCTLs so userspace can mark when the caches need to be flushed, and
also when a writer job needs to be waited for before the buffer can be
accessed
On Tue, Jun 24, 2025 at 10:02:41AM -0500, Ian Forbes wrote:
> On Mon, Jun 23, 2025 at 5:35 PM Colin Ian King wrote:
> >
> > The assignment to ts is missing on the call to ktime_to_timespec64.
> > Fix this by adding the missing assignment.
> >
> > Fixes: db6a94b26354 ("drm/vmwgfx: Implement dma_fen
Applied. Thanks!
On Tue, Jun 24, 2025 at 11:27 AM André Almeida wrote:
>
> Hi Alex,
>
> Em 16/06/2025 03:59, Christian König escreveu:
> > Acked-by: Christian König for the series.
> >
>
> Can you add this series to amd-staging-drm-next? Thanks!
>
> > On 6/13/25 20:26, André Almeida wrote:
> >>
Hi,
On Tue, Jun 24, 2025 at 04:40:43PM +0200, Bartosz Golaszewski wrote:
> On Tue, Jun 24, 2025 at 4:10 PM Bartosz Golaszewski wrote:
> >
> > From: Bartosz Golaszewski
> >
> > Here's an immutable tag containing the thead 1520 power sequencing driver
> > for the drm and pmdomain trees to pull fro
On Tue, Jun 24, 2025 at 03:27:54PM +, Alice Ryhl wrote:
> Since commit b20fbbc08a36 ("rust: check type of `$ptr` in
> `container_of!`") we have enforced that the field pointer passed to
> container_of! must match the declared field. This caused mismatches when
> using a pointer to bindings::x f
Since commit b20fbbc08a36 ("rust: check type of `$ptr` in
`container_of!`") we have enforced that the field pointer passed to
container_of! must match the declared field. This caused mismatches when
using a pointer to bindings::x for fields of type Opaque.
This situation encourages the user to sim
On Tue, Jun 24, 2025 at 04:36:35PM +0100, Greg KH wrote:
> On Tue, Jun 24, 2025 at 04:27:21PM +0300, Dmitry Baryshkov wrote:
> > On Thu, Jun 19, 2025 at 10:40:26AM +0530, Ekansh Gupta wrote:
> > > During rpmsg_probe, fastrpc device nodes are created first, then
> > > channel specific resources are
Since commit b20fbbc08a36 ("rust: check type of `$ptr` in
`container_of!`") we have enforced that the field pointer passed to
container_of! must match the declared field. This caused mismatches when
using a pointer to bindings::x for fields of type Opaque.
This situation encourages the user to sim
On 6/24/25 5:27 PM, Alice Ryhl wrote:
Since commit b20fbbc08a36 ("rust: check type of `$ptr` in
`container_of!`") we have enforced that the field pointer passed to
container_of! must match the declared field. This caused mismatches when
using a pointer to bindings::x for fields of type Opaque.
T
In the previous patch we added Opaque::cast_from() that performs the
opposite operation to Opaque::raw_get(). For consistency with this
naming, rename raw_get() to cast_from().
There are a few other options such as calling cast_from() something
closer to raw_get() rather than renaming this method.
Hi Raag,
Can you give me a Reviewed-by/Acked-by for this series before I push to
drm-misc-next?
Em 19/06/2025 11:06, André Almeida escreveu:
Fix the following warning:
Documentation/gpu/drm-uapi.rst:450: WARNING: Title underline too short.
Task information
--- [docutils]
Fixes:
On Mon, Jun 16, 2025 at 11:54 AM Biju Das wrote:
>
>
>
> > -Original Message-
> > From: Lad, Prabhakar
> > Sent: Monday, June 16, 2025 11:48 AM
> > To: Biju Das
> > Cc: Geert Uytterhoeven ; Andrzej Hajda
> > ; Neil Armstrong ;
> > Robert Foss ; laurent.pinchart
> > ; Jonas Karlman ;
> >
On 6/24/2025 12:42 AM, Werner Sembach wrote:
Hi Mario,
Am 23.06.25 um 21:42 schrieb Limonciello, Mario:
On 6/23/25 2:13 PM, Rodrigo Siqueira wrote:
On 06/23, Werner Sembach wrote:
gentle bump
Am 09.04.25 um 18:27 schrieb Werner Sembach:
The display backlight on TUXEDO Polaris AMD Gen2 and G
The vaddr of the fbdev framebuffer is private to the struct
intel_fbdev, so this function is needed to access it for drm_panic.
Also the struct i915_vma is different between i915 and xe, so it
requires a few functions to access fbdev->vma->iomap.
Signed-off-by: Jocelyn Falempe
---
v2:
* Add int
Now that we have DBANC framework, remove the connector initialisation code
as that piece of code is not called if DRM_BRIDGE_ATTACH_NO_CONNECTOR flag
is used. Only TI K3 platforms consume this driver and tidss (their display
controller) has this flag set. So this legacy support can be dropped.
Fix
On Mon, Jun 23, 2025 at 5:35 PM Colin Ian King wrote:
>
> The assignment to ts is missing on the call to ktime_to_timespec64.
> Fix this by adding the missing assignment.
>
> Fixes: db6a94b26354 ("drm/vmwgfx: Implement dma_fence_ops properly")
> Signed-off-by: Colin Ian King
Was this caught by a
drm_panic draws in linear framebuffer, so it's easier to re-use the
current framebuffer, and disable tiling in the panic handler, to show
the panic screen.
This assumes that the alignment restriction is always smaller in
linear than in tiled.
It also assumes that the linear framebuffer size is alwa
From: Rob Clark
[ Upstream commit 5d319f75ccf7f0927425a7545aa1a22b3eedc189 ]
In error paths, we could unref the submit without calling
drm_sched_entity_push_job(), so msm_job_free() will never get
called. Since drm_sched_job_cleanup() will NULL out the
s_fence, we can use that to detect this ca
On 6/24/25 4:47 AM, Werner Sembach wrote:
>
> Am 24.06.25 um 07:45 schrieb Mario Limonciello:
>> On 6/24/2025 12:42 AM, Werner Sembach wrote:
>>> Hi Mario,
>>>
>>> Am 23.06.25 um 21:42 schrieb Limonciello, Mario:
On 6/23/25 2:13 PM, Rodrigo Siqueira wrote:
> On 06/23, Werner Sembach wrote
On 24.06.25 16:03, Riana Tauro wrote:
> Hi Christian
>
> On 6/24/2025 5:56 PM, Christian König wrote:
>> On 23.06.25 12:01, Riana Tauro wrote:
>>> A device is declared wedged when it is non-recoverable from
>>> the driver context.
>>
>> Well, not quite.
>
> i took this from the below document. Sh
On 23/06/2025 12:42, Michal Wilczynski wrote:
> Several RISC-V boards feature Imagination GPUs that are compatible with
> the PowerVR driver. An example is the IMG BXM-4-64 GPU on the Lichee Pi
> 4A board. This commit adjusts the driver's Kconfig dependencies to allow
> the PowerVR driver to be com
Am 23.06.25 um 20:47 schrieb Mario Limonciello:
From: Mario Limonciello
The x86 specific check for whether a framebuffer belongs to a device
works for display devices as well as VGA devices. Callers to
video_is_primary_device() can benefit from checking non-VGA display
devices.
Move the x8
From: Bartosz Golaszewski
Here's an immutable tag containing the thead 1520 power sequencing driver
for the drm and pmdomain trees to pull from.
Best Regards,
Bartosz Golaszewski
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43
1 - 100 of 173 matches
Mail list logo
