Re: [PATCH v4 08/11] arm64: dts: qcom: sm8350: Use 2 interconnect cells

On 02/01/2023 18:10, Robert Foss wrote: > On Fri, 30 Dec 2022 at 17:12, Krzysztof Kozlowski > wrote: >> >> On 30/12/2022 16:35, Robert Foss wrote: >>> Use two interconnect cells in order to optionally >>> support a path tag. >>> >>> Signed-off-by: Robert Foss >>> Reviewed-by: Konrad Dybcio >>> -

Re: [PATCH 1/2] drm/panel-edp: fix name for IVO product id 854b

On Sat, Dec 31, 2022 at 04:27:20PM +0200, Abel Vesa wrote: > The actual name is R133NW4K-R0. > > Fixes: 0f9fa5f58c784 ("drm/panel-edp: add IVO M133NW4J-R3 panel entry") > Signed-off-by: Abel Vesa Reviewed-by: Johan Hovold

Re: [PATCH 3/5] drm/rockchip: vop2: use symmetric function pair vop2_{create,destroy}_crtcs

Hi Michael, url: https://github.com/intel-lab-lkp/linux/commits/Michael-Riesch/drm-rockchip-vop2-add-support-for-the-rgb-output-block/20221130-220346 base: b7b275e60bcd5f89771e865a8239325f86d9927d patch link: https://lore.kernel.org/r/20221130140217.3196414-4-michael.riesch%40wolfvision.

Re: [PATCH 2/2] drm/panel-edp: add IVO M133NW4J panel entry

On Sat, Dec 31, 2022 at 04:27:21PM +0200, Abel Vesa wrote: > Add an eDP panel entry for IVO M133NW4J. > > Due to lack of documentation, use the delay_200_500_p2e100 timings like > some other IVO entries for now. > > Signed-off-by: Abel Vesa > --- Reviewed-by: Johan Hovold

Re: [RFC PATCH 1/4] dt-bindings: vendor-prefixes: Add microtips

On 03/01/2023 07:46, Aradhya Bhatia wrote: > Add document vendor prefix for Microtips Technology USA (microtips). > > Signed-off-by: Aradhya Bhatia > --- > Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ Acked-by: Krzysztof Kozlowski Best regards, Krzysztof

Re: [RFC PATCH 2/4] dt-bindings: vendor-prefixes: Add lincolntech

On 03/01/2023 07:46, Aradhya Bhatia wrote: > Add document vendor prefix for Lincoln Technology Solutions > (lincolntech). > > Signed-off-by: Aradhya Bhatia > --- > Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ Acked-by: Krzysztof Kozlowski Best regards, Krzysztof

Re: [PATCH 2/2] vfio/pci: Remove console drivers

Hi, I just upgraded my system (after 7 months) and I also lost my framebuffer on boot. At first, I thought that my computer was freezing on startup, but it turns out that it is running fine (I can SSH to it and even startx remotely), only the framebuffer stops working very early on boot:

[PATCH v1 1/3] xen/grant-table: save page_count on map and use if during async unmapping

Save the reference count of the page before mapping and use this value in gntdev_unmap_refs_async() call. This is the enhancement of the commit 3f9f1c67572f5e5e6dc84216d48d1480f3c4fcf6 ("xen/grant-table: add a mechanism to safely unmap pages that are in use"). Safe unmapping mechanism defers page t

[PATCH v1 0/3] Add ioctls to map grant refs on the external backing storage

Hello, Let me introduce the new ioctls, which are intended to allow gntdev to map scatter-gather table on top of the existing dmabuf, referenced by file descriptor. When using dma-buf exporter to create dma-buf with backing storage and map it to the grant refs, provided from the domain, we've met

Re: AW: [PATCH v1 0/3] Add ioctls to map grant refs on the external backing storage

On 02.01.23 18:36, Koenig, Christian wrote: [AMD Official Use Only - General] Sorry for the messed up mail. We currently have mail problems here at AMD. Von: Oleksii Moisieiev Gesendet: Montag, 2. Januar 2023 14:41 An: jgr...

[PATCH v1 2/3] dma-buf: add dma buffer release notifier callback

Add posibility to register callback on dma-buffer which is called before dma_buf->ops->release call. This helps when external user of the dma buffer should be notified before buffer releases without changing dma-buf ops. This is needed when external dma buffer is used as backing storage for gntdev

[PATCH v1 3/3] xen/grant-table: add new ioctls to map dmabuf to existing fd

Add new ioctls to allow gntdev to map scatter-gather table on top of the existing dmabuf, referenced by file descriptor. When using dma-buf exporter to create dma-buf with backing storage and map it to the grant refs, provided from the domain, we've met a problem, that several HW (i.MX8 gpu in our

Re: [RFC PATCH 3/4] dt-bindings: panel: Introduce dual-link LVDS panel

On 03/01/2023 07:46, Aradhya Bhatia wrote: > Dual-link LVDS interfaces have 2 links, with even pixels traveling on > one link, and odd pixels on the other. These panels are also generic in > nature, with no documented constraints, much like their single-link > counterparts, "panel-lvds". > > Add a

