Re: [PATCH v1 0/3] Add support for next gen eDP driver on SnapDragon

On 2021-05-05 15:31, Dmitry Baryshkov wrote: Hi, On Wed, 5 May 2021 at 11:17, Sankeerth Billakanti wrote: These patches add support for the next generation eDP driver on SnapDragon with dpu support. The existing eDP driver cannot support the new eDP hardware. So, to maintain backward compat

[PATCH v1 3/3] drm/msm/disp/dpu1: add support for edp encoder

This change will enable dpu encoder support for the native eDP interface on next generation snapdragon platforms. Signed-off-by: Sankeerth Billakanti --- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 7 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 33 + 2 fil

[PATCH v1 2/3] drm/msm/edp: add support for next gen edp

The eDP controller and phy hardware for the next generation snapdragon platform has a different desgin compared to their earlier generations. So, there is a need to implement new sequences in driver software for the new hardware. This change will implement the required seuqences to enable eDP inte

[PATCH v1 0/3] Add support for next gen eDP driver on sc7280

These patches add support for the next generation eDP driver on SnapDragon with dpu support. The existing eDP driver cannot support the new eDP hardware. So, to maintain backward compatibility, the older eDP driver is moved to v200 folder and the new generation eDP driver is added in the v510 folde

Re: [PATCH 1/5] drm/fourcc: Add 16 bpc fixed point framebuffer formats.

On Sat, Mar 20, 2021 at 04:09:47AM +0200, Ville Syrjälä wrote: > On Fri, Mar 19, 2021 at 10:45:10PM +0100, Mario Kleiner wrote: > > On Fri, Mar 19, 2021 at 10:16 PM Ville Syrjälä > > wrote: > > > > > > On Fri, Mar 19, 2021 at 10:03:13PM +0100, Mario Kleiner wrote: > > > > These are 16 bits per col

Re: [PATCH v15 2/4] dt-bindings: msm: dsi: add yaml schemas for DSI bindings

On 2021-04-08 20:33, Rob Herring wrote: On Mon, Apr 05, 2021 at 04:36:08PM +0530, Krishna Manikandan wrote: Add YAML schema for the device tree bindings for DSI Signed-off-by: Krishna Manikandan Changes in v1: - Separate dsi controller bindings to a separate patch (Stephen Boyd) - M

[pull] radeon, amdgpu drm-fixes-5.13

Hi Dave, Daniel, Fixes for 5.13. The following changes since commit a1a1ca70deb3ec600eeabb21de7f3f48aaae5695: Merge tag 'drm-misc-next-fixes-2021-04-22' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2021-04-23 13:53:07 +1000) are available in the Git repository at: https:/

Re: [PATCH] fbmem: Correct position of '__maybe_unused' in proc_fb_seq_ops

