[PATCH v16 1/9] mm/gup: Introduce unpin_folio/unpin_folios helpers

These helpers are the folio versions of unpin_user_page/unpin_user_pages. They are currently only useful for unpinning folios pinned by memfd_pin_folios() or other associated routines. However, they could find new uses in the future, when more and more folio-only helpers are added to GUP. We shoul

[PATCH v16 4/9] udmabuf: add CONFIG_MMU dependency

From: Arnd Bergmann There is no !CONFIG_MMU version of vmf_insert_pfn(): arm-linux-gnueabi-ld: drivers/dma-buf/udmabuf.o: in function `udmabuf_vm_fault': udmabuf.c:(.text+0xaa): undefined reference to `vmf_insert_pfn' Fixes: d1d00dd1fd2f ("udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling

[PATCH v16 2/9] mm/gup: Introduce check_and_migrate_movable_folios()

This helper is the folio equivalent of check_and_migrate_movable_pages(). Therefore, all the rules that apply to check_and_migrate_movable_pages() also apply to this one as well. Currently, this helper is only used by memfd_pin_folios(). This patch also includes changes to rename and convert the i

[PATCH v16 0/9] mm/gup: Introduce memfd_pin_folios() for pinning memfd folios

Currently, some drivers (e.g, Udmabuf) that want to longterm-pin the pages/folios associated with a memfd, do so by simply taking a reference on them. This is not desirable because the pages/folios may reside in Movable zone or CMA block. Therefore, having drivers use memfd_pin_folios() API ensure

[PATCH v16 6/9] udmabuf: Add back support for mapping hugetlb pages

A user or admin can configure a VMM (Qemu) Guest's memory to be backed by hugetlb pages for various reasons. However, a Guest OS would still allocate (and pin) buffers that are backed by regular 4k sized pages. In order to map these buffers and create dma-bufs for them on the Host, we first need to

[PATCH v16 7/9] udmabuf: Convert udmabuf driver to use folios

This is mainly a preparatory patch to use memfd_pin_folios() API for pinning folios. Using folios instead of pages makes sense as the udmabuf driver needs to handle both shmem and hugetlb cases. And, using the memfd_pin_folios() API makes this easier as we no longer need to separately handle shmem

[PATCH v16 8/9] udmabuf: Pin the pages using memfd_pin_folios() API

Using memfd_pin_folios() will ensure that the pages are pinned correctly using FOLL_PIN. And, this also ensures that we don't accidentally break features such as memory hotunplug as it would not allow pinning pages in the movable zone. Using this new API also simplifies the code as we no longer ha

[PATCH v16 3/9] mm/gup: Introduce memfd_pin_folios() for pinning memfd folios

For drivers that would like to longterm-pin the folios associated with a memfd, the memfd_pin_folios() API provides an option to not only pin the folios via FOLL_PIN but also to check and migrate them if they reside in movable zone or CMA block. This API currently works with memfds but it should wo

[PATCH v16 5/9] udmabuf: Use vmf_insert_pfn and VM_PFNMAP for handling mmap

Add VM_PFNMAP to vm_flags in the mmap handler to ensure that the mappings would be managed without using struct page. And, in the vm_fault handler, use vmf_insert_pfn to share the page's pfn to userspace instead of directly sharing the page (via struct page *). Cc: David Hildenbrand Cc: Daniel V

[PATCH v16 9/9] selftests/udmabuf: Add tests to verify data after page migration

Since the memfd pages associated with a udmabuf may be migrated as part of udmabuf create, we need to verify the data coherency after successful migration. The new tests added in this patch try to do just that using 4k sized pages and also 2 MB sized huge pages for the memfd. Successful completion

[PATCH v1 1/5] drm/virtio: Implement VIRTIO_GPU_CMD_RESOURCE_DETACH_BACKING cmd

This cmd is useful to let the VMM (i.e, Qemu) know that the backing store associated with a resource is no longer valid, so that the VMM can perform any cleanup or unmap operations. Cc: Gerd Hoffmann Signed-off-by: Vivek Kasireddy --- drivers/gpu/drm/virtio/virtgpu_drv.h | 2 ++ drivers/gpu/dr

[PATCH v1 0/5] drm/virtio: Import scanout buffers from other devices

Having virtio-gpu import scanout buffers (via prime) from other devices means that we'd be adding a head to headless GPUs assigned to a Guest VM or additional heads to regular GPU devices that are passthrough'd to the Guest. In these cases, the Guest compositor can render into the scanout buffer us

[PATCH v1 5/5] drm/virtio: Add prepare and cleanup routines for imported dmabuf obj

When an imported dmabuf obj is used as part of an atomic commit, we need to pin it as part of prepare and unpin it during cleanup of the associated FB, to make sure that it does not move until the commit is completed (and also while it is being used on the Host). Cc: Gerd Hoffmann Signed-off-by:

[PATCH v1 4/5] drm/virtio: Import prime buffers from other devices as guest blobs

By importing scanout buffers from other devices, we should be able to use the virtio-gpu driver in KMS only mode. Note that we attach dynamically and register a move_notify() callback so that we can let the VMM know of any location changes associated with the backing store of the imported object by