Re: [PATCH v4 08/11] arm64: dts: qcom: sm8350: Use 2 interconnect cells

On Tue, 3 Jan 2023 at 08:59, Krzysztof Kozlowski wrote: > > On 02/01/2023 18:10, Robert Foss wrote: > > On Fri, 30 Dec 2022 at 17:12, Krzysztof Kozlowski > > wrote: > >> > >> On 30/12/2022 16:35, Robert Foss wrote: > >>> Use two interconnect cells in order to optionally > >>> support a path tag.

Re: [PATCH v4 08/11] arm64: dts: qcom: sm8350: Use 2 interconnect cells

On 03/01/2023 10:24, Robert Foss wrote: On which tree/revision did you base this? >>> >>> msm/drm-msm-display-for-6.2 >> >> Then it is not a proper base for DTS changes - you will miss quite some >> commits. The DTS patches should be based on Bjorn's SoC tree or >> linux-next (although the lat

Re: [PATCH v10 00/18] drm: Add Samsung MIPI DSIM bridge

Hi Marek, Am Sonntag, 18. Dezember 2022, 00:55:57 CET schrieb Marek Vasut: > On 12/16/22 14:25, Alexander Stein wrote: > Hi, > > [...] > > > Oh, nice, thanks for the pointer. When setting > > > >> samsung,burst-clock-frequency = <66825>; > > > > in imx8mm.dtsi > > I get a non-flickering di

Re: [PATCH] drm/vc4: Check for valid formats

On Mon, Jan 02, 2023 at 04:21:55PM +0100, Thomas Zimmermann wrote: > Hi > > Am 02.01.23 um 15:29 schrieb Maíra Canal: > > Hi, > > > > On 1/2/23 11:20, Thomas Zimmermann wrote: > > > Hi > > > > > > Am 02.01.23 um 14:57 schrieb Maíra Canal: > > > > Currently, vc4 is not checking valid formats befo

Re: [PATCH v2 00/11] Recover from failure to probe GPU

On 12/28/2022 10:00 PM, Mario Limonciello wrote: One of the first thing that KMS drivers do during initialization is destroy the system firmware framebuffer by means of `drm_aperture_remove_conflicting_pci_framebuffers` This means that if for any reason the GPU failed to probe the user will b

Re: [PATCH v3 02/12] dt-bindings: display: mediatek: add MT8195 hdmi bindings

Il 02/01/23 16:19, Guillaume Ranquet ha scritto: On Mon, 02 Jan 2023 15:14, AngeloGioacchino Del Regno wrote: Il 02/01/23 14:38, Guillaume Ranquet ha scritto: On Mon, 26 Dec 2022 06:18, CK Hu (胡俊光) wrote: Hi, Guillaume: On Fri, 2022-11-04 at 15:09 +0100, Guillaume Ranquet wrote: Add mt8195

Re: [Intel-gfx] [PATCH v2] drm/i915: dell wyse 3040 shutdown fix

On Mon, 02 Jan 2023, Alexey Lukyachuk wrote: > Regarding to your question about fdo gitlab, I went to do it. What's the URL for the issue? BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center

[PATCH v11 2/5] dt-bindings: display: bridge: cdns, dsi: Add compatible for dsi on j721e

Add compatible to support dsi bridge on j721e Signed-off-by: Rahul T R Reviewed-by: Rob Herring Reviewed-by: Laurent Pinchart --- .../bindings/display/bridge/cdns,dsi.yaml | 25 ++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindi

[PATCH v11 0/5] Add support for CDNS DSI J721E wrapper

Following series of patches adds supports for CDNS DSI bridge on j721e. v11: - Wrap commmit messages at 72 chars - Fix the order in Kconfig and Makefile - Clean up the includes, move macros and some headers to .c file - Add missing forward declarations - Add __ prefix to header gaurds - Chan

[PATCH v11 5/5] drm/bridge: cdns-dsi: Add support for J721E wrapper

Add support for wrapper settings for DSI bridge on j721e. Also enable DPI0 --- --- | ---| |--- | | DSS | DPI2 |->| DPI0 | DSI Wrapper | | ---| |--- | --- --

[PATCH v11 4/5] drm/bridge: cdns-dsi: Create a header file

Create a header file for cdns dsi and move structure definations to prepare for adding j721e wrapper support Signed-off-by: Rahul T R Reviewed-by: Tomi Valkeinen Reviewed-by: Laurent Pinchart --- .../gpu/drm/bridge/cadence/cdns-dsi-core.c| 48 +- .../gpu/drm/bridge/cadence/cdns

[PATCH v11 1/5] dt-bindings: display: bridge: Convert cdns, dsi.txt to yaml

Convert cdns,dsi.txt binding to yaml format Signed-off-by: Rahul T R Reviewed-by: Rob Herring Reviewed-by: Laurent Pinchart --- .../bindings/display/bridge/cdns,dsi.txt | 112 - .../bindings/display/bridge/cdns,dsi.yaml | 157 ++ 2 files changed, 157 insert

[PATCH v11 3/5] drm/bridge: cdns-dsi: Move to drm/bridge/cadence

