[PATCH v2 0/1] Mark xe driver as BROKEN if kernel page size is not 4kB

Hi, until either of - https://patchwork.freedesktop.org/series/150230/ or the (same but rebased) - https://patchwork.freedesktop.org/series/151983/ goes in, the xe module will Oops on insmod when kernel page size is not 4kB. This disables the module for the time being, and should be reverted

Re: [PATCH v2 0/1] MAINTAINERS: .mailmap: Update Hans de Goede's email address

On Mon, 09 Jun 2025 16:35:56 +0200, Hans de Goede wrote: > I'm moving all my kernel work over to using my kernel.org email address. > > The single patch in this series updates .mailmap and all MAINTAINERS > entries still using hdego...@redhat.com. > > Since most of my work is pdx86 related I bel

[PATCH v2 0/1] MAINTAINERS: .mailmap: Update Hans de Goede's email address

Hi All, I'm moving all my kernel work over to using my kernel.org email address. The single patch in this series updates .mailmap and all MAINTAINERS entries still using hdego...@redhat.com. Since most of my work is pdx86 related I believe it would be best for Ilpo to merge this through the pdx8

[PATCH v2 0/1] drm/amdgpu: Use device wedged event

Raag Jadav is introducing a new DRM API for generating "device wedged events", to notify userspace when the device needs userspace intervention after a GPU reset[1]. I did a simple patch to add support for it for amdgpu for the telemetry aspect of the event. Tested in Steam Deck. This patch require

[PATCH v2 0/1] Expose UCHE_TRAP_BASE value via uapi

Depends on https://patchwork.freedesktop.org/series/141667/ The parameter would be used in [1] to implement VK_KHR_shader_clock and GL_ARB_shader_clock. On at least a6xx+, shader could read 64b ALWAYSON counter from UCHE_TRAP_BASE+0 address. Downstream driver exposes uche trap base via uapi only

[PATCH v2 0/1] Maintenence of devcoredump <-> GuC-Err-Capture plumbing

The GuC-Error-Capture is currently reaching into xe_devcoredump structure to store its own place-holder snaphot to workaround the race between G2H-Error-Capture-Notification vs Drm-Scheduler triggering GuC-Submission-exec-queue-timeout/kill. Part of that race workaround design included GuC-Error-C

[PATCH v2 0/1] FOR-CI: drm/i915/guc: Move destroy context at end of reset prepare

During GuC reset prepare, interrupt disabled before hardware reset, although interrupt disabled, the ct is still enabled, the host-GuC communication is still active. Move the destroy part to the end of reset preparation to avoid the situation of host processing G2H messages about an context, but th

[PATCH v2 0/1] Use functionality of irq_get_trigger_type()

Changes in v2: - Split patches to subsystems - Add tag --- v1: https://lore.kernel.org/all/20240902225534.130383-1-vassilisa...@gmail.com/ Vasileios Amoiridis (1): drm/i2c: tda998x: Make use of irq_get_trigger_type() drivers/gpu/drm/i2c/tda998x_drv.c | 3 +-- 1 file changed, 1

[PATCH v2 0/1] video: Handle HAS_IOPORT dependencies

Hi, This is a follow up in my ongoing effort of making inb()/outb() and similar I/O port accessors compile-time optional. Previously I sent this as a treewide series titled "treewide: Remove I/O port accessors for HAS_IOPORT=n" with the latest being its 5th version[0]. With a significant subset of

[PATCH v2 0/1] drm: Add ioctl for querying a DRM device's list of open client PIDs

This is v2 of the patch being discussed at https://lore.kernel.org/dri-devel/20240403182951.724488-1-adrian.laru...@collabora.com/ In the original patch, a DRM device sysfs attribute file was chosen as the interface for fetching the list of active client PIDs. That came with a hosts of problems:

[PATCH v2 0/1] fbdev: Handle HAS_IOPORT dependencies

Hi Helge, This is a follow up in my ongoing effort of making inb()/outb() and similar I/O port accessors compile-time optional. Previously I sent this as a treewide series titled "treewide: Remove I/O port accessors for HAS_IOPORT=n" with the latest being its 5th version[0]. With a significant sub

[PATCH v2 0/1] Revert "drm/qxl: simplify qxl_fence_wait"

Changes since v1: - replace new code logic in v1 with past code version by reverting commit 5a838e5d5825 ("drm/qxl: simplify qxl_fence_wait") - add missing code dependency from commit d72277b6c37d ("dma-buf: nuke DMA_FENCE_TRACE macros v2") --- Hi, To clarify, the reason for my original patc