[PATCH v1 3/5] drm/virtio: Add helpers to initialize and free the imported object

The imported object can be considered a guest blob resource; therefore, we use create_blob cmd while creating it. These helpers are used in the next patch which does the actual import. Cc: Gerd Hoffmann Signed-off-by: Vivek Kasireddy --- drivers/gpu/drm/virtio/virtgpu_object.c | 3 ++ drivers/

[PATCH v1 2/5] drm/virtio: Add a helper to map and note the dma addrs and lengths

This helper would be used when first initializing the object as part of import and also when updating the plane where we need to ensure that the imported object's backing is valid. Cc: Gerd Hoffmann Signed-off-by: Vivek Kasireddy --- drivers/gpu/drm/virtio/virtgpu_drv.h | 5 +++ drivers/gpu/

Re: [PATCH v4 06/15] dt-bindings: display: mediatek: dpi: add power-domains property

On 21/06/2024 17:10, Chun-Kuang Hu wrote: Hi, Alexandre: 於 2024年5月23日 週四 下午8:49寫道： From: Fabien Parent DPI is part of the display / multimedia block in MediaTek SoCs, and always have a power-domain (at least in the upstream device-trees). Add the power-domains property to the binding docu

[PATCH v2 1/3] vfio: Export vfio device get and put registration helpers

These helpers are useful for managing additional references taken on the device from other associated VFIO modules. Original-patch-by: Jason Gunthorpe Signed-off-by: Vivek Kasireddy --- drivers/vfio/vfio_main.c | 2 ++ include/linux/vfio.h | 2 ++ 2 files changed, 4 insertions(+) diff --gi

[PATCH v2 3/3] vfio/pci: Allow MMIO regions to be exported through dma-buf

>From Jason Gunthorpe: "dma-buf has become a way to safely acquire a handle to non-struct page memory that can still have lifetime controlled by the exporter. Notably RDMA can now import dma-buf FDs and build them into MRs which allows for PCI P2P operations. Extend this to allow vfio-pci to export

[PATCH v2 2/3] vfio/pci: Share the core device pointer while invoking feature functions

There is no need to share the main device pointer (struct vfio_device *) with all the feature functions as they only need the core device pointer. Therefore, extract the core device pointer once in the caller (vfio_pci_core_ioctl_feature) and share it instead. Signed-off-by: Vivek Kasireddy ---

[PATCH v2 0/3] vfio/pci: Allow MMIO regions to be exported through dma-buf

This is an attempt to revive the patches posted by Jason Gunthorpe at: https://patchwork.kernel.org/project/linux-media/cover/0-v2-472615b3877e+28f7-vfio_dma_buf_...@nvidia.com/ Here is the cover letter text from Jason's original series: "dma-buf has become a way to safely acquire a handle to non-

Re: [PATCH 06/15] net: hbl_cn: debugfs support

On 6/23/24 18:02, Andrew Lunn wrote: >>> If there is no netdev, what is the point of putting it into loopback? >>> How do you send packets which are to be looped back? How do you >>> receive them to see if they were actually looped back? >>> >>> Andrew >> >> To run RDMA test in loopback. > > W

Re: [PATCH v4 12/15] drm/mediatek: add MT8365 SoC support

On 21/06/2024 17:24, Chun-Kuang Hu wrote: Hi, Alexandre: 於 2024年5月23日 週四 下午8:49寫道： From: Fabien Parent Add DRM support for MT8365 SoC. Signed-off-by: Fabien Parent Reviewed-by: AngeloGioacchino Del Regno Signed-off-by: Alexandre Mergnat --- drivers/gpu/drm/mediatek/mtk_drm_drv.c | 8 ++

[PATCH 3/7] dt-bindings: arm: qcom: add OnePlus 8 series

Add bindings for the OnePlus 8, 8 Pro, and 8T devices. Signed-off-by: Caleb Connolly --- Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml index

[PATCH 2/4] drm/udl: Add cursor drm_plane support

From: Łukasz Spintzyk Atomic support for cursor plane was inspired by evdi drm driver that is maintained on github.com/displaylink/evdi. Also added ARGB plane format as it is used by cursor plane. Signed-off-by: Łukasz Spintzyk --- drivers/gpu/drm/udl/udl_cursor.c | 32 +++- drivers

[PATCH 4/7] drm: mipi: add mipi_dsi_generic_write_multi_type()

Some panels like the Samsung AMB655X use long write commands for all non-standard messages and do not work when trying to use the appropriate command type. Support these panels by introducing a new helper to send commands of a specific type, overriding the normal rules. Signed-off-by: Caleb Conno

[PATCH 5/7] drm/panel: add driver for samsung amb655x

This is a 1080x2400 120hz panel used on the OnePlus 8T. It uses DSC but uses non-standard DCS commands. Signed-off-by: Caleb Connolly --- MAINTAINERS | 7 + drivers/gpu/drm/panel/Kconfig | 9 + drivers/gpu/drm/panel/Makefile|

[PATCH 3/4] drm/udl: Allow smaller plane sizes to allow cursor plane

From: Łukasz Spintzyk Signed-off-by: Łukasz Spintzyk --- drivers/gpu/drm/udl/udl_modeset.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/udl/udl_modeset.c b/drivers/gpu/drm/udl/udl_modeset.c index 0bd4e2f02dcf..28b7c269e913 100644 --- a/drivers/gpu/drm