Move the cadence dsi bridge under drm/bridge/cadence directory, to prepare for adding j721e wrapper support Signed-off-by: Rahul T R Reviewed-by: Tomi Valkeinen Reviewed-by: Laurent Pinchart --- drivers/gpu/drm/bridge/Kconfig| 11 --- drivers/gpu/drm/bridge/Make

Re: [PATCH v10 5/5] drm/bridge: cdns-dsi: Add support for J721E wrapper

Hi Laurent, Thanks for the detailed review I have addressed the review comments and sent v11 of this series On 15:32-20230102, Laurent Pinchart wrote: > Hi Rahul, > > Thank you for the patch. > > On Mon, Jan 02, 2023 at 03:39:42PM +0530, Rahul T R wrote: > > Add support for wrapper settings for

Re: [Intel-gfx] [PATCH v2] drm/i915: dell wyse 3040 shutdown fix

On Tue, 03 Jan 2023 12:14:02 +0200 Jani Nikula wrote: > On Mon, 02 Jan 2023, Alexey Lukyachuk wrote: > > Regarding to your question about fdo gitlab, I went to do it. > > What's the URL for the issue? > > BR, > Jani. > I have not submited issue in bug tracker because I found solution in git.

Re: [PATCH] drm/i915/display: Check source height is > 0

Hi Drew, this is good find. I went looking where the problem is in and saw what you probably also saw earlier. I was wondering if diff below would be better fix? I assume this would end up with einval or erange in your case but code flow otherwise would stay as is while fixing all future cal

Re: [PATCH v3] arch: rename all internal names __xchg to __arch_xchg

On Fri, Dec 30, 2022 at 03:15:52PM +0100, Andrzej Hajda wrote: > __xchg will be used for non-atomic xchg macro. > > Signed-off-by: Andrzej Hajda > Reviewed-by: Arnd Bergmann > --- > v2: squashed all arch patches into one > v3: fixed alpha/xchg_local, thx to l...@intel.com > --- ... > arch/s390/

[PULL] drm-misc-next

Hi Dave and Daniel, here's the first PR for drm-misc-next for the upcomming version v6.3 of the Linux kernel. Overall, it's fairly small; due to holidays, I guess. Noteworthy changes are in connector TV-mode handling, KUnit tests and MIPI helpers. Best regards Thomas drm-misc-next-2023-01-03: dr

Re: [PATCH v4 4/7] accel/ivpu: Add IPC driver and JSM messages

Hi, On 27.12.2022 16:34, Oded Gabbay wrote: > On Thu, Dec 8, 2022 at 1:08 PM Jacek Lawrynowicz > wrote: >> >> The IPC driver is used to send and receive messages to/from firmware >> running on the VPU. >> >> The only supported IPC message format is Job Submission Model (JSM) >> defined in vpu_jsm

Re: [PATCH v10 00/18] drm: Add Samsung MIPI DSIM bridge

Hi, Am Sonntag, 18. Dezember 2022, 23:28:20 CET schrieb Marek Vasut: > On 12/18/22 23:24, Adam Ford wrote: > > On Sat, Dec 17, 2022 at 10:33 PM Marek Vasut wrote: > >> On 12/18/22 05:23, Adam Ford wrote: > >>> On Sat, Dec 17, 2022 at 5:56 PM Marek Vasut wrote: > On 12/16/22 14:25, Alexander

Re: [RFC PATCH 3/4] dt-bindings: panel: Introduce dual-link LVDS panel

Hi Krzysztof, Thank you for reviewing the patches! On 03-Jan-23 14:02, Krzysztof Kozlowski wrote: On 03/01/2023 07:46, Aradhya Bhatia wrote: Dual-link LVDS interfaces have 2 links, with even pixels traveling on one link, and odd pixels on the other. These panels are also generic in nature, wit

Re: [RFC PATCH 3/4] dt-bindings: panel: Introduce dual-link LVDS panel

On 03/01/2023 12:02, Aradhya Bhatia wrote: > But this is throwing an error. I am confused what else could be done. > Can you please suggest what might be a more accurate check here? > >> >>> + required: >>> +- dual-lvds-odd-pixels >>> +then: >>> + prop

Re: [RFC PATCH 3/4] dt-bindings: panel: Introduce dual-link LVDS panel

Il 03/01/23 07:46, Aradhya Bhatia ha scritto: Dual-link LVDS interfaces have 2 links, with even pixels traveling on one link, and odd pixels on the other. These panels are also generic in nature, with no documented constraints, much like their single-link counterparts, "panel-lvds". Add a new co

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 Eduard Bloch (bl...@debian.org) changed: What|Removed |Added CC||bl...@debian.org --- Co

Re: [Intel-gfx] [RFC PATCH 00/20] Initial Xe driver submission

On 22/12/2022 22:21, Matthew Brost wrote: Hello, This is a submission for Xe, a new driver for Intel GPUs that supports both integrated and discrete platforms starting with Tiger Lake (first platform with Intel Xe Architecture). The intention of this new driver is to have a fresh base to work