[PATCH v2 0/1] drm/bridge: it6505: fix hibernate to resume no display issue patch v2

From: kuro chung New patch description for v2 patch Missing declaration for i variable in function it6505_irq_video_error_handler , add it by this patch Origianl description for v1 patch drm/bridge: it6505: fix hibernate to resume no display issue ITE added a

[PATCH v2 0/1] drm/panfrost: Replace fdinfo's profiling debugfs knob

This is v2 of the patch already discussed in [1] Changelog: - Turned the profile mode atomic variable into a boolean - Rewrote the sysfs file's uAPI documentation to make it more generic - Improved the casting of the profiling variable inside the Panfrost device structure [1]https://lore.kern

[RESEND PATCH v2 0/1] drm/msm/adreno: Add support for SM7150

This patch adds support for SM7150 SoC machine. Reason for RESEND: The discussion was resolved. As far as I understand, everything remains unchanged. Let's make a RESEND for the patch so it doesn't get lost. - Link to v2: https://lore.kernel.org/all/20230926174243.161422-1-dan...@jiaxyga.com/ Cha

[PATCH v2 0/1] Filter modes according to hardware capability

From: Hsiao Chien Sung This series is based on mediatek-drm-next branch of kernel/git/chunkuang.hu/linux.git. Changes in v2: - Refined the filtering formula - Add the .mode_valid hook to the hardware that causes the limitation Hsiao Chien Sung (1): drm/mediatek: Filter modes according to hard

[PATCH v2 0/1] Implement device_attach for virtio gpu

To realize dGPU prime feature for virtio gpu, we are trying to let dGPU import vram object of virtio gpu. As vram objects don't have backing pages and thus can't implement the drm_gem_object_funcs.get_sg_table callback, this removes calling drm_gem_map_dma_buf in virtgpu_gem_map_dma_buf and impleme

[PATCH v2 0/1] drm/ttm: allocate dummy_read_page without DMA32 on fail

Some platforms may not have any memory below 4GB address space, but the kernel defines ZONE_DMA32 on their ISA. Thus, these platforms will have an empty DMA32 zone, resulting ttm failing when alloc_page with GFP_DMA32 flag. However, we can't directly allocate dummy_read_page without GFP_DMA32 as so

Re: [PATCH v2 0/1] Implementation of resource_query_layout

I see, I will implement this. Thank you very much. On 2023/12/27 09:29, Gurchetan Singh wrote: > > > On Thu, Dec 21, 2023 at 2:01 AM Julia Zhang > wrote: > > Hi all, > > Sorry to late reply. This is v2 of the implementation of > resource_query_layout. T

Re: [PATCH v2 0/1] Implementation of resource_query_layout

On Thu, Dec 21, 2023 at 2:01 AM Julia Zhang wrote: > Hi all, > > Sorry to late reply. This is v2 of the implementation of > resource_query_layout. This adds a new ioctl to let guest query information > of host resource, which is originally from Daniel Stone. We add some > changes to support query

[PATCH v2 0/1] Implementation of resource_query_layout

Hi all, Sorry to late reply. This is v2 of the implementation of resource_query_layout. This adds a new ioctl to let guest query information of host resource, which is originally from Daniel Stone. We add some changes to support query the correct stride of host resource before it's created, which

[PATCH v2 0/1] Fix errors when reporting rotation capability

This commit is based on 20231024130048.14749-1-shawn.s...@mediatek.com. This bug is found when running IGT tests. For CRTCs that doesn't support rotation should still return DRM_MODE_ROTATE_0. Returns the hardware capabilities accordingly. Changes in v2: - Restore DRM_MODE_ROTATE_180 (reflect x +

[PATCH v2 0/1] dt-bindings: backlight: mp3309c: remove two required properties

This patch remove the following two not-required properties from the "required" section: - max-brightness - default brightness These properties are not really required, so they can be removed from the "required" section. The "max-brightness" is no longer used in the current version of the driver

[RFC PATCH v2 0/1] fence per plane state

The patch "drm/virtio: new fence for every plane update" is to prevent a fence synchronization problem when multiple planes are referencing a single large FB (i.e. Xorg with multi displays configured as one extended surface.). One example of a possible problematic flow is 1.virtio_gpu_plane_prepa

[PATCH v2 0/1] drm/amdkfd: Fix unaligned doorbell absolute offset for gfx8

On older chips, the absolute doorbell offset within the doorbell page is based on the queue ID. KFD is using queue ID and doorbell size to get an absolute doorbell offset in userspace. This patch is to adjust the absolute doorbell offset against the doorbell id considering the doorbell size of 32/