[PATCH 4/4] drm/udl: Shutdown all CRTCs on usb disconnect

From: Łukasz Spintzyk This is fixing some kernel panics on device unplug, that started to be more visible after implementing cursor plane support. Signed-off-by: Łukasz Spintzyk --- drivers/gpu/drm/udl/udl_drv.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/udl/udl_drv

[PATCH 1/7] dt-bindings: panel: document Samsung AMB655X

Describe the Samsung AMB655X panel. It has three supplies. Signed-off-by: Caleb Connolly --- .../bindings/display/panel/samsung,amb655x.yaml| 59 ++ 1 file changed, 59 insertions(+) diff --git a/Documentation/devicetree/bindings/display/panel/samsung,amb655x.yaml b/Doc

[PATCH] drm/amd/display: Add otg_master NULL check within init_pipe_slice_table_from_context

To avoid reports of NULL_RETURN warning, we should add otg_master NULL check. Signed-off-by: Ma Ke --- drivers/gpu/drm/amd/display/dc/dml/dcn32/dcn32_fpu.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/amd/display/dc/dml/dcn32/dcn32_fpu.c b/drivers/gpu/drm/amd/display/dc

[PATCH 0/7] qcom: initial support for the OnePlus 8T

Add bindings for the SM8250 OnePlus devices, a common devicetree, touchscreen and display drivers, and a dts for the OnePlus 8T (kebab). The OnePlus 8 series is made up of 3 flagship smartphones from 2019, featuring the Qualcomm X55 5G PCIe modem. This series introduces initial support for the 8T

[PATCH 6/7] Input: touchscreen: add Synaptics TCM oncell S3908

The TCM oncell is the next generation of Synaptics touchscreen ICs. These run a very featured firmware with a reasonably well defined API. It is however entirely incompatible with the existing RMI4 interface. Unfortunately, no public datasheet for the interface seems to be available, instead this

[PATCH] drm/amd/display: Check pipe_ctx before it is used

resource_get_otg_master_for_stream() could return NULL, we should check the return value of 'otg_master' before it is used in resource_log_pipe_for_stream(). Signed-off-by: Ma Ke --- drivers/gpu/drm/amd/display/dc/core/dc_resource.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/g

[PATCH 7/7] arm64: dts: qcom: add OnePlus 8T (kebab)

Initial support for USB, UFS, touchscreen, panel, wifi, and bluetooth. Co-developed-by: Frieder Hannenheim Signed-off-by: Frieder Hannenheim Signed-off-by: Caleb Connolly --- arch/arm64/boot/dts/qcom/Makefile | 1 + .../arm64/boot/dts/qcom/sm8250-oneplus-common.dtsi | 866 ++

[PATCH 1/4] drm/udl: Port CrOS cursor blending on primary plane in usb transfer

From: Douglas Anderson Port applicable parts of CrOS udl cursor implementation from 5.4 CrOS kernel fork. - removed legacy non-atomic udl_cursor_move, udl_cursor_set ioctl's implementation - modified udl_cursor_download to copy cursor content to the buffer from iosys_map - removed unnecessa

drm/udl: Implementation of atomic cursor drm_plane

This brings cursor on DisplayLink USB2.0 device on ChromeOS compositor that requires either crtc'c cursor_set callback or cursor drm_plane. Patch was tested on ChromeOS and Ubuntu 22.04 with Gnome/Wayland

Re: [PATCH v2 1/7] drm/radeon: remove load callback

Hi Am 21.06.24 um 16:15 schrieb Wu Hoi Pok: This is "drm/radeon: remove load callback" v2, the only changes were made are adding "ddev->dev_private = rdev;", right after the allocation of "struct radeon_device". Patch v2 2-7 mostly describes simple "rdev->ddev" to "rdev_to_drm(rdev)" to suit Pat

Re: [PATCH 1/7] dt-bindings: panel: document Samsung AMB655X

On 24/06/2024 03:30, Caleb Connolly wrote: Describe the Samsung AMB655X panel. It has three supplies. Signed-off-by: Caleb Connolly --- .../bindings/display/panel/samsung,amb655x.yaml| 59 ++ 1 file changed, 59 insertions(+) diff --git a/Documentation/devicetree/

[PATCH 2/7] dt-bindings: input: touchscreen: document synaptics TCM oncell

Document the Synaptics TCM oncell series of touchscreens, starting with the s3908. Signed-off-by: Caleb Connolly --- .../input/touchscreen/syna,tcm-oncell.yaml | 66 ++ 1 file changed, 66 insertions(+) diff --git a/Documentation/devicetree/bindings/input/touchscreen

Re: [PATCH 04/15] net: hbl_cn: QP state machine