Re: [PATCH AUTOSEL 5.15 24/27] Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10 properly""

Hello! Why is this revert for revert coming for 6.1 but reverted again for 6.1.2? My GPU is not working correctly again! https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.2 It seems like somebody made a mistake and pick up the wrong patch for the stable channel. Regards! On Sat, Nov 19

Re: [Intel-gfx] [PATCH v2] drm/i915: dell wyse 3040 shutdown fix

On Mon, Jan 02, 2023 at 04:56:49PM +0300, Alexey Lukyachuk wrote: > On Tue, 27 Dec 2022 20:40:03 +0300 > Alexey Lukyachuk wrote: > > > On Tue, 27 Dec 2022 11:39:25 -0500 > > Rodrigo Vivi wrote: > > > > > On Sun, Dec 25, 2022 at 09:55:08PM +0300, Alexey Lukyanchuk wrote: > > > > dell wyse 3040 d

[PATCH] drm/gem: Check for valid formats

Currently, drm_gem_fb_create() doesn't check if the pixel format is supported, which can lead to the acceptance of invalid pixel formats e.g. the acceptance of invalid modifiers. Therefore, add a check for valid formats on drm_gem_fb_create(). Moreover, note that this check is only valid for atomi

Re: [PATCH v2 2/3] iommu/sound: Use component_match_add_of helper

Hi Sean, On 22/12/2022 11:37 pm, Sean Anderson wrote: Convert users of component_match_add_release with component_release_of and component_compare_of to component_match_add_of. Signed-off-by: Sean Anderson Acked-by: Mark Brown --- Changes in v2: - Split off from helper addition drivers/io

Re: [Intel-gfx] [RFC PATCH 04/20] drm/sched: Convert drm scheduler to use a work queue rather than kthread

On 02/01/2023 07:30, Boris Brezillon wrote: On Fri, 30 Dec 2022 12:55:08 +0100 Boris Brezillon wrote: On Fri, 30 Dec 2022 11:20:42 +0100 Boris Brezillon wrote: Hello Matthew, On Thu, 22 Dec 2022 14:21:11 -0800 Matthew Brost wrote: In XE, the new Intel GPU driver, a choice has made

Re: [PATCH] drm/gem: Check for valid formats

Hi, thanks for the follow-up patch. Am 03.01.23 um 13:53 schrieb Maíra Canal: Currently, drm_gem_fb_create() doesn't check if the pixel format is supported, which can lead to the acceptance of invalid pixel formats e.g. the acceptance of invalid modifiers. Therefore, add a check for valid forma

Re: [Intel-gfx] [PATCH v2] drm/i915: dell wyse 3040 shutdown fix

On Tue, 03 Jan 2023, Rodrigo Vivi wrote: > On Mon, Jan 02, 2023 at 04:56:49PM +0300, Alexey Lukyachuk wrote: >> On Tue, 27 Dec 2022 20:40:03 +0300 >> Alexey Lukyachuk wrote: >> >> > On Tue, 27 Dec 2022 11:39:25 -0500 >> > Rodrigo Vivi wrote: >> > >> > > On Sun, Dec 25, 2022 at 09:55:08PM +0300

Re: [PATCH 3/9] drm/arm/hdlcd: use new debugfs device-centered functions

On Mon, Dec 26, 2022 at 12:50:23PM -0300, Maíra Canal wrote: > Replace the use of drm_debugfs_create_files() with the new > drm_debugfs_add_files() function, which center the debugfs files > management on the drm_device instead of drm_minor. Moreover, remove the > debugfs_init hook and add the debu

Re: [PATCH 09/18] vfio-mdev/mdpy-fb: Do not set struct fb_info.apertures

Am 20.12.22 um 10:32 schrieb Javier Martinez Canillas: [adding Kirti Wankhede and k...@vger.kernel.org to Cc list] On 12/19/22 17:05, Thomas Zimmermann wrote: Generic fbdev drivers use the apertures field in struct fb_info to control ownership of the framebuffer memory and graphics device. Do

Re: [RFC PATCH 00/20] Initial Xe driver submission

Hi, On Mon, 02 Jan 2023 13:42:46 +0200 Jani Nikula wrote: > On Mon, 02 Jan 2023, Thomas Zimmermann wrote: > > Hi > > > > Am 22.12.22 um 23:21 schrieb Matthew Brost: > >> Hello, > >> > >> This is a submission for Xe, a new driver for Intel GPUs that supports both > >> integrated and discrete

[PATCH v2] drm/gem: Check for valid formats

Currently, drm_gem_fb_create() doesn't check if the pixel format is supported, which can lead to the acceptance of invalid pixel formats e.g. the acceptance of invalid modifiers. Therefore, add a check for valid formats on drm_gem_fb_create(). Moreover, note that this check is only valid for atomi

Re: [PATCH] drm/nouveau/mmu: fix Use after Free bug in nvkm_vmm_node_split

On Fri, 30 Dec 2022 08:27:58 +0100, Zheng Wang wrote: > > Here is a function call chain. > nvkm_vmm_pfn_map->nvkm_vmm_pfn_split_merge->nvkm_vmm_node_split > If nvkm_vma_tail return NULL in nvkm_vmm_node_split, it will > finally invoke nvkm_vmm_node_merge->nvkm_vmm_node_delete, which > will free th