On Wed, May 05, 2021 at 11:28:08AM -0700, Nathan Chancellor wrote: > Clang warns: > > drivers/video/fbdev/core/fbmem.c:736:21: warning: attribute > declaration must precede definition [-Wignored-attributes] > static const struct __maybe_unused seq_operations proc_fb_seq_ops = { >

[Bug 212959] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link!

https://bugzilla.kernel.org/show_bug.cgi?id=212959 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

Re: [PATCH v1 2/3] drm/msm/edp: add support for next gen edp

Hi Sankeerth, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on drm-intel/for-linux-next] [also build test WARNING on drm-tip/drm-tip drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next linus/master v5.12 next-20210505] [cannot apply to drm/drm-next] [If

Re: 16 bpc fixed point (RGBA16) framebuffer support for core and AMD.

On Wed, Apr 28, 2021 at 11:22 PM Alex Deucher wrote: > > On Tue, Apr 20, 2021 at 5:25 PM Alex Deucher wrote: > > > > On Fri, Apr 16, 2021 at 12:29 PM Mario Kleiner > > wrote: > > > > > > Friendly ping to the AMD people. Nicholas, Harry, Alex, any feedback? > > > Would be great to get this in soo

[Bug 212959] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link!

https://bugzilla.kernel.org/show_bug.cgi?id=212959 tob88...@gmail.com changed: What|Removed |Added CC||tob88...@gmail.com --- Comment #1 fr

[Bug 212959] New: [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link!

https://bugzilla.kernel.org/show_bug.cgi?id=212959 Bug ID: 212959 Summary: [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! Product: Drivers Version: 2.5 Kernel Version: 5.4, 5.8 Hardwa

Re: [PATCHv2 4/5] dt-bindings: arm: fsl: add GE B1x5pv2 boards

On Thu, 29 Apr 2021 00:29:52 +0200, Sebastian Reichel wrote: > Document the compatible for GE B1x5pv2 boards. > > Signed-off-by: Sebastian Reichel > --- > Documentation/devicetree/bindings/arm/fsl.yaml | 11 +++ > 1 file changed, 11 insertions(+) > Acked-by: Rob Herring

Re: [PATCHv2 3/5] dt-bindings: vendor-prefixes: add congatec

On Thu, 29 Apr 2021 00:29:51 +0200, Sebastian Reichel wrote: > Document binding for congatec. > > Signed-off-by: Sebastian Reichel > --- > Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ > 1 file changed, 2 insertions(+) > Acked-by: Rob Herring

Re: [PATCHv2 1/5] rtc: m41t80: add support for fixed clock

On Thu, 29 Apr 2021 00:29:49 +0200, Sebastian Reichel wrote: > Congatec's QMX6 system on module (SoM) uses a m41t62 as RTC. The > modules SQW clock output defaults to 32768 Hz. This behaviour is > used to provide the i.MX6 CKIL clock. Once the RTC driver is probed, > the clock is disabled and all i

[Bug 212957] [radeon] kernel NULL pointer dereference during system boot

https://bugzilla.kernel.org/show_bug.cgi?id=212957 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

[Bug 212957] New: [radeon] kernel NULL pointer dereference during system boot

https://bugzilla.kernel.org/show_bug.cgi?id=212957 Bug ID: 212957 Summary: [radeon] kernel NULL pointer dereference during system boot Product: Drivers Version: 2.5 Kernel Version: 5.12.1 Hardware: x86-64

Re: [PATCH 2/3] Restructure output format computation for better expandability

Hi Werner, Thank you for the patch! Yet something to improve: [auto build test ERROR on drm-intel/for-linux-next] [also build test ERROR on next-20210505] [cannot apply to v5.12] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use

Re: [PATCH 8/8] drm/modifiers: Enforce consistency between the cap an IN_FORMATS

On Tue, Apr 27, 2021 at 11:20 AM Daniel Vetter wrote: > > It's very confusing for userspace to have to deal with inconsistencies > here, and some drivers screwed this up a bit. Most just ommitted the > format list when they meant to say that only linear modifier is > allowed, but some also meant t

[syzbot] WARNING in drm_wait_one_vblank

Hello, syzbot found the following issue on: HEAD commit:d2b6f8a1 Merge tag 'xfs-5.13-merge-3' of git://git.kernel... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12c5b2c3d0 kernel config: https://syzkaller.appspot.com/x/.config?x=65c207250bba4efe das

Re: [RESEND PATCH] drm/rockchip: dsi: move all lane config except LCDC mux to bind()

On Mon, 19 Apr 2021 at 02:04, Thomas Hebb wrote: > > When we first enable the DSI encoder, we currently program some per-chip > configuration that we look up in rk3399_chip_data based on the device > tree compatible we match. This data configures various parameters of the > MIPI lanes, including o

[PATCH 5/6] drm/vmwgfx: Add basic support for SVGA3

SVGA3 is the next version of our PCI device. Some of the changes include using MMIO for register accesses instead of ioports, deprecating the FIFO MMIO and removing a lot of the old and legacy functionality. SVGA3 doesn't support guest backed objects right now so everything except 3D is working. v

Re: [PATCH 2/3] Restructure output format computation for better expandability

Hi Werner, Thank you for the patch! Yet something to improve: [auto build test ERROR on drm-intel/for-linux-next] [also build test ERROR on next-20210505] [cannot apply to v5.12] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use

[PATCH] drm: bridge: make a const array static, makes object smaller

From: Colin Ian King Don't populate the const array frs_limits on the stack but instead it static. Makes the object code smaller by 128 bytes: Before: textdata bss dec hex filename 248357440 64 323397e53 drivers/gpu/drm/bridge/tc358768.o After: textdat

[PATCH] fbmem: Correct position of '__maybe_unused' in proc_fb_seq_ops

Clang warns: drivers/video/fbdev/core/fbmem.c:736:21: warning: attribute declaration must precede definition [-Wignored-attributes] static const struct __maybe_unused seq_operations proc_fb_seq_ops = { ^ ./include/linux/compiler_attributes.h:273:56: note: expanded from mac

[PATCH 3/3] Use YCbCr420 as fallback when RGB fails

When encoder validation of a display mode fails, retry with less bandwidth heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups to support 4k60Hz output, which previously failed silently. AMDGPU had nearly the exact same issue. This problem description is therefore copied fro

[PATCH 2/3] Restructure output format computation for better expandability

Couples the decission between RGB and YCbCr420 mode and the check if the port clock can archive the required frequency. Other checks and configuration steps that where previously done in between can also be done before or after. This allows for are cleaner implementation of retrying different colo

[PATCH 1/3] New function to avoid duplicate code in upcomming commits

Moves some checks that later will be performed 2 times to an own fuction. This avoids duplicate code later on. Signed-off-by: Werner Sembach --- >From 42a4a3a7d9ea9948b4071f406e7fcae23bfa0bdf Mon Sep 17 00:00:00 2001 From: Werner Sembach Date: Mon, 3 May 2021 14:35:39 +0200 Subject: [PATCH 1/3]

[PATCH 0/3] drm/i915/display Try YCbCr420 color when RGB fails

When encoder validation of a display mode fails, retry with less bandwidth heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups to support 4k60Hz output, which previously failed silently. AMDGPU had nearly the exact same issue. This problem description is therefore copied fro

Re: [PATCH] drm/bridge: fix LONTIUM_LT8912B dependencies

On Wed, May 05, 2021 at 12:02:07AM +0200, Adrien Grassein wrote: > LONTIUM_LT8912B uses "drm_display_mode_to_videomode" from > DRM framework that needs VIDEOMODE_HELPERS to be enabled. > > Fixes: 30e2ae943c26 ("drm/bridge: Introduce LT8912B DSI to HDMI bridge") > Reported-by: Michal Suchánek > Si

[PATCH 3/3] Use YCbCr420 as fallback when RGB fails

When encoder validation of a display mode fails, retry with less bandwidth heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups to support 4k60Hz output, which previously failed silently. AMDGPU had nearly the exact same issue. This problem description is therefore copied fro

[PATCH 0/3] drm/i915/display Try YCbCr420 color when RGB fails

When encoder validation of a display mode fails, retry with less bandwidth heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups to support 4k60Hz output, which previously failed silently. AMDGPU had nearly the exact same issue. This problem description is therefore copied fro

[PATCH 2/3] Restructure output format computation for better expandability

Couples the decission between RGB and YCbCr420 mode and the check if the port clock can archive the required frequency. Other checks and configuration steps that where previously done in between can also be done before or after. This allows for are cleaner implementation of retrying different colo

[PATCH 1/3] New function to avoid duplicate code in upcomming commits

Moves some checks that later will be performed 2 times to an own fuction. This avoids duplicate code later on. Signed-off-by: Werner Sembach --- >From 42a4a3a7d9ea9948b4071f406e7fcae23bfa0bdf Mon Sep 17 00:00:00 2001 From: Werner Sembach Date: Mon, 3 May 2021 14:35:39 +0200 Subject: [PATCH 1/3]

Re: [PATCH 12/13] drm/vmwgfx: switch the TTM backends to self alloc

On Fri, 30 Apr 2021 at 10:25, Christian König wrote: > > Similar to the TTM range manager. > > Signed-off-by: Christian König Reviewed-by: Matthew Auld ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/lis

Re: [PATCH 08/13] drm/amdgpu: revert "drm/amdgpu: stop allocating dummy GTT nodes"

On Fri, 30 Apr 2021 at 10:25, Christian König wrote: > > TTM is going to need this again since we are moving the resource > allocation into the backend. > > Signed-off-by: Christian König Acked-by: Matthew Auld ___ dri-devel mailing list dri-devel@list

Re: [PATCH 11/13] drm/nouveau: switch the TTM backends to self alloc

On Mon, 3 May 2021 at 12:14, Christian König wrote: > > Am 30.04.21 um 17:02 schrieb Matthew Auld: > > On Fri, 30 Apr 2021 at 10:25, Christian König > > wrote: > >> Similar to the TTM range manager. > >> > >> Signed-off-by: Christian König > >> --- > >> drivers/gpu/drm/nouveau/nouveau_mem.h |

Re: [PATCH 13/13] drm/ttm: flip the switch for driver allocated resources

On Fri, 30 Apr 2021 at 10:25, Christian König wrote: > > Instead of both driver and TTM allocating memory finalize embedding the > ttm_resource object as base into the driver backends. > > Signed-off-by: Christian König > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c | 44 ++ >

[PATCH AUTOSEL 5.4 38/46] drm/amd/display: fixed divide by zero kernel crash during dsc enablement

From: Robin Singh [ Upstream commit 19cc1f3829567e7dca21c1389ea6407b8f5efab4 ] [why] During dsc enable, a divide by zero condition triggered the kernel crash. [how] An IGT test, which enable the DSC, was crashing at the time of restore the default dsc status, becaue of h_totals value becoming 0

[PATCH AUTOSEL 5.4 26/46] drm/amd/display: Force vsync flip when reconfiguring MPCC

From: Anthony Wang [ Upstream commit 56d63782af9bbd1271bff1422a6a013123eade4d ] [Why] Underflow observed when disabling PIP overlay in-game when vsync is disabled, due to OTC master lock not working with game pipe which is immediate flip. [How] When performing a full update, override flip_immed

[PATCH AUTOSEL 5.10 68/85] drm/amdgpu: Add mem sync flag for IB allocated by SA

From: Jinzhou Su [ Upstream commit 5c88e3b86a88f14efa0a3ddd28641c6ff49fb9c4 ] The buffer of SA bo will be used by many cases. So it's better to invalidate the cache of indirect buffer allocated by SA before commit the IB. Signed-off-by: Jinzhou Su Reviewed-by: Christian König Signed-off-by: A

[PATCH AUTOSEL 5.10 67/85] drm/amd/display: add handling for hdcp2 rx id list validation

From: "Dingchen (David) Zhang" [ Upstream commit 4ccf9446b2a3615615045346c97f8a1e2a16568a ] [why] the current implementation of hdcp2 rx id list validation does not have handler/checker for invalid message status, e.g. HMAC, the V parameter calculated from PSP not matching the V prime from Rx.

[PATCH AUTOSEL 5.10 66/85] drm/amd/display: fixed divide by zero kernel crash during dsc enablement

From: Robin Singh [ Upstream commit 19cc1f3829567e7dca21c1389ea6407b8f5efab4 ] [why] During dsc enable, a divide by zero condition triggered the kernel crash. [how] An IGT test, which enable the DSC, was crashing at the time of restore the default dsc status, becaue of h_totals value becoming 0

[PATCH AUTOSEL 5.10 52/85] drm/amd/display: Force vsync flip when reconfiguring MPCC

From: Anthony Wang [ Upstream commit 56d63782af9bbd1271bff1422a6a013123eade4d ] [Why] Underflow observed when disabling PIP overlay in-game when vsync is disabled, due to OTC master lock not working with game pipe which is immediate flip. [How] When performing a full update, override flip_immed

[PATCH AUTOSEL 5.11 087/104] drm/amdgpu: Add mem sync flag for IB allocated by SA

From: Jinzhou Su [ Upstream commit 5c88e3b86a88f14efa0a3ddd28641c6ff49fb9c4 ] The buffer of SA bo will be used by many cases. So it's better to invalidate the cache of indirect buffer allocated by SA before commit the IB. Signed-off-by: Jinzhou Su Reviewed-by: Christian König Signed-off-by: A

[PATCH AUTOSEL 5.11 086/104] drm/amd/display: add handling for hdcp2 rx id list validation

From: "Dingchen (David) Zhang" [ Upstream commit 4ccf9446b2a3615615045346c97f8a1e2a16568a ] [why] the current implementation of hdcp2 rx id list validation does not have handler/checker for invalid message status, e.g. HMAC, the V parameter calculated from PSP not matching the V prime from Rx.

[PATCH AUTOSEL 5.11 085/104] drm/amd/display: fixed divide by zero kernel crash during dsc enablement

From: Robin Singh [ Upstream commit 19cc1f3829567e7dca21c1389ea6407b8f5efab4 ] [why] During dsc enable, a divide by zero condition triggered the kernel crash. [how] An IGT test, which enable the DSC, was crashing at the time of restore the default dsc status, becaue of h_totals value becoming 0

[PATCH AUTOSEL 5.11 068/104] drm/amd/display: Force vsync flip when reconfiguring MPCC

From: Anthony Wang [ Upstream commit 56d63782af9bbd1271bff1422a6a013123eade4d ] [Why] Underflow observed when disabling PIP overlay in-game when vsync is disabled, due to OTC master lock not working with game pipe which is immediate flip. [How] When performing a full update, override flip_immed

[PATCH AUTOSEL 5.12 095/116] drm/amd/display: fixed divide by zero kernel crash during dsc enablement

From: Robin Singh [ Upstream commit 19cc1f3829567e7dca21c1389ea6407b8f5efab4 ] [why] During dsc enable, a divide by zero condition triggered the kernel crash. [how] An IGT test, which enable the DSC, was crashing at the time of restore the default dsc status, becaue of h_totals value becoming 0

[PATCH AUTOSEL 5.12 097/116] drm/amdgpu: Add mem sync flag for IB allocated by SA

From: Jinzhou Su [ Upstream commit 5c88e3b86a88f14efa0a3ddd28641c6ff49fb9c4 ] The buffer of SA bo will be used by many cases. So it's better to invalidate the cache of indirect buffer allocated by SA before commit the IB. Signed-off-by: Jinzhou Su Reviewed-by: Christian König Signed-off-by: A

[PATCH AUTOSEL 5.12 096/116] drm/amd/display: add handling for hdcp2 rx id list validation

From: "Dingchen (David) Zhang" [ Upstream commit 4ccf9446b2a3615615045346c97f8a1e2a16568a ] [why] the current implementation of hdcp2 rx id list validation does not have handler/checker for invalid message status, e.g. HMAC, the V parameter calculated from PSP not matching the V prime from Rx.

[PATCH AUTOSEL 5.12 077/116] drm/amd/display: Force vsync flip when reconfiguring MPCC

From: Anthony Wang [ Upstream commit 56d63782af9bbd1271bff1422a6a013123eade4d ] [Why] Underflow observed when disabling PIP overlay in-game when vsync is disabled, due to OTC master lock not working with game pipe which is immediate flip. [How] When performing a full update, override flip_immed

[PATCH 6/8] drm/i915/dp: Add support for out-of-bound hotplug events

On some Cherry Trail devices, DisplayPort over Type-C is supported through a USB-PD microcontroller (e.g. a fusb302) + a mux to switch the superspeed datalines between USB-3 and DP (e.g. a pi3usb30532). The kernel in this case does the PD/alt-mode negotiation itself, rather then everything being ha

[PATCH 5/8] drm/i915: Associate ACPI connector nodes with connector entries (v2)

From: Heikki Krogerus On Intel platforms we know that the ACPI connector device node order will follow the order the driver (i915) decides. The decision is made using the custom Intel ACPI OpRegion (intel_opregion.c), though the driver does not actually know that the values it sends to ACPI there

[PATCH 3/8] drm/connector: Add drm_connector_find_by_fwnode() function (v2)

Add a function to find a connector based on a fwnode. This will be used by the new drm_connector_oob_hotplug_event() function which is added by the next patch in this patch-set. Changes in v2: - Complete rewrite to use a global connector list in drm_connector.c rather then using a class-dev-ite

[PATCH 1/8] drm/connector: Give connector sysfs devices there own device_type

Give connector sysfs devices there own device_type, this allows us to check if a device passed to functions dealing with generic devices is a drm_connector or not. A check like this is necessary in the drm_connector_acpi_bus_match() function added in the next patch in this series. Signed-off-by:

[PATCH 7/8] usb: typec: altmodes/displayport: Make dp_altmode_notify() more generic

Make dp_altmode_notify() handle the dp->data.conf == 0 case too, rather then having separate code-paths for this in various places which call it. Signed-off-by: Hans de Goede --- drivers/usb/typec/altmodes/displayport.c | 35 +--- 1 file changed, 13 insertions(+), 22 deletion

[PATCH 8/8] usb: typec: altmodes/displayport: Notify drm subsys of hotplug events

Use the new drm_connector_oob_hotplug_event() functions to let drm/kms drivers know about DisplayPort over Type-C hotplug events. Signed-off-by: Hans de Goede --- Changes in v3: - Only call drm_connector_oob_hotplug_event() on hpd status bit change - Adjust for drm_connector_oob_hotplug_event() n

[PATCH 4/8] drm/connector: Add support for out-of-band hotplug notification (v3)

Add a new drm_connector_oob_hotplug_event() function and oob_hotplug_event drm_connector_funcs member. On some hardware a hotplug event notification may come from outside the display driver / device. An example of this is some USB Type-C setups where the hardware muxes the DisplayPort data and aux

[PATCH 2/8] drm/connector: Add a fwnode pointer to drm_connector and register with ACPI (v2)

Add a fwnode pointer to struct drm_connector and register an acpi_bus_type for the connectors with the ACPI subsystem (when CONFIG_ACPI is enabled). The adding of the fwnode pointer allows drivers to associate a fwnode that represents a connector with that connector. When the new fwnode pointer p

[PATCH 0/8] drm + usb-type-c: Add support for out-of-band hotplug notification (v3)

Hi All, Here is v3 of my patchset making DP over Type-C work on devices where the Type-C controller does not drive the HPD pin on the GPU, but instead we need to forward HPD events from the Type-C controller to the DRM driver. Changes in v3: - Base on top of latest drm-tip, which should fix the C

Re: Enabling sample_c optimization for Broadwell GPUs

Hello, Yes, that bit only exists on Haswell. On Haswell, sample_c operations were processed at 1 pixel/clock unless you set that bit, in which case they get processed at 4 pixels/clock. The downside is that it breaks some obscure media feature that apparently no one used. Broadwell and later al

Re: Enabling sample_c optimization for Broadwell GPUs

Hi Rodrigo, Thank you very much for providing that information in a precise manner. Às 07:16 de 05/05/21, Rodrigo Vivi escreveu: Hi Andre, I'm not familiar with the sample c message optimization. Probably Ken can comment. However I could check the internal spec here and I saw this bit only ex

Re: [PATCH v5 06/27] drm/amdgpu: Handle IOMMU enabled case.

Ping Andrey On 2021-05-04 11:43 a.m., Andrey Grodzovsky wrote: On 2021-05-04 3:03 a.m., Christian König wrote: Am 03.05.21 um 22:43 schrieb Andrey Grodzovsky: On 2021-04-29 3:08 a.m., Christian König wrote: Am 28.04.21 um 17:11 schrieb Andrey Grodzovsky: Handle all DMA IOMMU gropup rela

Re: [PATCH] drm/bridge: fix LONTIUM_LT8912B dependencies

Pushed to drm-misc-next On Wed, 5 May 2021 at 16:28, Robert Foss wrote: > > Hi Adrien, > > Thanks for the quick fix. > > On Wed, 5 May 2021 at 00:02, Adrien Grassein > wrote: > > > > LONTIUM_LT8912B uses "drm_display_mode_to_videomode" from > > DRM framework that needs VIDEOMODE_HELPERS to be e

Re: [PATCH] drm/bridge: fix LONTIUM_LT8912B dependencies

Hi Adrien, Thanks for the quick fix. On Wed, 5 May 2021 at 00:02, Adrien Grassein wrote: > > LONTIUM_LT8912B uses "drm_display_mode_to_videomode" from > DRM framework that needs VIDEOMODE_HELPERS to be enabled. > > Fixes: 30e2ae943c26 ("drm/bridge: Introduce LT8912B DSI to HDMI bridge") > Report

Re: [Intel-gfx] [PATCH] i915: Increase *_latency array size

On Wed, May 05, 2021 at 07:18:30AM -0700, Andi Kleen wrote: > > > Increase all the latency fields to 8 members, which is enough for SKL. > > > > > > I don't know if they are correctly initialized upto 8, but dev_priv > > > should start out as zero, so presumably they will be zero. > > > > Thanks,

Re: [PATCH] i915: Increase *_latency array size

> > Increase all the latency fields to 8 members, which is enough for SKL. > > > > I don't know if they are correctly initialized upto 8, but dev_priv > > should start out as zero, so presumably they will be zero. > > Thanks, the warning should be fixed by commit > > c6deb5e97ded ("drm/i915/pm: M

[PATCH 3/3] Use YCbCr420 as fallback when RGB fails

When encoder validation of a display mode fails, retry with less bandwidth heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups to support 4k60Hz output, which previously failed silently. AMDGPU had nearly the exact same issue. This problem description is therefore copied fro

[PATCH 0/4] drm/i915/display Try YCbCr420 color when RGB fails

When encoder validation of a display mode fails, retry with less bandwidth heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups to support 4k60Hz output, which previously failed silently. AMDGPU had nearly the exact same issue. This problem description is therefore copied fro

[PATCH 1/3] New function to avoid duplicate code in upcomming commits

Moves some checks that later will be performed 2 times to an own fuction. This avoids duplicate code later on. Signed-off-by: Werner Sembach --- PS.: I have no idea why git send-email is messing up this timestamp in "From" below. >From 42a4a3a7d9ea9948b4071f406e7fcae23bfa0bdf Mon Sep 17 00:00:0

[PATCH 2/3] Restructure output format computation for better expandability

Couples the decission between RGB and YCbCr420 mode and the check if the port clock can archive the required frequency. Other checks and configuration steps that where previously done in between can also be done before or after. This allows for are cleaner implementation of retrying different colo

Re: [PATCH v5 06/27] drm/amdgpu: Handle IOMMU enabled case.

On 2021-05-04 1:05 p.m., Felix Kuehling wrote: Am 2021-04-28 um 11:11 a.m. schrieb Andrey Grodzovsky: Handle all DMA IOMMU gropup related dependencies before the group is removed. v5: Drop IOMMU notifier and switch to lockless call to ttm_tt_unpopulate Signed-off-by: Andrey Grodzovsky ---

Re: 16 bpc fixed point (RGBA16) framebuffer support for core and AMD.

On Tue, May 4, 2021 at 9:22 PM Alex Deucher wrote: > > On Wed, Apr 28, 2021 at 5:21 PM Alex Deucher wrote: > > > > On Tue, Apr 20, 2021 at 5:25 PM Alex Deucher wrote: > > > > > > On Fri, Apr 16, 2021 at 12:29 PM Mario Kleiner > > > wrote: > > > > > > > > Friendly ping to the AMD people. Nichola

Re: [PATCH 3/4] Restructure output format computation for better expandability

On Wed, May 05, 2021 at 03:02:53PM +0200, Werner Sembach wrote: > > Am 05.05.21 um 14:15 schrieb Ville Syrjälä: > > On Wed, May 05, 2021 at 11:54:35AM +0200, Werner Sembach wrote: > >> Am 04.05.21 um 11:54 schrieb Ville Syrjälä: > >> > >>> On Mon, May 03, 2021 at 08:21:47PM +0200, Werner Sembach w

Re: [PATCH v5 20/27] drm: Scope all DRM IOCTLs with drm_dev_enter/exit

Ping Andrey On 2021-04-30 1:27 p.m., Andrey Grodzovsky wrote: On 2021-04-30 6:25 a.m., Daniel Vetter wrote: On Thu, Apr 29, 2021 at 04:34:55PM -0400, Andrey Grodzovsky wrote: On 2021-04-29 3:05 p.m., Daniel Vetter wrote: On Thu, Apr 29, 2021 at 12:04:33PM -0400, Andrey Grodzovsky wrote:

Re: [PATCH v5 15/27] drm/scheduler: Fix hang when sched_entity released

Ping Andrey On 2021-04-30 12:10 p.m., Andrey Grodzovsky wrote: On 2021-04-30 2:47 a.m., Christian König wrote: Am 29.04.21 um 19:06 schrieb Andrey Grodzovsky: On 2021-04-29 3:18 a.m., Christian König wrote: I need to take another look at this part when I don't have a massive headache a

Re: [PATCH 4/4] Use YCbCr420 as fallback when RGB fails

Am 04.05.21 um 12:08 schrieb Ville Syrjälä: > On Mon, May 03, 2021 at 08:21:48PM +0200, Werner Sembach wrote: >> When encoder validation of a display mode fails, retry with less bandwidth >> heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups >> to support 4k60Hz output, whi

Re: [PATCH 3/4] Restructure output format computation for better expandability

Am 05.05.21 um 14:15 schrieb Ville Syrjälä: > On Wed, May 05, 2021 at 11:54:35AM +0200, Werner Sembach wrote: >> Am 04.05.21 um 11:54 schrieb Ville Syrjälä: >> >>> On Mon, May 03, 2021 at 08:21:47PM +0200, Werner Sembach wrote: Couples the decission between RGB and YCbCr420 mode and the check

Re: [PATCH 5/9] drm/i915: Associate ACPI connector nodes with connector entries

On Wed, May 5, 2021 at 1:30 PM Hans de Goede wrote: > On 5/5/21 12:02 PM, Andy Shevchenko wrote: ... > But we do really need to document the behavior better here > in the kdoc for fwnode_get_next_child_node() and > device_get_next_child_node(). Totally agree! > of_get_next_child has this bit,

Re: [PATCH v5 01/20] drm/panel: panel-simple: Add missing pm_runtime_disable() calls

On Mon, May 3, 2021 at 10:41 PM Doug Anderson wrote: > > At your convenience and when you think there is too little > > stuff in your sn65dsi86 TODO, check out > > pinctrl-bcm63xx.c for an example of select GPIO_REGMAP > > made very simple (this works fine as long as they are bit > > offsets star

Re: [PATCH V3 2/2] drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 driver

On Wed, May 5, 2021 at 12:03 PM Marek Vasut wrote: > Add driver for TI SN65DSI83 Single-link DSI to Single-link LVDS bridge > and TI SN65DSI84 Single-link DSI to Dual-link or 2x Single-link LVDS > bridge. TI SN65DSI85 is unsupported due to lack of hardware to test on, > but easy to add. > > The d

Re: [PATCH V3 1/2] dt-bindings: drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 bindings

On Wed, May 5, 2021 at 12:03 PM Marek Vasut wrote: > Add DT binding document for TI SN65DSI83 and SN65DSI84 DSI to LVDS bridge. > > Signed-off-by: Marek Vasut > Cc: Douglas Anderson > Cc: Jagan Teki > Cc: Laurent Pinchart > Cc: Linus Walleij > Cc: Rob Herring > Cc: Sam Ravnborg > Cc: Steph

Re: [PATCH 3/4] Restructure output format computation for better expandability

On Wed, May 05, 2021 at 11:54:35AM +0200, Werner Sembach wrote: > Am 04.05.21 um 11:54 schrieb Ville Syrjälä: > > > On Mon, May 03, 2021 at 08:21:47PM +0200, Werner Sembach wrote: > >> Couples the decission between RGB and YCbCr420 mode and the check if the > >> port > >> clock can archive the re

Re: [PATCHv2] drm/omap: Fix issue with clocks left on after resume

* Tony Lindgren [210503 12:18]: > I think we still fix the dispc related issue too, otherwise the parent > child_count will just keep increasing on each suspend. I check that > again though. After tons more debugging, I found the root cause for the parent child_count increasing and posted a patch

Re: [PATCH 8/9] usb: typec: altmodes/displayport: Notify drm subsys of hotplug events

Hi Heikki, On 5/5/21 12:17 PM, Heikki Krogerus wrote: > Hi Hans, > > On Mon, May 03, 2021 at 05:46:46PM +0200, Hans de Goede wrote: >> Use the new drm_connector_find_by_fwnode() and >> drm_connector_oob_hotplug_event() functions to let drm/kms drivers >> know about DisplayPort over Type-C hotplug

Re: [PATCH 4/9] drm/connector: Add support for out-of-band hotplug notification (v2)

Hi, On 5/5/21 11:50 AM, Heikki Krogerus wrote: > On Tue, May 04, 2021 at 05:35:49PM +0200, Hans de Goede wrote: >> Hi, >> >> On 5/4/21 5:10 PM, Heikki Krogerus wrote: +/** + * drm_connector_oob_hotplug_event - Report out-of-band hotplug event to connector + * @connector: conne

Re: [PATCH 5/9] drm/i915: Associate ACPI connector nodes with connector entries

Hi, On 5/5/21 12:02 PM, Andy Shevchenko wrote: > On Wed, May 5, 2021 at 12:28 PM Hans de Goede wrote: >> On 5/5/21 11:17 AM, Andy Shevchenko wrote: >>> On Wed, May 5, 2021 at 12:07 PM Hans de Goede wrote: On 5/4/21 9:52 AM, Andy Shevchenko wrote: > On Monday, May 3, 2021, Hans de Goede

Re: [PATCH 5/9] drm/i915: Associate ACPI connector nodes with connector entries

Hi Andy, Hans, On Wed, May 05, 2021 at 12:17:14PM +0300, Andy Shevchenko wrote: > On Wed, May 5, 2021 at 12:07 PM Hans de Goede wrote: > > On 5/4/21 9:52 AM, Andy Shevchenko wrote: > > > On Monday, May 3, 2021, Hans de Goede > > > wrote: > > ... > > > > +

Re: [PATCH 8/9] usb: typec: altmodes/displayport: Notify drm subsys of hotplug events

Hi Hans, On Mon, May 03, 2021 at 05:46:46PM +0200, Hans de Goede wrote: > Use the new drm_connector_find_by_fwnode() and > drm_connector_oob_hotplug_event() functions to let drm/kms drivers > know about DisplayPort over Type-C hotplug events. > > Signed-off-by: Hans de Goede > --- > Changes in v

Re: [PATCH] drm/i915: drop the __i915_active_call pointer packing

On Tue, May 04, 2021 at 05:41:36PM +0100, Matthew Auld wrote: > We use some of the lower bits of the retire function pointer for > potential flags, which is quite thorny, since the caller needs to > remember to give the function the correct alignment with > __i915_active_call, otherwise we might in

Re: Enabling sample_c optimization for Broadwell GPUs

Hi Andre, I'm not familiar with the sample c message optimization. Probably Ken can comment. However I could check the internal spec here and I saw this bit only exists with this meaning in Haswell. For all the other platforms, including Broadwell it got re-purposed with a different meaning and

Re: [PATCH 5/6] drm/vmwgfx: Add basic support for SVGA3

Hi Zack, I love your patch! Perhaps something to improve: [auto build test WARNING on drm-tip/drm-tip] [also build test WARNING on linus/master next-20210505] [cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next drm/drm-next v5.12] [If your patch is

[PATCH] drm/vmwgfx: fix badzero.cocci warnings

: kernel test robot --- url: https://github.com/0day-ci/linux/commits/Zack-Rusin/drm-vmwgfx-SVGA-v3-and-arm64-support/20210505-120026 base: git://anongit.freedesktop.org/drm/drm-tip drm-tip vmwgfx_cmd.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/gpu/drm/vmwgfx

Re: [Intel-gfx] [PATCH 16/27] drm/i915/gem: Add an intermediate proto_context struct

On 03/05/2021 16:57, Jason Ekstrand wrote: The current context uAPI allows for two methods of setting context parameters: SET_CONTEXT_PARAM and CONTEXT_CREATE_EXT_SETPARAM. The former is allowed to be called at any time while the later happens as part of GEM_CONTEXT_CREATE. Currently, everyth

Re: [Intel-gfx] [PATCH 27/27] drm/i915/gem: Roll all of context creation together

On Mon, May 03, 2021 at 10:57:48AM -0500, Jason Ekstrand wrote: > Now that we have the whole engine set and VM at context creation time, > we can just assign those fields instead of creating first and handling > the VM and engines later. This lets us avoid creating useless VMs and > engine sets an

[PATCH V3 2/2] drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 driver

Add driver for TI SN65DSI83 Single-link DSI to Single-link LVDS bridge and TI SN65DSI84 Single-link DSI to Dual-link or 2x Single-link LVDS bridge. TI SN65DSI85 is unsupported due to lack of hardware to test on, but easy to add. The driver operates the chip via I2C bus. Currently the LVDS clock ar

[PATCH V3 1/2] dt-bindings: drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 bindings

Add DT binding document for TI SN65DSI83 and SN65DSI84 DSI to LVDS bridge. Signed-off-by: Marek Vasut Cc: Douglas Anderson Cc: Jagan Teki Cc: Laurent Pinchart Cc: Linus Walleij Cc: Rob Herring Cc: Sam Ravnborg Cc: Stephen Boyd Cc: devicet...@vger.kernel.org To: dri-devel@lists.freedesktop.

Re: [PATCH 5/9] drm/i915: Associate ACPI connector nodes with connector entries

On Wed, May 5, 2021 at 12:28 PM Hans de Goede wrote: > On 5/5/21 11:17 AM, Andy Shevchenko wrote: > > On Wed, May 5, 2021 at 12:07 PM Hans de Goede wrote: > >> On 5/4/21 9:52 AM, Andy Shevchenko wrote: > >>> On Monday, May 3, 2021, Hans de Goede >>> > wrote: > > > > .

  1   2   >