On 6/18/24 12:00, Leon Romanovsky wrote: > On Tue, Jun 18, 2024 at 07:58:55AM +, Omer Shpigelman wrote: >> On 6/18/24 10:08, Leon Romanovsky wrote: >>> On Tue, Jun 18, 2024 at 05:50:15AM +, Omer Shpigelman wrote: On 6/17/24 16:18, Leon Romanovsky wrote: > [Some people who received

Re: [PATCH 2/7] dt-bindings: input: touchscreen: document synaptics TCM oncell

Hi Caleb, On Mon, Jun 24, 2024 at 03:30:26AM +0200, Caleb Connolly wrote: > +examples: > + - | > +#include > +#include > + > +i2c { > + clock-frequency = <40>; > + status = "okay"; > + > + touchscreen@4b { > +compatible = "syna,s3908"; > +reg = <0x

Re: drm/udl: Implementation of atomic cursor drm_plane

Hi Am 24.06.24 um 09:10 schrieb lukasz.spint...@synaptics.com: This brings cursor on DisplayLink USB2.0 device on ChromeOS compositor that requires either crtc'c cursor_set callback or cursor drm_plane. Patch was tested on ChromeOS and Ubuntu 22.04 with Gnome/Wayland NAK on this patchset. UD

Re: [PATCH 6/7] Input: touchscreen: add Synaptics TCM oncell S3908

Hi Caleb, On Mon, Jun 24, 2024 at 03:30:30AM +0200, Caleb Connolly wrote: > The TCM oncell is the next generation of Synaptics touchscreen ICs. > These run a very featured firmware with a reasonably well defined API. > It is however entirely incompatible with the existing RMI4 interface. > > Unfo

Re: [PATCH v3 4/6] drm/bridge: tc358767: Disable MIPI_DSI_CLOCK_NON_CONTINUOUS

Hi, Am Sonntag, 23. Juni 2024, 16:38:36 CEST schrieb Marek Vasut: > The MIPI_DSI_CLOCK_NON_CONTINUOUS causes visible artifacts in high > resolution modes, disable it. Namely, in DSI->DP mode 1920x1200 24 > bpp 59.95 Hz, with DSI bus at maximum 1 Gbps per lane setting, the > image contains jitterin

Re: [PATCH v1] misc: fastrpc: Move fastrpc driver to misc/fastrpc/

On Sun, Jun 23, 2024 at 03:19:17PM GMT, Bjorn Andersson wrote: > On Fri, Jun 21, 2024 at 05:52:32PM GMT, Daniel Vetter wrote: > > On Fri, Jun 21, 2024 at 09:40:09AM -0600, Jeffrey Hugo wrote: > > > On 6/21/2024 5:19 AM, Dmitry Baryshkov wrote: > > > > On Fri, 21 Jun 2024 at 09:19, Bjorn Andersson

[PATCH] MAINTAINERS: CC dri-devel list on Qualcomm FastRPC patches

--- base-commit: 2102cb0d050d34d50b9642a3a50861787527e922 change-id: 20240624-fastrpc-ml-24c7d5cf5e7b Best regards, -- Dmitry Baryshkov

Re: [PATCH v3 6/6] Revert "drm/bridge: tc358767: Set default CLRSIPO count"

Am Sonntag, 23. Juni 2024, 16:38:38 CEST schrieb Marek Vasut: > This reverts commit 01338bb82fed40a6a234c2b36a92367c8671adf0. > > With clock improvements in place, this seems to be no longer > necessary. Set the CLRSIPO to default setting recommended by > manufacturer. > > Signed-off-by: Marek Va

Re: [PATCH] drm/ttm/pool: Revert to clear-on-alloc to honor TTM_TT_FLAG_ZERO_ALLOC

Am 21.06.24 um 17:43 schrieb Nirmoy Das: Hi Christian, On 6/21/2024 4:54 PM, Christian König wrote: Am 20.06.24 um 18:01 schrieb Nirmoy Das: Currently ttm pool is not honoring TTM_TT_FLAG_ZERO_ALLOC flag and clearing pages on free. It does help with allocation latency but clearing happens ev

Re: [PATCH v3 5/6] drm/bridge: tc358767: Set LSCLK divider for SYSCLK to 1

Am Sonntag, 23. Juni 2024, 16:38:37 CEST schrieb Marek Vasut: > The only information in the datasheet regarding this divider is a note > in SYS_PLLPARAM register documentation which states that when LSCLK is > 270 MHz, LSCLK_DIV should be 1. What should LSCLK_DIV be set to when > LSCLK is 162 MHz (

Re: [PATCH v6 0/7] Add mediate-drm secure flow for SVP

Re: [PATCH 11/15] RDMA/hbl: add habanalabs RDMA driver

On 6/19/24 13:52, Leon Romanovsky wrote: > On Wed, Jun 19, 2024 at 09:27:54AM +, Omer Shpigelman wrote: >> On 6/18/24 15:58, Leon Romanovsky wrote: >>> On Tue, Jun 18, 2024 at 11:08:34AM +, Omer Shpigelman wrote: On 6/17/24 22:04, Leon Romanovsky wrote: > [Some people who received

Re: [PATCH RESEND] drm/panel: simple: Add missing display timing flags for KOE TX26D202VM0BWA

On 24/06/2024 03:56, Liu Ying wrote: KOE TX26D202VM0BWA panel spec indicates the DE signal is active high in timing chart, so add DISPLAY_FLAGS_DE_HIGH flag in display timing flags. This aligns display_timing with panel_desc. Fixes: 8a07052440c2 ("drm/panel: simple: Add support for KOE TX26D202V

Re: [PATCH v2 1/3] drm: Add panel backlight quirks

Hi Thomas, On 6/23/24 10:51 AM, Thomas Weißschuh wrote: > Panels using a PWM-controlled backlight source without an do not have a > standard way to communicate their valid PWM ranges. > On x86 the ranges are read from ACPI through driver-specific tables. > The built-in ranges are not necessarily c

Re: [PATCH v3 3/6] drm/bridge: tc358767: Drop line_pixel_subtract

Am Sonntag, 23. Juni 2024, 16:38:35 CEST schrieb Marek Vasut: > This line_pixel_subtract is no longer needed now that the bridge can > request and obtain specific pixel clock on input to the bridge, with > clock frequency that matches the Pixel PLL frequency. > > The line_pixel_subtract is now alw

Re: [PATCH v3 2/6] drm/bridge: tc358767: Use tc_pxl_pll_calc() to correct adjusted_mode clock

Am Sonntag, 23. Juni 2024, 16:38:34 CEST schrieb Marek Vasut: > Use tc_pxl_pll_calc() to find out the exact clock frequency generated by the > Pixel PLL. Use the Pixel PLL frequency as adjusted_mode clock frequency and > pass it down the display pipeline to obtain exactly this frequency on input >

Re: [PATCH] drm/panel: asus-z00t-tm5p5-n35596: transition to mipi_dsi wrapped functions

Hi, On Fri, 21 Jun 2024 18:46:46 +0530, Tejas Vipin wrote: > Use functions introduced in commit 966e397e4f60 ("drm/mipi-dsi: > Introduce mipi_dsi_*_write_seq_multi()") and commit f79d6d28d8fe > ("drm/mipi-dsi: wrap more functions for streamline handling") for the > asus-z00t-tm5p5-n35596 panel. >

Re: [PATCH v3] drm/panel: raydium-rm692e5: transition to mipi_dsi wrapped functions

Hi, On Thu, 20 Jun 2024 23:40:49 +0530, Tejas Vipin wrote: > Use functions introduced in commit 966e397e4f60 ("drm/mipi-dsi: > Introduce mipi_dsi_*_write_seq_multi()") and commit f79d6d28d8fe > ("drm/mipi-dsi: wrap more functions for streamline handling") for the > raydium-rm692e5 panel. > > Addi

Re: [PATCH v3 1/6] drm/bridge: tc358767: Split tc_pxl_pll_en() into parameter calculation and enablement

Am Sonntag, 23. Juni 2024, 16:38:33 CEST schrieb Marek Vasut: > Split tc_pxl_pll_en() into tc_pxl_pll_calc() which does only Pixel PLL > parameter calculation and tc_pxl_pll_en() which calls tc_pxl_pll_calc() > and then configures the Pixel PLL register. > > This is a preparatory patch for further

Re: [PATCH v3 4/6] drm/bridge: tc358767: Disable MIPI_DSI_CLOCK_NON_CONTINUOUS

Am Montag, 24. Juni 2024, 09:45:13 CEST schrieb Alexander Stein: > Hi, > > Am Sonntag, 23. Juni 2024, 16:38:36 CEST schrieb Marek Vasut: > > The MIPI_DSI_CLOCK_NON_CONTINUOUS causes visible artifacts in high > > resolution modes, disable it. Namely, in DSI->DP mode 1920x1200 24 > > bpp 59.95 Hz, w

Re: [PATCH v5 07/12] drm/ttm: Use the LRU walker for eviction

Hi, Matthew On Wed, 2024-06-19 at 22:52 +, Matthew Brost wrote: > On Tue, Jun 18, 2024 at 09:18:15AM +0200, Thomas Hellström wrote: > > Use the LRU walker for eviction. This helps > > removing a lot of code with weird locking > > semantics. > > > > The functionality is slightly changed so tha

Re: [PATCH 11/15] RDMA/hbl: add habanalabs RDMA driver

On Mon, Jun 24, 2024 at 08:47:41AM +, Omer Shpigelman wrote: > On 6/19/24 13:52, Leon Romanovsky wrote: > > On Wed, Jun 19, 2024 at 09:27:54AM +, Omer Shpigelman wrote: > >> On 6/18/24 15:58, Leon Romanovsky wrote: > >>> On Tue, Jun 18, 2024 at 11:08:34AM +, Omer Shpigelman wrote: > >>>

Re: [PATCH v2 0/3] drm: backlight quirk infrastructure and lower minimum for Framework AMD 13

Hi Thomas, On 6/23/24 10:51 AM, Thomas Weißschuh wrote: > The value of "min_input_signal" returned from ATIF on a Framework AMD 13 > is "12". This leads to a fairly bright minimum display backlight. > > Add a generic quirk infrastructure for backlight configuration to > override the settings prov

Re: [PATCH 01/11] drm/rockchip: cdn-dp: get rid of drm_edid_raw()

On Tue, May 14, 2024 at 03:55:07PM +0300, Jani Nikula wrote: > The dimensions are available in display info, so there's no need for raw > EDID access. While at it, move the debug logging to where the EDID is > actually read. > > Signed-off-by: Jani Nikula > > --- > > Cc: Sandy Huang > Cc: "Hei

Re: [PATCH v5 07/12] drm/ttm: Use the LRU walker for eviction

On Wed, 2024-06-19 at 23:33 +, Matthew Brost wrote: > On Tue, Jun 18, 2024 at 09:18:15AM +0200, Thomas Hellström wrote: > > Use the LRU walker for eviction. This helps > > removing a lot of code with weird locking > > semantics. > > > > The functionality is slightly changed so that > > when tr

Re: [PATCH 8/8] drm: bridge: dw_hdmi: Use display_info is_hdmi and has_audio

On 11/06/2024 17:51, Jonas Karlman wrote: drm_edid_connector_update() is being called from bridge connector ops and from detect and get_modes ops for dw-hdmi connector. Change to use is_hdmi and has_audio from display_info directly instead of keeping our own state in sink_is_hdmi and sink_has_au

Re: [PATCH] drm: lcdif: Use adjusted_mode .clock instead of .crtc_clock

Am Freitag, 31. Mai 2024, 22:27:21 CEST schrieb Marek Vasut: > In case an upstream bridge modified the required clock frequency > in its .atomic_check callback by setting adjusted_mode.clock , > make sure that clock frequency is generated by the LCDIFv3 block. > > This is useful e.g. when LCDIFv3

Re: [PATCH 5/8] drm: bridge: dw_hdmi: Invalidate CEC phys addr from connector detect

On 11/06/2024 17:50, Jonas Karlman wrote: Wait until the connector detect ops is called to invalidate CEC phys addr instead of doing it directly from the irq handler. Signed-off-by: Jonas Karlman --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 18 +++--- 1 file changed, 11 insert

Re: [PATCH 6/8] drm: bridge: dw_hdmi: Remove cec_notifier_mutex

On 11/06/2024 17:50, Jonas Karlman wrote: With CEC phys addr invalidation moved away from the irq handler there is no longer a need for cec_notifier_mutex, remove it. Signed-off-by: Jonas Karlman --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 11 +-- 1 file changed, 1 insertion(+),

Re: [PATCH 06/15] net: hbl_cn: debugfs support

On Sun, Jun 23, 2024 at 05:02:44PM +0200, Andrew Lunn wrote: > > > If there is no netdev, what is the point of putting it into loopback? > > > How do you send packets which are to be looped back? How do you > > > receive them to see if they were actually looped back? > > > > > > Andrew > > > >

Re: [PATCH 02/11] drm/sti/sti_hdmi: convert to struct drm_edid

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 could not be read. > > Signed-off-by: Jani Nikul

Re: [PATCH 1/8] drm: bridge: dw_hdmi: Call poweron/poweroff from atomic enable/disable

On 11/06/2024 17:50, Jonas Karlman wrote: Change to only call poweron/poweroff from atomic_enable/atomic_disable ops instead of trying to keep a bridge_is_on state and poweron/off in the hotplug irq handler. A benefit of this is that drm mode_config mutex is always held at poweron/off, something

Re: [PATCH v4 03/10] drm/rockchip:hdmi: migrate to use inno-hdmi bridge driver

On Sun, Jun 23, 2024 at 07:17:14AM GMT, Keith Zhao wrote: > Hi Maxime： > > > > -Original Message- > > From: Maxime Ripard > > Sent: 2024年5月22日 15:25 > > To: Keith Zhao > > Cc: andrzej.ha...@intel.com; neil.armstr...@linaro.org; rf...@kernel.org; > > laurent.pinch...@ideasonboard.com; jo

Re: [PATCH v5 08/12] drm/ttm: Add a virtual base class for graphics memory backup

On Thu, 2024-06-20 at 15:17 +, Matthew Brost wrote: > On Tue, Jun 18, 2024 at 09:18:16AM +0200, Thomas Hellström wrote: > > Initially intended for experimenting with different backup > > solutions (shmem vs direct swap cache insertion), abstract > > the backup destination using a virtual base c

Re: [1/2] drm: bridge: samsung-dsim: Initialize bridge on attach

Hi, Am Montag, 13. Mai 2024, 04:16:27 CEST schrieb Marek Vasut: > Initialize the bridge on attach already, to force lanes into LP11 > state, since attach does trigger attach of downstream bridges which > may trigger (e)DP AUX channel mode read. > > This fixes a corner case where DSIM with TC9595

Re: [2/2] drm/bridge: tc358767: Reset chip again on attach

Hi, Am Montag, 13. Mai 2024, 04:16:28 CEST schrieb Marek Vasut: > In case the chip is released from reset using the RESX signal while the > DSI lanes are in non-LP11 mode, the chip may enter some sort of debug > mode, where its internal clock run at 1/6th of expected clock rate. In > this mode, th

Re: [PATCH 2/6] drm/bridge: tc358767: Use tc_pxl_pll_calc() to correct adjusted_mode clock

Hi Marek, Am Freitag, 21. Juni 2024, 16:54:51 CEST schrieb Marek Vasut: > On 6/21/24 12:32 PM, Alexander Stein wrote: > > Hi, > > skipping the parts where I would simply write "OK" ... > > As FVUEN is cleared at the next VSYNC event I suspect the DSI timings > are (slightly) off, but

Re: [PATCH 09/11] drm/tegra: convert to struct drm_edid

On Tue, May 14, 2024 at 03:55:15PM +0300, Jani Nikula wrote: > Prefer the struct drm_edid based functions for reading the EDID and > updating the connector. > > Signed-off-by: Jani Nikula > > --- > > Cc: Thierry Reding > Cc: Mikko Perttunen > Cc: Jonathan Hunter > Cc: linux-te...@vger.kernel

Re: [PATCH v1] misc: fastrpc: Move fastrpc driver to misc/fastrpc/

On Fri, Jun 21, 2024 at 10:48:27PM +0300, Dmitry Baryshkov wrote: > On Fri, 21 Jun 2024 at 18:52, Daniel Vetter wrote: > > > > On Fri, Jun 21, 2024 at 09:40:09AM -0600, Jeffrey Hugo wrote: > > > On 6/21/2024 5:19 AM, Dmitry Baryshkov wrote: > > > > On Fri, 21 Jun 2024 at 09:19, Bjorn Andersson >

Re: [PATCH v1] misc: fastrpc: Move fastrpc driver to misc/fastrpc/

On Sun, Jun 23, 2024 at 03:19:17PM -0500, Bjorn Andersson wrote: > On Fri, Jun 21, 2024 at 05:52:32PM GMT, Daniel Vetter wrote: > > On Fri, Jun 21, 2024 at 09:40:09AM -0600, Jeffrey Hugo wrote: > > > On 6/21/2024 5:19 AM, Dmitry Baryshkov wrote: > > > > On Fri, 21 Jun 2024 at 09:19, Bjorn Andersson

Re: [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case

On 22/06/24 17:49, Dmitry Baryshkov wrote: > On Sat, Jun 22, 2024 at 05:16:58PM GMT, Aradhya Bhatia wrote: >> >> >> On 17-Jun-24 13:41, Dmitry Baryshkov wrote: >>> On Mon, Jun 17, 2024 at 07:40:32AM GMT, Jan Kiszka wrote: On 16.02.24 15:57, Marek Vasut wrote: > On 2/16/24 10:10, Tomi Va

Re: [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case

On Mon, Jun 24, 2024 at 03:07:10PM GMT, Aradhya Bhatia wrote: > > > On 22/06/24 17:49, Dmitry Baryshkov wrote: > > On Sat, Jun 22, 2024 at 05:16:58PM GMT, Aradhya Bhatia wrote: > >> > >> > >> On 17-Jun-24 13:41, Dmitry Baryshkov wrote: > >>> On Mon, Jun 17, 2024 at 07:40:32AM GMT, Jan Kiszka wrot

Re: [PATCH 1/8] drm: bridge: dw_hdmi: Call poweron/poweroff from atomic enable/disable

Hi Neil, On 2024-06-24 11:23, Neil Armstrong wrote: > On 11/06/2024 17:50, Jonas Karlman wrote: >> Change to only call poweron/poweroff from atomic_enable/atomic_disable >> ops instead of trying to keep a bridge_is_on state and poweron/off in >> the hotplug irq handler. >> >> A benefit of this is

Re: [PATCH linux-next] gpu:ipu-v3:pre: replace of_node_put() with __free

On Sa, 2024-04-27 at 10:20 +0530, R Sundar wrote: > use the new cleanup magic to replace of_node_put() with > __free(device_node) marking to auto release when they get out of scope. > > Suggested-by: Julia Lawall > Signed-off-by: R Sundar Reviewed-by: Philipp Zabel regards Philipp

Re: [PATCH v3 2/3] gpu: ipu-v3: pre: add dynamic buffer layout reconfiguration

On Fr, 2024-05-17 at 12:45 +0200, Lucas Stach wrote: > imx-drm doesn't mandate a modeset when the framebuffer modifier changes, > but currently the tile prefetch and resolve (TPR) configuration of the > PRE is only set up on the initial modeset. > > As the TPR configuration is double buffered, sam

Re: [PATCH 1/8] drm: bridge: dw_hdmi: Call poweron/poweroff from atomic enable/disable

On 24/06/2024 11:41, Jonas Karlman wrote: Hi Neil, On 2024-06-24 11:23, Neil Armstrong wrote: On 11/06/2024 17:50, Jonas Karlman wrote: Change to only call poweron/poweroff from atomic_enable/atomic_disable ops instead of trying to keep a bridge_is_on state and poweron/off in the hotplug irq h

Re: [PATCH v3 3/3] gpu: ipu-v3: pre: don't use fixed timeout when waiting for safe window

On Fr, 2024-05-17 at 12:45 +0200, Lucas Stach wrote: > The timeout when waiting for the PRE safe window is rather short, as > normally we would only need to wait a few dozen usecs for the problematic > scanline region to pass and we don't want to spin too long in case > something goes wrong. This h

[PATCH] drm/mediatek: Fix bit depth overwritten for mtk_ovl_set bit_depth()

Refine the value and mask define of bit depth for mtk_ovl_set bit_depth(). Use cmdq_pkt_write_mask() instead of cmdq_pkt_write() to avoid bit depth settings being overwritten. Fixes: fb36c5020c9c ("drm/mediatek: Add support for AR30 and BA30 overlays") Signed-off-by: Jason-JH.Lin --- Based on: h

Re: [PATCH v2 3/3] vfio/pci: Allow MMIO regions to be exported through dma-buf

On Sun, Jun 23, 2024 at 11:53:11PM -0700, Vivek Kasireddy wrote: > From Jason Gunthorpe: > "dma-buf has become a way to safely acquire a handle to non-struct page > memory that can still have lifetime controlled by the exporter. Notably > RDMA can now import dma-buf FDs and build them into MRs whic

Re: drm/udl: Implementation of atomic cursor drm_plane

On Mon, Jun 24, 2024 at 09:28:29AM +0200, Thomas Zimmermann wrote: > Hi > > Am 24.06.24 um 09:10 schrieb lukasz.spint...@synaptics.com: > > This brings cursor on DisplayLink USB2.0 device on ChromeOS compositor that > > requires either crtc'c cursor_set callback > > or cursor drm_plane. Patch was

Re: [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case

Hi, Am Montag, 24. Juni 2024, 11:49:04 CEST schrieb Dmitry Baryshkov: > On Mon, Jun 24, 2024 at 03:07:10PM GMT, Aradhya Bhatia wrote: > > > > > > On 22/06/24 17:49, Dmitry Baryshkov wrote: > > > On Sat, Jun 22, 2024 at 05:16:58PM GMT, Aradhya Bhatia wrote: > > >> > > >> > > >> On 17-Jun-24 13:41

Re: [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case

On Mon, 24 Jun 2024 at 13:07, Alexander Stein wrote: > > Hi, > > Am Montag, 24. Juni 2024, 11:49:04 CEST schrieb Dmitry Baryshkov: > > On Mon, Jun 24, 2024 at 03:07:10PM GMT, Aradhya Bhatia wrote: > > > > > > > > > On 22/06/24 17:49, Dmitry Baryshkov wrote: > > > > On Sat, Jun 22, 2024 at 05:16:58

Re: [PATCH v1 0/3] Support for Adreno X1-85 GPU

On 24/06/2024 08:21, Akhil P Oommen wrote: > On Sun, Jun 23, 2024 at 01:11:48PM +0200, Krzysztof Kozlowski wrote: >> On 23/06/2024 13:06, Akhil P Oommen wrote: >>> This series adds support for the Adreno X1-85 GPU found in Qualcomm's >>> compute series chipset, Snapdragon X1 Elite (x1e80100). In th

[PATCH] drm/ttm: Add a flag to allow drivers to skip clear-on-free

Add TTM_TT_FLAG_CLEARED_ON_FREE, which DRM drivers can set before releasing backing stores if they want to skip clear-on-free. Cc: Matthew Auld Cc: Thomas Hellström Suggested-by: Christian König Signed-off-by: Nirmoy Das --- drivers/gpu/drm/ttm/ttm_pool.c | 18 +++--- include/drm/

[PATCH] drm/lcdif: switch to DRM_BRIDGE_ATTACH_NO_CONNECTOR

} return 0; --- base-commit: f76698bd9a8ca01d3581236082d786e9a6b72bb7 change-id: 20240624-mxc-lcdif-bridge-attach-60368807b2f9 Best regards, -- Dmitry Baryshkov

Re: [PATCH v14 00/12] Improve test coverage of TTM

Hi Amar, I pushed all the patches into drm-misc-next. Regards, Arun. On 6/21/2024 11:41 AM, Somalapuram, Amaranath wrote: Hi Arun, I still don't have commit permission. Can you please help to push this patches. Regards, S.Amarnath On 6/20/2024 2:38 PM, Karolina Stolarek wrote: Hi Christi

Re: [PATCH v3 0/7] Support fdinfo runtime and memory stats on Panthor

Hi Steven, On 13.06.2024 16:28, Steven Price wrote: > On 06/06/2024 01:49, Adrián Larumbe wrote: > > This patch series enables userspace utilities like gputop and nvtop to > > query a render context's fdinfo file and figure out rates of engine > > and memory utilisation. > > > > Previous discussi

Re: [PATCH v2 0/7] drm/panic: Fixes and graphical logo

On 21/06/2024 10:55, Jocelyn Falempe wrote: Hi, I want to push at least the first patch that is an important fix. But if there are no objections, I can push the whole series except patch 5 "drm/panic: Convert to drm_fb_clip_offset()" which causes some build issue. I just pushed them to drm-m

Re: [PATCH] drm/lcdif: switch to DRM_BRIDGE_ATTACH_NO_CONNECTOR

if (IS_ERR(connector)) { > + ret = PTR_ERR(connector); > + of_node_put(ep); > + > + return dev_err_probe(dev, ret, > + "Failed to create bridge connector > for endpoint

Re: [PATCH 0/7] qcom: initial support for the OnePlus 8T

On Mon, 24 Jun 2024 at 14:33, Caleb Connolly wrote: > > > > On 24/06/2024 07:18, Dmitry Baryshkov wrote: > > On Mon, Jun 24, 2024 at 03:30:24AM GMT, Caleb Connolly wrote: > >> Add bindings for the SM8250 OnePlus devices, a common devicetree, > >> touchscreen and display drivers, and a dts for the

  1   2   3   >