Re: [PATCH v2] drm/gem: Check for valid formats

Am 03.01.23 um 14:59 schrieb Maíra Canal: Currently, drm_gem_fb_create() doesn't check if the pixel format is supported, which can lead to the acceptance of invalid pixel formats e.g. the acceptance of invalid modifiers. Therefore, add a check for valid formats on drm_gem_fb_create(). Moreover

Re: [PATCH v2 00/11] Recover from failure to probe GPU

On Tue, Jan 3, 2023 at 5:10 AM Lazar, Lijo wrote: > > > > On 12/28/2022 10:00 PM, Mario Limonciello wrote: > > One of the first thing that KMS drivers do during initialization is > > destroy the system firmware framebuffer by means of > > `drm_aperture_remove_conflicting_pci_framebuffers` > > > >

Re: [Intel-gfx] [RFC PATCH 04/20] drm/sched: Convert drm scheduler to use a work queue rather than kthread

Hi, On Tue, 3 Jan 2023 13:02:15 + Tvrtko Ursulin wrote: > On 02/01/2023 07:30, Boris Brezillon wrote: > > On Fri, 30 Dec 2022 12:55:08 +0100 > > Boris Brezillon wrote: > > > >> On Fri, 30 Dec 2022 11:20:42 +0100 > >> Boris Brezillon wrote: > >> > >>> Hello Matthew, > >>> > >>> On Thu,

[PATCH 0/2] drm/panel: add support for the Visionox VTDR6130 AMOLED DSI panel

tions(+) --- base-commit: 1b929c02afd37871d5afb9d498426f83432e71c2 change-id: 20230103-topic-sm8550-upstream-vtdr6130-panel-f81dad976abd Best regards, -- Neil Armstrong

[PATCH 1/2] dt-bindings: display: panel: document the Visionox VTDR6130 AMOLED DSI Panel bindings

Document the 1080x2400 Visionox VTDR6130 AMOLED DSI Panel bindings. Signed-off-by: Neil Armstrong --- .../bindings/display/panel/visionox,vtdr6130.yaml | 53 ++ 1 file changed, 53 insertions(+) diff --git a/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.

[PATCH 2/2] drm/panel: add visionox vtdr6130 DSI panel driver

Add support for the 1080x2400 Visionox VTDR6130 AMOLED DSI panel found on the Qualcomm SM8550 MTP board. By default the the panel is configured to work with DSI compressed streams, but can work in uncompressed video mode since 1080x2400 in RGB888 fits in the 4 DSI lanes bandwidth. While display c

Re: [RFC PATCH 00/20] Initial Xe driver submission

> > For one thing, setting that up would be a lot of up front infrastructure > > work. I'm not sure how to even pull that off when Xe is still > > out-of-tree and i915 development plunges on upstream as ever. > > > > For another, realistically, the overlap between supported platforms is > > going

[PULL] drm-misc-next-fixes

Hi Daniel, Dave, Here's the drm-misc-next-fixes leftovers. Maxime drm-misc-next-fixes-2023-01-03: The drm-misc-next-fixes leftovers. It addresses a bug in drm/scheduler ending up causing a lockup, and reduces the stack usage of some drm/mm kunit tests. The following changes since commit b02897e5

[PATCH] drm/docs: Explicitly document default CRTC background behavior

From: Sean Paul Add a paragraph explaining that the default behavior for areas which are not covered by planes or where planes are blending with the CRTC background, is black. This is alluded to in the "pixel blend mode" property docs, but not called out explicitly. Signed-off-by: Sean Paul --

Re: [PATCH] drm: Replace DRM_DEBUG with drm_dbg_core in file and ioctl handling

On 23/12/2022 11:26, Simon Ser wrote: Reviewed-by: Simon Ser Thanks - adding some drm-misc maintainers to consider pulling the patch in. Regards, Tvrtko

Re: [PATCH] drm: Replace DRM_DEBUG with drm_dbg_core in file and ioctl handling

On Tuesday, January 3rd, 2023 at 16:37, Tvrtko Ursulin wrote: > On 23/12/2022 11:26, Simon Ser wrote: > > > Reviewed-by: Simon Ser cont...@emersion.fr > > Thanks - adding some drm-misc maintainers to consider pulling the patch in. I can push the patches if you don't have commit rights.

Re: [syzbot] WARNING: locking bug in inet_autobind

The regression point doesn't make sense. The kernel config doesn't enable CONFIG_DRM_AMDGPU, so there is no way that a change in AMDGPU could have caused this regression. Regards,   Felix Am 2022-12-29 um 01:26 schrieb syzbot: syzbot has found a reproducer for the following issue on: HEAD c

[PATCH v2] drm/msm: another fix for the headless Adreno GPU