[PATCH v2 0/1] drm/msm/adreno: Add support for SM7150

This patch adds support for SM7150 SoC machine. Changes in v2: - Use a630_gmu.bin instead of a618_gmu.bin. - Use squashed version of a615_zap (.mbn). - Drop .revn. - Link to v1: https://lore.kernel.org/all/20230913191957.26537-1-dan...@jiaxyga.com/ Danila Tikhonov (1): drm/msm/adreno: Add suppo

[PATCH v2 0/1] HID backlight driver

Complete rewrite of [1]. Instead of a USB driver it`s now a HID driver and will work without being part of the early boot environment. The driver is no longer heavily tied to the Apple Studio Display, but should work with all HID devices, that expose a report containing fields with the Monitor - B

Recall: [LINUX KERNEL PATCH v2 0/1] add S3 support for virtgpu

Chen, Jiqian would like to recall the message, "[LINUX KERNEL PATCH v2 0/1] add S3 support for virtgpu".

Re: [LINUX KERNEL PATCH v2 0/1] add S3 support for virtgpu

Hi all, V2 patch of kernel is https://lore.kernel.org/lkml/20230630073448.842767-1-jiqian.c...@amd.com/T/#t. On 2023/6/30 15:34, Jiqian Chen wrote: > v2: > > Hi all, > > Thanks to Marc-André Lureau, Robert Beckett and Gerd Hoffmann for > their advice and guidance. V2 makes below changes: > >

[LINUX KERNEL PATCH v2 0/1] add S3 support for virtgpu

v2: Hi all, Thanks to Marc-André Lureau, Robert Beckett and Gerd Hoffmann for their advice and guidance. V2 makes below changes: * Change VIRTIO_CPU_CMD_STATUS_FREEZING to 0x0400 (<0x1000) * Add a new feature flag VIRTIO_GPU_F_FREEZING, so that guest and host can negotiate whenever freezing is

[PATCH v2 0/1] drm: Add doc about GPU reset

Hi, Thanks everyone that gave feedback. v2 Changes: - This new version is a section of drm-uapi instead of a new file - Drop requirement for KMD to kill applications - Drop role of init systems on compositors recover - Drop assumption that robust apps creates new contexts Original cover letter be

[PATCH v2 0/1] drm/panel: st7703: Fix resume of XBD599 panel

This is V2 of a patch that fixes flickering after resume from sleep on panel xingbangda,xbd599 (e.g. used in PinePhone). Please see here for the discussion around V1: https://lore.kernel.org/all/20230212120830.46880-1-fr...@oltmanns.dev/T/ V1 introduced panel specific functions for the JH057N and

[PATCH v2 0/1] Fixup documentation for dsi-phy-28nm

This is the one remaining patch I had from a previous series for mdss-dsi-ctrl and the dsi-phy. The mdss-dsi-ctrl set became a bigger so I split out the 28nm phy fixes. I'm resubmitting with Dmitry's RB as a standalone. Old: https://lore.kernel.org/all/20220630120845.3356144-1-bryan.odonog...@li

[PATCH v2 0/1] Fix bug in version reduced firmware update

From: John Harrison The earlier patch to support firmware files with reduced versioning introduced an issue with the firmware override module parameter. So fix that. v2: Also remove ANSI colour codes that accidentally got left in an error message in the original patch. Signed-off-by: John Harri

Re: [EXT] Re: [PATCH v2 0/1] tee: Add tee_shm_register_fd

On Thu, 8 Sept 2022 at 14:48, Olivier Masse wrote: > > Hi Sumit > > On ven., 2022-08-19 at 13:54 +0530, Sumit Garg wrote: > > Caution: EXT Email > > > > Hi Olivier, > > > > On Fri, 12 Aug 2022 at 20:01, Olivier Masse > > wrote: > > > > > > Add a new ioctl called TEE_IOC_SHM_REGISTER_FD to registe

Re: [PATCH v2 0/1] tee: Add tee_shm_register_fd

Hi Daniel, On Wed, 7 Sept 2022 at 01:29, Daniel Vetter wrote: > > On Fri, Aug 19, 2022 at 01:54:31PM +0530, Sumit Garg wrote: > > Hi Olivier, > > > > On Fri, 12 Aug 2022 at 20:01, Olivier Masse wrote: > > > > > > Add a new ioctl called TEE_IOC_SHM_REGISTER_FD to register a > > > shared memory fr

Re: [EXT] Re: [PATCH v2 0/1] tee: Add tee_shm_register_fd

Hi Sumit On ven., 2022-08-19 at 13:54 +0530, Sumit Garg wrote: > Caution: EXT Email > > Hi Olivier, > > On Fri, 12 Aug 2022 at 20:01, Olivier Masse > wrote: > > > > Add a new ioctl called TEE_IOC_SHM_REGISTER_FD to register a > > shared memory from a dmabuf file descriptor. > > This new ioctl

Re: [PATCH v2 0/1] tee: Add tee_shm_register_fd

On Fri, Aug 19, 2022 at 01:54:31PM +0530, Sumit Garg wrote: > Hi Olivier, > > On Fri, 12 Aug 2022 at 20:01, Olivier Masse wrote: > > > > Add a new ioctl called TEE_IOC_SHM_REGISTER_FD to register a > > shared memory from a dmabuf file descriptor. > > This new ioctl will allow the Linux Kernel to

Re: [PATCH v2 0/1] tee: Add tee_shm_register_fd

Hi Olivier, On Fri, 12 Aug 2022 at 20:01, Olivier Masse wrote: > > Add a new ioctl called TEE_IOC_SHM_REGISTER_FD to register a > shared memory from a dmabuf file descriptor. > This new ioctl will allow the Linux Kernel to register a buffer > to be used by the Secure Data Path OPTEE OS feature. >

Re: [EXT] Re: [PATCH v2 0/1] tee: Add tee_shm_register_fd

Hi Jens, On mar., 2022-08-16 at 10:17 +0200, Jens Wiklander wrote: > Caution: EXT Email > > Hi Olivier, > > On Fri, Aug 12, 2022 at 4:31 PM Olivier Masse > wrote: > > > > Add a new ioctl called TEE_IOC_SHM_REGISTER_FD to register a > > shared memory from a dmabuf file descriptor. > > This new

Re: [PATCH v2 0/1] tee: Add tee_shm_register_fd

Hi Olivier, On Fri, Aug 12, 2022 at 4:31 PM Olivier Masse wrote: > > Add a new ioctl called TEE_IOC_SHM_REGISTER_FD to register a > shared memory from a dmabuf file descriptor. > This new ioctl will allow the Linux Kernel to register a buffer > to be used by the Secure Data Path OPTEE OS feature.

[PATCH v2 0/1] tee: Add tee_shm_register_fd

Add a new ioctl called TEE_IOC_SHM_REGISTER_FD to register a shared memory from a dmabuf file descriptor. This new ioctl will allow the Linux Kernel to register a buffer to be used by the Secure Data Path OPTEE OS feature. Please find more information here: https://static.linaro.org/connect/san19/

Re: [PATCH v2 0/1] dt-bindings: spi/display/panel: drop SPI CPHA and CPOL

On Fri, 22 Jul 2022 21:15:38 +0200, Krzysztof Kozlowski wrote: > Rebased on Linus' master > > Changes since v1 > > 1. Rework patchset as Rob suggested, so there is only one patch - changing spi >and display/panel. > v1: > https://lore.kernel.org/all/20220721153155.245336-2-kr

[PATCH v2 0/1] drm/msm/a6xx: Fix null pointer access in a6xx_get_indexed_registers

From: Devi prasad Dhamarasingi Fix a null pointer access when memory allocation fails in a6xx_get_indexed_registers(). Akhil P Oommen (1): drm/msm/a6xx: Fix null pointer access in a6xx_get_indexed_registers drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c | 6 ++ 1 file changed, 6 insertions(

[PATCH v2 0/1] dt-bindings: spi/display/panel: drop SPI CPHA and CPOL

Hi, Rebased on Linus' master Changes since v1 1. Rework patchset as Rob suggested, so there is only one patch - changing spi and display/panel. v1: https://lore.kernel.org/all/20220721153155.245336-2-krzysztof.kozlow...@linaro.org/ Merging === I guess via DT or SPI tree.

[PATCH v2 0/1] bridge/ti-sn65dsi86.c: convert to atomic operations

This patch is what is left on a previous attempt to make the ti-sn65dsi86 support DRM_BRIDGE_ATTACH_NO_CONNECTOR. I ran into several challenges on the way: - I never found a way to retreive bpc when the driver do not create the connector - and the driver needs it. There may be ways to change h

[PATCH v2 0/1] bridge/ti-sn65dsi86.c: convert to atomic operations

This patch is what is left on a previous attempt to make the ti-sn65dsi86 support DRM_BRIDGE_ATTACH_NO_CONNECTOR. I ran into several challenges on the way: - I never found a way to retreive bpc when the driver do not create the connector - and the driver needs it. There may be ways to change h

Re: [PATCH v2 0/1] bridge/ti-sn65dsi86.c: convert to atomic operations

(Dropping CC/lists) Quoting Sam Ravnborg (2022-07-03 21:27:23) > This patch is what is left on a previous attempt to make the > ti-sn65dsi86 support DRM_BRIDGE_ATTACH_NO_CONNECTOR. > > I ran into several challenges on the way: > - I never found a way to retreive bpc when the driver > do not cre

[PATCH v2 0/1] devcoredump support for Panfrost GPU driver

This is v2 for a previous patch series being discussed at https://lore.kernel.org/dri-devel/20220517174216.381287-1-adrian.laru...@collabora.com/. Mesa MR under review can be found at: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14034 Changes with respect to v1 of the same patch:

[PATCH v2 0/1] Drop wbinvd_on_all_cpus usage

To align with the discussion in [1][2], this patch series drops all usage of wbvind_on_all_cpus within i915 by either replacing the call with certain drm clflush helpers, or reverting to a previous logic.

[PATCH v2 0/1]

To align with the discussion in [1][2], this patch series drops all usage of wbvind_on_all_cpus within i915 by either replacing the call with certain drm clflush helpers, or reverting to a previous logic.

[PATCH v2 0/1] Fix i915 error_state_read ptr use

Fix pointer offset usage in error_state_read when there is no i915_gpu_coredump but buf offset is non-zero. This is the 2nd rev of this series. Changes from prior revs: v2: - Fix build issue: uninitialized var Reported-by: kernel test robot Alan Previn (1): drm/i915/reset: Fix error

[PATCH v2 0/1] Add fallback inside memcpy_from_wc functions

Fallback function implemented inside memcpy_from_wc functions when copying using accelerated read is not possible. v2: Fixed Sparse warnings Balasubramani Vivekanandan (1): drm/i915: Add fallback inside memcpy_from_wc functions drivers/gpu/drm/i915/gem/i915_gem_object.c | 5 +- drivers/gpu/d

[PATCH v2 0/1] drm/lsdc: add drm driver for loongson display controller

v2: fixup warnings reported by kernel test robot There is a display controller in loongson's LS2K1000 SoC and LS7A1000 bridge, and the DC in those chip is a PCI device. This display controller have two display pipes but with only one hardware cursor. This display controller is uncommon outside of

[PATCH v2 0/1] drm/vkms: zpos

Hi all, This patch adds support for the zpos plane prop in the VKMS driver. It should be applied after the "drm/vkms: add support for multiple overlay planes" series [1] because this new patch takes advantage of the new constant "NUM_OVERLAY_PLANES" to set the maximum overlay plane zpos. Notice

[PATCH v2 0/1] drm/i915/rpm: Enable runtime pm autosuspend by default

Enable runtime pm autosuspend by default for all platforms Signed-off-by: Tilak Tangudu Tilak Tangudu (1): drm/i915/rpm: Enable runtime pm autosuspend by default drivers/gpu/drm/i915/intel_runtime_pm.c | 3 +++ 1 file changed, 3 insertions(+) -- 2.25.1

[PATCH v2, 0/1] mailbox: cmdq: add instruction time-out interrupt support

Base v5.15 Yongqiang Niu (1): mailbox: cmdq: add instruction time-out interrupt support drivers/mailbox/mtk-cmdq-mailbox.c | 11 +++ 1 file changed, 11 insertions(+) -- 2.25.1

[RFC PATCH v2 0/1] Providers/rxe: Add dma-buf support

This is an user space counter-part of the kernel patch set to add dma-buf support to the RXE driver. Pull request at GitHub: https://github.com/linux-rdma/rdma-core/pull/1055 This is the secound version of the patch. Change log: v2: * Fix code formats that were indicated by Azure CI v1: https://w

[PATCH v2 0/1] lib, stackdepot: Add helper to print stack entries into buffer.

Changes in v2: - Addressed review comment. - Added Acked from Vlastimil. - Fixed one mistake, due to which stack_trace_snprint was always getting invoked with 0 as space value. Changed it to make use of space argument, because users that are printing stack entries into buffer, may

[PATCH v2 0/1] Fix cursor plane didn't update

Change in v2: Fix typo in patch message. jason-jh.lin (1): Fix cursor plane didn't update drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 1 - drivers/gpu/drm/mediatek/mtk_drm_plane.c | 60 ++-- 2 files changed, 34 insertions(+), 27 deletions(-) -- 2.18.0

[PATCH v2 0/1] drm/dp_mst: Use kHz as link rate units when settig source max link caps at init

Change log: v2: - Added 'Acked-by' to comment v1: - Initial Nikola Cornij (1): drm/dp_mst: Use kHz as link rate units when settig source max link caps at init .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 4 ++-- drivers/gpu/drm/drm_dp_mst_topology.c

[PATCH v2 0/1] drm/mediatek: Remove redundant error printing

v1 --> v2: 1. Combine the modifications of several drm/mediatek files into one patch. 2. According to Baruch Siach's review comment, simplify the following code snippets: -ret = PTR_ERR(cec->regs); -return ret; +return PTR_ERR(cec->regs); Zhen Lei (1):

Re: [PATCH v2 0/1] drm/msm/dpu: Fix error return code in dpu_mdss_init()

On 10/05/2021 04:16, Zhen Lei wrote: v1 --> v2: According to Anton Ivanov's review comments, detele the unnecessary local variable initialization "ret = 0". Zhen Lei (1): drm/msm/dpu: Fix error return code in dpu_mdss_init() drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 8 +--- 1 file c

[PATCH v2 0/1] drm/msm/dpu: Fix error return code in dpu_mdss_init()

v1 --> v2: According to Stephen Boyd's review comments, detele the unnecessary local variable initialization "ret = 0". Zhen Lei (1): drm/msm/dpu: Fix error return code in dpu_mdss_init() drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) -

Re: [PATCH v2 0/1] drm/msm/dpu: Fix error return code in dpu_mdss_init()

On 2021/5/10 14:01, Anton Ivanov wrote: > On 10/05/2021 04:16, Zhen Lei wrote: >> v1 --> v2: >> According to Anton Ivanov's review comments, detele the unnecessary local >> variable initialization "ret = 0". >> >> >> Zhen Lei (1): >>    drm/msm/dpu: Fix error return code in dpu_mdss_init() >> >>

[PATCH v2 0/1] drm/msm/dpu: Fix error return code in dpu_mdss_init()

v1 --> v2: According to Anton Ivanov's review comments, detele the unnecessary local variable initialization "ret = 0". Zhen Lei (1): drm/msm/dpu: Fix error return code in dpu_mdss_init() drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) -

[PATCH v2 0/1] drm/i915: Use the correct max source link rate for MST

This is a follow-up change to fix incorrectly used max link rate source capability at MST init time. Change history: v1: - Initial v2: - Use local variabale for improved code readability - Fix the comment to point to the correct sub-directory Nikola Cornij (1): drm/i915: Use the correc

[PATCH v2 0/1] Document drm_mode_get_plane

This is a follow up of the patchset "Document how userspace should use plane format list and IN_FORMATS": https://lists.freedesktop.org/archives/dri-devel/2021-April/302433.html The first patch of the series ("drm/doc: document drm_mode_get_plane") is still useful, although the other commit of th

[PATCH v2 0/1] drm/nouveau/dmem: Remove duplicated header file

v1 --> v2: Arrange all included header files in alphabetical order. Zhen Lei (1): drm/nouveau/dmem: Remove duplicated header file inclusion drivers/gpu/drm/nouveau/nouveau_dmem.c | 27 --- 1 file changed, 12 insertions(+), 15 deletions(-) -- 1.8.3 _

[PATCH v2 0/1] Fixes 30e2ae943c26 "drm/bridge: Introduce LT8912B DSI to HDMI"

Hi, This patch fixes issues found by a static checker. Thanks, Adrien Grassein (1): drm/bridge: lt8912b: Fix issues found during static analysis drivers/gpu/drm/bridge/lontium-lt8912b.c | 24 +++- 1 file changed, 15 insertions(+), 9 deletions(-) -- 2.25.1 _

[PATCH v2 0/1] dt-bindings: display: eliminate yamllint warnings

This patch is based on the latest linux-next code. v1 --> v2: Extract the modification of the Documentation/devicetree/bindings/display/ parts and send the patch separately. https://www.spinics.net/lists/arm-kernel/msg860713.html v1: There're too many people, I just send to the maintainer, revi

[PATCH v2 0/1] dt-bindings: fix warning in panel/advantech, idk-2121wr

The binding for the advantech,idk-2121wr uses an example where a ports {} node is used. The panel-lvds binding failed to support a ports node, which the following patch fixes. This fix was part of a longer series, but we need this fix in upstream before -rc2. So pull this out of the larger series

[PATCH v2 0/1] Regression in analogix_anx78xx

commit ff1e8fb68ea0 ("drm/bridge: analogix-anx78xx: Avoid drm_dp_link helpers") stores the max link rate in a u8, overflowing it. This will probably prevent the link training from working. I've not tested this patch beyond a simple compile test since I do not own any devices containing an anx78xx.

[PATCH v2 0/1] Take SST-only branch device into account

Noticed this while testing 4 ports MST hub from StarTech.com. While plugging in and display a MST monitor(Dell U2417H), change the MST feature to off from OSD. Monitor then can't display anymore. After analyzing, found out that the CSN reports the specific port from Device with MST Branching Unit

[PATCH v2 0/1] Regression in rockchipdrm

commit 2589c4025f13 ("drm/rockchip: Avoid drm_dp_link helpers") changed the datatype used for storing the display port data rate to u8. A u8 is not sufficient to store the data rate, resulting in a crash due to incorrect calculations. This series resolves the issue by restoring the data type chang

[PATCH v2 0/1] drm/syncobj: add syncobj sideband payload for threaded submission

Hi all, Just a single patch this time with a new ioctl. Cheers, Lionel Landwerlin (1): drm/syncobj: add sideband payload drivers/gpu/drm/drm_internal.h | 2 ++ drivers/gpu/drm/drm_ioctl.c| 3 ++ drivers/gpu/drm/drm_syncobj.c | 63 +++--- include/drm/drm_syn

[PATCH v2 0/1] drm/exynos: drop use of drmP.h

Drop the use of the deprecated drmP.h header file. Build tested using allyesconfig, allmodconfig for various architectures. v2: - add missing people to recipient list of mail - no change in actual patch Sam Sam Ravnborg (1): drm/exynos: drop drmP.h usage drivers/gpu/drm/exynos/e

[PATCH v2 0/1] Stop users from using the device on driver unbind

Use drm_dev_unplug() to have device resources protected from user access by DRM layer as soon as the driver is going to be unbound. Janusz Krzysztofik (1): drm/i915: Use drm_dev_unplug() drivers/gpu/drm/i915/i915_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Since this patch sho

[PATCH v2 0/1] drm/msm/a6xx: Add interconnect support

This is an updated version of [1] adding interconnect support without OPP bindings to get maximum performance from the GPU. Big delta here is that I stupidly confused Bps and KBps and passed a value that overflowed the API. Correct bandwidth values are now passed. [1] https://lists.freedesktop.or

[PATCH v2 0/1] fbdev/core: Disable console-lock warnings when fb.lockless_register_fb is set

Hi, this is a follow-up patch for the recent addition of 'ignore_console_lock_warning' to the console module [1] and should probably go through the same tree. When debugging fbdev console registration, the console-lock warnings will now be disabled temporarily. Best regards Thomas [1] https://ma

[RFC PATCH v2 0/1] Fix drm driver hang on tegra124-nyan-big

This patch was initially sent along with another one to fix a first hang in the nouveau drm driver[1]. I'm now sending it again as a separate patch as it's to fix a second hang which is not strictly related. It is hidden by the first hang though, as this happens later on during the driver initial

[PATCH v2 0/1] Split VGA default nomination out from VGA arbiter

This is approach 3, version 2, of my patch series to sort out Xorg autoconfiguration for the Hibmc card beind a Hisilicon bridge on arm64. Approach 1 was a simple quirk for the card+bridge to mark it as default. This higlighted the fact that the default card was picked by the arbiter, which assume

[PATCH v2 0/1] apple-gmux: Add initial documentation

Hi Darren, On Mon, Jan 11, 2016 at 09:45:25AM -0800, Darren Hart wrote: > On Mon, Jan 11, 2016 at 08:03:18AM +0100, Daniel Vetter wrote: > > On Mon, Jan 11, 2016 at 12:08:35AM +0100, Lukas Wunner wrote: > > > On Fri, Jan 08, 2016 at 09:49:22AM -0700, Jonathan Corbet wrote: > > > > Well, it's built

[PATCH v2 0/1] apple-gmux: Add initial documentation

On Mon, Jan 11, 2016 at 02:07:15PM +0100, Lukas Wunner wrote: > Hi Daniel, > > On Mon, Jan 11, 2016 at 08:03:18AM +0100, Daniel Vetter wrote: > > On Mon, Jan 11, 2016 at 12:08:35AM +0100, Lukas Wunner wrote: > > > Here's a v2, the only change is Bruno Pr?mont's addition to the commit > > > message

[PATCH v2 0/1] apple-gmux: Add initial documentation

Hi Daniel, On Mon, Jan 11, 2016 at 08:03:18AM +0100, Daniel Vetter wrote: > On Mon, Jan 11, 2016 at 12:08:35AM +0100, Lukas Wunner wrote: > > Here's a v2, the only change is Bruno Pr?mont's addition to the commit > > message. > > > > @Daniel Vetter: Could you pick this up for topic/drm-misc pleas

[PATCH v2 0/1] apple-gmux: Add initial documentation

On Mon, Jan 11, 2016 at 08:19:54PM +0100, Lukas Wunner wrote: > Hi Darren, > > On Mon, Jan 11, 2016 at 09:45:25AM -0800, Darren Hart wrote: > > On Mon, Jan 11, 2016 at 08:03:18AM +0100, Daniel Vetter wrote: > > > On Mon, Jan 11, 2016 at 12:08:35AM +0100, Lukas Wunner wrote: > > > > On Fri, Jan 08,

[PATCH v2 0/1] apple-gmux: Add initial documentation

On Mon, Jan 11, 2016 at 08:03:18AM +0100, Daniel Vetter wrote: > On Mon, Jan 11, 2016 at 12:08:35AM +0100, Lukas Wunner wrote: > > On Fri, Jan 08, 2016 at 09:49:22AM -0700, Jonathan Corbet wrote: > > > Well, it's built around the asciidoc patch, which isn't in the mainline > > > at this point. Sho

[PATCH v2 0/1] apple-gmux: Add initial documentation

On Mon, Jan 11, 2016 at 12:08:35AM +0100, Lukas Wunner wrote: > On Fri, Jan 08, 2016 at 09:49:22AM -0700, Jonathan Corbet wrote: > > Well, it's built around the asciidoc patch, which isn't in the mainline > > at this point. Should things go a different direction, that could force > > some changes

[PATCH v2 0/1] apple-gmux: Add initial documentation

On Fri, Jan 08, 2016 at 09:49:22AM -0700, Jonathan Corbet wrote: > Well, it's built around the asciidoc patch, which isn't in the mainline > at this point. Should things go a different direction, that could force > some changes here; If/when that happens, I'll be happy to fixup the documentation

[PATCH v2 0/1] drm: modes: fix DRM modes analysis regression

Hello Changes since v1 - Fix a memory leak when returning after an error of kstrtox LABBE Corentin (1): drm: modes: fix DRM modes analysis regression drivers/gpu/drm/drm_modes.c | 28 +--- 1 file changed, 21 insertions(+), 7 deletions(-) -- 2.4.10

[PATCH v2 0/1] drm/mgag200: Added resolution and bandwidth limits for various G200e products.

I am resubmitting this patch because I ran into a build error when trying to build it on a 32-bit system. I had to fix how the 64-bit division was done in mga_vga_calculate_mode_bandwidth. I used the do_div macro instead of doing the straight division. Julia Lemire (1): drm/mgag200: Added r

[PATCH v2 0/1] drm/mgag200: Added resolution and bandwidth limits for various G200e products.

I am resubmitting this patch because I ran into a build error when trying to build it on a 32-bit system. I had to fix how the 64-bit division was done in mga_vga_calculate_mode_bandwidth. I used the do_div macro instead of doing the straight division. Julia Lemire (1): drm/mgag200: Added r

[PATCH v2 0/1] Adds display-timing node parsing to exynos drm fimd

Hi Vikas, Changelog mentioning differences between v1 and v2 is generally preferred as it will help the reviewers. On 30 January 2013 12:00, Vikas Sajjan wrote: > This patch adds display-timing node parsing to drm fimd, this depends on > the display helper patchset at > http://lists.freedesktop.

[PATCH v2 0/1] Adds display-timing node parsing to exynos drm fimd

This patch adds display-timing node parsing to drm fimd, this depends on the display helper patchset at http://lists.freedesktop.org/archives/dri-devel/2013-January/033998.html It also adds pinctrl support for drm fimd. patch is based on branch "exynos-drm-next" at http://git.kernel.org/pub/scm/l

Re: [PATCH v2 0/1] Adds display-timing node parsing to exynos drm fimd

Hi Vikas, Changelog mentioning differences between v1 and v2 is generally preferred as it will help the reviewers. On 30 January 2013 12:00, Vikas Sajjan wrote: > This patch adds display-timing node parsing to drm fimd, this depends on > the display helper patchset at > http://lists.freedesktop.

[PATCH v2 0/1] Adds display-timing node parsing to exynos drm fimd

This patch adds display-timing node parsing to drm fimd, this depends on the display helper patchset at http://lists.freedesktop.org/archives/dri-devel/2013-January/033998.html It also adds pinctrl support for drm fimd. patch is based on branch "exynos-drm-next" at http://git.kernel.org/pub/scm/l