Fix another oops reproducible when rebooting the board with the Adreno GPU wokring in the headless mode (e.g. iMX platforms). Unable to handle kernel NULL pointer dereference at virtual address when read [] *pgd=74936831, *pte=, *ppte= Internal error: Oops: 17 [#1

Re: [syzbot] WARNING: locking bug in inet_autobind

On 1/3/23 10:39, Felix Kuehling wrote: The regression point doesn't make sense. The kernel config doesn't enable CONFIG_DRM_AMDGPU, so there is no way that a change in AMDGPU could have caused this regression. I agree. It is likely a pre-existing problem or caused by another commit that got t

Re: [Intel-gfx] [PATCH v2] drm/i915: dell wyse 3040 shutdown fix

On Tue, 3 Jan 2023 07:46:40 -0500 Rodrigo Vivi wrote: > On Mon, Jan 02, 2023 at 04:56:49PM +0300, Alexey Lukyachuk wrote: > > On Tue, 27 Dec 2022 20:40:03 +0300 > > Alexey Lukyachuk wrote: > > > > > On Tue, 27 Dec 2022 11:39:25 -0500 > > > Rodrigo Vivi wrote: > > > > > > > On Sun, Dec 25, 202

Re: [PATCH v2 2/3] iommu/sound: Use component_match_add_of helper

Hi Robin, On Tue, Jan 03, 2023 at 01:01:07PM +, Robin Murphy wrote: > Hi Sean, > > On 22/12/2022 11:37 pm, Sean Anderson wrote: > > Convert users of component_match_add_release with component_release_of > > and component_compare_of to component_match_add_of. > > > > Signed-off-by: Sean Ander

Re: [Intel-gfx] [PATCH v2] drm/i915: dell wyse 3040 shutdown fix

On Tue, Jan 03, 2023 at 07:09:20PM +0300, Alexey Lukyachuk wrote: > On Tue, 3 Jan 2023 07:46:40 -0500 > Rodrigo Vivi wrote: > > > On Mon, Jan 02, 2023 at 04:56:49PM +0300, Alexey Lukyachuk wrote: > > > On Tue, 27 Dec 2022 20:40:03 +0300 > > > Alexey Lukyachuk wrote: > > > > > > > On Tue, 27 Dec

Re: [syzbot] WARNING: locking bug in inet_autobind

Am 2023-01-03 um 11:05 schrieb Waiman Long: On 1/3/23 10:39, Felix Kuehling wrote: The regression point doesn't make sense. The kernel config doesn't enable CONFIG_DRM_AMDGPU, so there is no way that a change in AMDGPU could have caused this regression. I agree. It is likely a pre-existing

Re: [PATCH v2 2/3] iommu/sound: Use component_match_add_of helper

On 1/3/23 11:15, Maxime Ripard wrote: > Hi Robin, > > On Tue, Jan 03, 2023 at 01:01:07PM +, Robin Murphy wrote: >> Hi Sean, >> >> On 22/12/2022 11:37 pm, Sean Anderson wrote: >> > Convert users of component_match_add_release with component_release_of >> > and component_compare_of to component

Re: [PATCH] drm: Replace DRM_DEBUG with drm_dbg_core in file and ioctl handling

On 03/01/2023 15:39, Simon Ser wrote: On Tuesday, January 3rd, 2023 at 16:37, Tvrtko Ursulin wrote: On 23/12/2022 11:26, Simon Ser wrote: Reviewed-by: Simon Ser cont...@emersion.fr Thanks - adding some drm-misc maintainers to consider pulling the patch in. I can push the patches if yo

Re: [PATCH v2 2/3] iommu/sound: Use component_match_add_of helper

On 03/01/2023 4:15 pm, Maxime Ripard wrote: Hi Robin, On Tue, Jan 03, 2023 at 01:01:07PM +, Robin Murphy wrote: Hi Sean, On 22/12/2022 11:37 pm, Sean Anderson wrote: Convert users of component_match_add_release with component_release_of and component_compare_of to component_match_add_of.

Re: [PATCH v16 1/5] arm64: dts: qcom: add data-lanes and link-freuencies into dp_out endpoint

Hi Krzysztof/Dmitry, Would you please review this patch. Thanks, On 12/27/2022 9:44 AM, Kuogee Hsieh wrote: Move data-lanes property from mdss_dp node to dp_out endpoint. Also add link-frequencies property into dp_out endpoint as well. The last frequency specified at link-frequencies will be

Re: [PATCH] drm: Replace DRM_DEBUG with drm_dbg_core in file and ioctl handling

Pushed, thanks!

Re: [PATCH 1/2] dt-bindings: display: panel: document the Visionox VTDR6130 AMOLED DSI Panel bindings

Hi Neil, On Tue, Jan 03, 2023 at 03:22:27PM +0100, Neil Armstrong wrote: > Document the 1080x2400 Visionox VTDR6130 AMOLED DSI Panel bindings. > > Signed-off-by: Neil Armstrong > --- > .../bindings/display/panel/visionox,vtdr6130.yaml | 53 > ++ > 1 file changed, 53 insert

Re: renesas/master bisection: igt-kms-rockchip.kms_vblank.pipe-A-wait-forked on rk3399-gru-kevin

On 12/21/22 23:02, Brian Norris wrote: > Hi Mark, Sean, (and dri-devel) > > On Wed, Dec 14, 2022 at 07:04:37PM -0800, Brian Norris wrote: >> On Tue, Dec 13, 2022 at 04:51:11PM +, Mark Brown wrote: >>> On Tue, Dec 13, 2022 at 05:56:30AM -0800, KernelCI bot wrote: >>> >>> The KernelCI bisection

Re: [PATCH 2/2] drm/panel: add visionox vtdr6130 DSI panel driver

Hi Neil, On Tue, Jan 03, 2023 at 03:22:28PM +0100, Neil Armstrong wrote: > Add support for the 1080x2400 Visionox VTDR6130 AMOLED DSI panel > found on the Qualcomm SM8550 MTP board. > > By default the the panel is configured to work with DSI compressed > streams, but can work in uncompressed vide

Re: [PATCH] drm/docs: Explicitly document default CRTC background behavior

Nice! Reviewed-by: Simon Ser

[PATCH AUTOSEL 6.1 04/10] drm/amd/display: Report to ACPI video if no panels were found

From: Mario Limonciello [ Upstream commit c573e240609ff781a0246c0c8c8351abd0475287 ] On desktop APUs amdgpu doesn't create a native backlight device as no eDP panels are found. However if the BIOS has reported backlight control methods in the ACPI tables then an acpi_video0 backlight device wil

[PATCH v7 0/4] drm/panel: Add Magnachip D53E6EA8966 Panel Controller

From: Chris Morgan Add the Magnachip D53E6EA8966 panel IC controller for display panels such as the Samsung AMS495QA01 panel as found on the Anbernic RG503. This panel uses DSI to receive video signals, but 3-wire SPI to receive command signals using DBI. Changes since V6: - Fixed a trivial err

[PATCH V7 2/4] dt-bindings: display: panel: Add Samsung AMS495QA01

From: Chris Morgan Add documentation for Samsung AMS495QA01 panel (with Magnachip D53E6EA8966 controller IC). Signed-off-by: Chris Morgan Signed-off-by: Maya Matuszczyk --- .../display/panel/samsung,ams495qa01.yaml | 57 +++ 1 file changed, 57 insertions(+) create mode 10

[PATCH V7 1/4] drm: of: Add drm_of_get_dsi_bus helper function

From: Chris Morgan Add helper function to find DSI host for devices where DSI panel is not a minor of a DSI bus (such as the Samsung AMS495QA01 panel or the official Raspberry Pi touchscreen display). Signed-off-by: Chris Morgan Signed-off-by: Maya Matuszczyk Reviewed-by: Linus Walleij --- d

[PATCH V7 4/4] arm64: dts: rockchip: add display to RG503

From: Chris Morgan Add Samsung AMS495QA01 panel to RG503. Signed-off-by: Chris Morgan Signed-off-by: Maya Matuszczyk --- .../dts/rockchip/rk3566-anbernic-rg503.dts| 55 +++ 1 file changed, 55 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3566-anbernic-rg503.dt

[PATCH V7 3/4] drm/panel: Add Magnachip D53E6EA8966 Panel Driver

From: Chris Morgan Support Magnachip D53E6EA8966 based panels such as the Samsung AMS495QA01 panel as found on the Anbernic RG503. Note this driver supports only the AMS495QA01 today which receives video signals via DSI, however it receives commands via 3-wire SPI using DBI. Signed-off-by: Chris

Re: [PATCH] drm/v3d: replace open-coded implementation of drm_gem_object_lookup

On 12/28, Melissa Wen wrote: > On 12/27, Maíra Canal wrote: > > As v3d_submit_tfu_ioctl() performs the same steps as > > drm_gem_object_lookup(), > > replace the open-code implementation in v3d with its DRM core equivalent. > > > > Signed-off-by: Maíra Canal > > --- > > drivers/gpu/drm/v3d/v3d_

Re: [PATCH V7 1/4] drm: of: Add drm_of_get_dsi_bus helper function

Hi Chris. On Tue, Jan 03, 2023 at 01:07:04PM -0600, Chris Morgan wrote: > From: Chris Morgan > > Add helper function to find DSI host for devices where DSI panel is not > a minor of a DSI bus (such as the Samsung AMS495QA01 panel or the > official Raspberry Pi touchscreen display). > > Signed-o

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Consolidate TLB invalidation flow

On Mon, Dec 19, 2022 at 05:10:02PM +0100, Andrzej Hajda wrote: > On 19.12.2022 11:13, Tvrtko Ursulin wrote: > > From: Tvrtko Ursulin > > > > As the logic for selecting the register and corresponsing values grew, the > > corresponding > > > code become a bit unsightly. Consolidate by storing the

Re: [PULL] drm-misc-next-fixes

On Tue, Jan 03, 2023 at 03:49:26PM +0100, Maxime Ripard wrote: > Hi Daniel, Dave, > > Here's the drm-misc-next-fixes leftovers. > > Maxime > > drm-misc-next-fixes-2023-01-03: > The drm-misc-next-fixes leftovers. It addresses a bug in drm/scheduler > ending up causing a lockup, and reduces the st

Re: [PATCH V7 3/4] drm/panel: Add Magnachip D53E6EA8966 Panel Driver

Hi Chris. On Tue, Jan 03, 2023 at 01:07:06PM -0600, Chris Morgan wrote: > From: Chris Morgan > > Support Magnachip D53E6EA8966 based panels such as the Samsung > AMS495QA01 panel as found on the Anbernic RG503. Note this driver > supports only the AMS495QA01 today which receives video signals vi

Re: [PATCH v2] drm/amdgpu: Retry DDC probing on DVI on failure if we got an HPD interrupt

On Fri, Dec 23, 2022 at 9:23 AM xurui wrote: > > HPD signals on DVI ports can be fired off before the pins required for > DDC probing actually make contact, due to the pins for HPD making > contact first. This results in a HPD signal being asserted but DDC > probing failing, resulting in hotpluggi

Re: [PATCH v3 11/13] drm/fb-helper: Fix single-probe color-format selection

Hi Thomas, On 1/2/23 08:29, Thomas Zimmermann wrote: Fix the color-format selection of the single-probe helper. Go through all user-specified values and test each for compatibility with the driver. If none is supported, use the driver-provided default. This guarantees that the console is always

[PATCH v4 00/27] Recover from failure to probe GPU

One of the first thing that KMS drivers do during initialization is destroy the system firmware framebuffer by means of `drm_aperture_remove_conflicting_pci_framebuffers` This means that if for any reason the GPU failed to probe the user will be stuck with at best a screen frozen at the last thing

[PATCH v4 01/27] drm/amd: Delay removal of the firmware framebuffer

Removing the firmware framebuffer from the driver means that even if the driver doesn't support the IP blocks in a GPU it will no longer be functional after the driver fails to initialize. This change will ensure that unsupported IP blocks at least cause the driver to work with the EFI framebuffer

[PATCH v4 03/27] drm/amd: Convert SMUv11 microcode to use `amdgpu_ucode_ip_version_decode`

Remove the special casing from SMU v11 code. No intended functional changes. Signed-off-by: Mario Limonciello Acked-by: Christian König --- v3->v4: * No changes --- .../gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c| 35 ++- 1 file changed, 3 insertions(+), 32 deletions(-) diff --

[PATCH v4 04/27] drm/amd: Convert SMUv13 microcode to use `amdgpu_ucode_ip_version_decode`

The special case for the one dGPU has been moved into `amdgpu_ucode_ip_version_decode`, so simplify this code. Reviewed-by: Alex Deucher Signed-off-by: Mario Limonciello Acked-by: Christian König --- v3->v4: * No changes --- drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0.c | 12 ++-- 1

[PATCH v4 02/27] drm/amd: Add a legacy mapping to "amdgpu_ucode_ip_version_decode"

This will allow other parts of the driver that currently special case firmware file names to before IP version style naming to just have a single call to `amdgpu_ucode_ip_version_decode`. Signed-off-by: Mario Limonciello Acked-by: Christian König --- v3->v4: * No changes v2->v3: * Fixes for GF

[PATCH v4 05/27] drm/amd: Add a new helper for loading/validating microcode

All microcode runs a basic validation after it's been loaded. Each IP block as part of init will run both. Introduce a wrapper for request_firmware and amdgpu_ucode_validate. This wrapper will also remap any error codes from request_firmware to -ENODEV. This is so that early_init will fail if fir

[PATCH v4 06/27] drm/amd: Use `amdgpu_ucode_load` helper for SDMA

The `amdgpu_ucode_load` helper will ensure that the return code for missing firmware is -ENODEV so that early_init can fail. Signed-off-by: Mario Limonciello --- v3->v4: * New patch --- drivers/gpu/drm/amd/amdgpu/amdgpu_sdma.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --

[PATCH v4 07/27] drm/amd: Convert SDMA to use `amdgpu_ucode_ip_version_decode`

Simplifies the code so that all SDMA versions will get the firmware name from `amdgpu_ucode_ip_version_decode`. Signed-off-by: Mario Limonciello --- v3->v4: * Move out of IP discovery and instead simplify early_init v2->v3: * Fix dGPU naming scheme --- drivers/gpu/drm/amd/amdgpu/amdgpu_sdma.c

[PATCH v4 10/27] drm/amd: Load VCN microcode during early_init

Simplifies the code so that all VCN versions will get the firmware name from `amdgpu_ucode_ip_version_decode` and then use this filename to load microcode as part of the early_init process. Signed-off-by: Mario Limonciello --- v3->v4: * Move out of IP discovery and introduce early_init phase for

[PATCH v4 08/27] drm/amd: Make SDMA firmware load failures less noisy.

When firmware is missing we get failures at every step. ``` [3.855086] amdgpu :04:00.0: Direct firmware load for amdgpu/green_sardine_sdma.bin failed with error -2 [3.855087] [drm:amdgpu_sdma_init_microcode [amdgpu]] *ERROR* SDMA: Failed to init firmware "amdgpu/green_sardine_sdma.bin

  1   2   >