dri-devel June 2020

dri-devel@lists.freedesktop.org

315 participants
731 discussions

amdgpu freezes kernel after kernel 5.7.6 changes
by roland.rucky＠gmail.com 28 Jun '20

28 Jun '20

Not sure if I am contacting the correct person, Since I updated to kernel 5.7.6, my system started to freeze randomly. After a couple of freezes, I noticed, that they always happen when playing games, or during videoplayback in e.g. firefox. I reverted to the previous kernel 5.7.5, and all issues are gone. Next I started to revert and test single commits between the two kernel versions, which affect amdgpu. If I revert the changes listed below, the kernel does not freeze any more. Sadly I can`t get any crash reports / logs. Even the magic sysrq key does not work, when the system is frozen. I will also attach a patch, which includes all reverted commits. List of changes I reverted: ----------------------------------------------------------------------- commit 6674508ba1a2ea6caca5de2bcb25bc00a050fd0a Author: Harry Wentland <harry.wentland(a)amd.com> Date: Thu May 28 09:44:44 2020 -0400 Revert "drm/amd/display: disable dcn20 abm feature for bring up" commit 14ed1c908a7a623cc0cbf0203f8201d1b7d31d16 upstream. This reverts commit 96cb7cf13d8530099c256c053648ad576588c387. This change was used for DCN2 bringup and is no longer desired. In fact it breaks backlight on DCN2 systems. Cc: Alexander Monakov <amonakov(a)ispras.ru> Cc: Hersen Wu <hersenxs.wu(a)amd.com> Cc: Anthony Koo <Anthony.Koo(a)amd.com> Cc: Michael Chiu <Michael.Chiu(a)amd.com> Signed-off-by: Harry Wentland <harry.wentland(a)amd.com> Acked-by: Alex Deucher <alexander.deucher(a)amd.com> Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas(a)amd.com> Reported-and-tested-by: Alexander Monakov <amonakov(a)ispras.ru> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Cc: stable(a)vger.kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c index 7fc15b82fe48..f9f02e08054b 100644 --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c @@ -1334,7 +1334,7 @@ static int dm_late_init(void *handle) unsigned int linear_lut[16]; int i; struct dmcu *dmcu = adev->dm.dc->res_pool->dmcu; - bool ret = false; + bool ret; for (i = 0; i < 16; i++) linear_lut[i] = 0xFFFF * i / 15; @@ -1350,13 +1350,10 @@ static int dm_late_init(void *handle) */ params.min_abm_backlight = 0x28F; - /* todo will enable for navi10 */ - if (adev->asic_type <= CHIP_RAVEN) { - ret = dmcu_load_iram(dmcu, params); + ret = dmcu_load_iram(dmcu, params); - if (!ret) - return -EINVAL; - } + if (!ret) + return -EINVAL; return detect_mst_link_for_all_connectors(adev->ddev); } commit fba8f9ef7e1405ee6f422beb874791e8a5eb489c Author: Alex Deucher <alexander.deucher(a)amd.com> Date: Tue Jun 2 17:22:48 2020 -0400 drm/amdgpu/display: use blanked rather than plane state for sync groups commit b7f839d292948142eaab77cedd031aad0bfec872 upstream. We may end up with no planes set yet, depending on the ordering, but we should have the proper blanking state which is either handled by either DPG or TG depending on the hardware generation. Check both to determine the proper blanked state. Bug: https://gitlab.freedesktop.org/drm/amd/issues/781 Fixes: 5fc0cbfad45648 ("drm/amd/display: determine if a pipe is synced by plane state") Cc: nicholas.kazlauskas(a)amd.com Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Cc: stable(a)vger.kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc.c b/drivers/gpu/drm/amd/display/dc/core/dc.c index 4a619328101c..4acaf4be8a81 100644 --- a/drivers/gpu/drm/amd/display/dc/core/dc.c +++ b/drivers/gpu/drm/amd/display/dc/core/dc.c @@ -1011,9 +1011,17 @@ static void program_timing_sync( } } - /* set first pipe with plane as master */ + /* set first unblanked pipe as master */ for (j = 0; j < group_size; j++) { - if (pipe_set[j]->plane_state) { + bool is_blanked; + + if (pipe_set[j]->stream_res.opp->funcs- >dpg_is_blanked) + is_blanked = + pipe_set[j]->stream_res.opp- >funcs->dpg_is_blanked(pipe_set[j]->stream_res.opp); + else + is_blanked = + pipe_set[j]->stream_res.tg- >funcs->is_blanked(pipe_set[j]->stream_res.tg); + if (!is_blanked) { if (j == 0) break; @@ -1034,9 +1042,17 @@ static void program_timing_sync( status->timing_sync_info.master = false; } - /* remove any other pipes with plane as they have already been synced */ + /* remove any other unblanked pipes as they have already been synced */ for (j = j + 1; j < group_size; j++) { - if (pipe_set[j]->plane_state) { + bool is_blanked; + + if (pipe_set[j]->stream_res.opp->funcs- >dpg_is_blanked) + is_blanked = + pipe_set[j]->stream_res.opp- >funcs->dpg_is_blanked(pipe_set[j]->stream_res.opp); + else + is_blanked = + pipe_set[j]->stream_res.tg- >funcs->is_blanked(pipe_set[j]->stream_res.tg); + if (!is_blanked) { group_size--; pipe_set[j] = pipe_set[group_size]; j--; commit b5232e2ee8df85891514c73472cac09921e5d51d Author: Nicholas Kazlauskas <nicholas.kazlauskas(a)amd.com> Date: Tue Jun 2 20:42:33 2020 -0400 drm/amd/display: Revalidate bandwidth before commiting DC updates [ Upstream commit a24eaa5c51255b344d5a321f1eeb3205f2775498 ] [Why] Whenever we switch between tiled formats without also switching pixel formats or doing anything else that recreates the DC plane state we can run into underflow or hangs since we're not updating the DML parameters before committing to the hardware. [How] If the update type is FULL then call validate_bandwidth again to update the DML parmeters before committing the state. This is basically just a workaround and protective measure against update types being added DC where we could run into this issue in the future. We can only fully validate the state in advance before applying it to the hardware if we recreate all the plane and stream states since we can't modify what's currently in use. The next step is to update DM to ensure that we're creating the plane and stream states for whatever could potentially be a full update in DC to pre-emptively recreate the state for DC global validation. The workaround can stay until this has been fixed in DM. Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas(a)amd.com> Reviewed-by: Hersen Wu <hersenxs.wu(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Signed-off-by: Sasha Levin <sashal(a)kernel.org> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc.c b/drivers/gpu/drm/amd/display/dc/core/dc.c index 47431ca6986d..4a619328101c 100644 --- a/drivers/gpu/drm/amd/display/dc/core/dc.c +++ b/drivers/gpu/drm/amd/display/dc/core/dc.c @@ -2517,6 +2517,12 @@ void dc_commit_updates_for_stream(struct dc *dc, copy_stream_update_to_stream(dc, context, stream, stream_update); + if (!dc->res_pool->funcs->validate_bandwidth(dc, context, false)) { + DC_ERROR("Mode validation failed for stream update!\n"); + dc_release_state(context); + return; + } + commit_planes_for_stream( dc, srf_updates, Details: * Kernel: 5.7.6 * GPU: radeon 5700XT * CPU: ryzen 3800X * running on swaywm(wayland)

1 1

[PATCH v1 0/2] Improve descriptions of a few simple-panels
by Dmitry Osipenko 28 Jun '20

28 Jun '20

Hello, This is a follow up to [1], which was already applied to drm-misc and then Laurent Pinchart spotted some problems. This series addresses those problems. [1] https://patchwork.ozlabs.org/project/linux-tegra/patch/20200617222703.17080… Dmitry Osipenko (2): drm/panel-simple: Correct EDT ET057090DHU connector type drm/panel-simple: Add missing BUS descriptions for some panels drivers/gpu/drm/panel/panel-simple.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) -- 2.26.0

3 11

[PATCH v3 0/7] Convert the remaining text files to ReST
by Mauro Carvalho Chehab 28 Jun '20

28 Jun '20

The main goal of this series is to finish the ReST conversion. After this series, we have just those files still in plain old format: - Documentation/RCU/RTFP.txt - Documentation/atomic_bitops.txt - Documentation/memory-barriers.txt - Documentation/atomic_t.txt - Documentation/filesystems/dax.txt - Documentation/filesystems/path-lookup.txt - Documentation/virt/kvm/devices/README PS.: I'm using a script to remove false-positives and ignore non-converted translated files. --- - v3: removed SPDX patches, because upstream discussion about GFDL is not finished yet. So, for now, use the old way to specify dual-licensed GPL and GFDL files. I have already a tree ready for submission once upstream pushes this feat on SPDX specs. Mauro Carvalho Chehab (7): docs: dt: convert booting-without-of.txt to ReST format docs: trace: ring-buffer-design.txt: convert to ReST format docs: move nommu-mmap.txt to admin-guide and rename to ReST docs: move mailbox.txt to driver-api and rename it docs: move other kAPI documents to core-api docs: Add remaining Documentation/*.txt at staging/index.rst docs: staging: use small font for literal includes Documentation/admin-guide/mm/index.rst | 1 + .../mm/nommu-mmap.rst} | 0 Documentation/admin-guide/sysctl/vm.rst | 2 +- Documentation/arm/booting.rst | 2 +- .../bus-virt-phys-mapping.rst} | 0 Documentation/core-api/index.rst | 3 + .../this_cpu_ops.rst} | 0 .../unaligned-memory-access.rst | 0 ...-without-of.txt => booting-without-of.rst} | 298 ++++--- Documentation/devicetree/index.rst | 1 + Documentation/driver-api/index.rst | 1 + .../{mailbox.txt => driver-api/mailbox.rst} | 0 Documentation/gpu/drm-mm.rst | 2 +- Documentation/staging/index.rst | 24 + Documentation/trace/index.rst | 1 + ...ffer-design.txt => ring-buffer-design.rst} | 802 ++++++++++-------- Documentation/translations/zh_CN/arm/Booting | 2 +- arch/Kconfig | 2 +- init/Kconfig | 2 +- mm/Kconfig | 2 +- mm/nommu.c | 2 +- 21 files changed, 631 insertions(+), 516 deletions(-) rename Documentation/{nommu-mmap.txt => admin-guide/mm/nommu-mmap.rst} (100%) rename Documentation/{bus-virt-phys-mapping.txt => core-api/bus-virt-phys-mapping.rst} (100%) rename Documentation/{this_cpu_ops.txt => core-api/this_cpu_ops.rst} (100%) rename Documentation/{process => core-api}/unaligned-memory-access.rst (100%) rename Documentation/devicetree/{booting-without-of.txt => booting-without-of.rst} (90%) rename Documentation/{mailbox.txt => driver-api/mailbox.rst} (100%) rename Documentation/trace/{ring-buffer-design.txt => ring-buffer-design.rst} (55%) -- 2.26.2

2 3

[PATCH 00/27] Converter R-Car DU to the DRM bridge connector helper
by Laurent Pinchart 28 Jun '20

28 Jun '20

Hello, This patch series converts the R-Car DU driver to use the DRM bridge connector helper drm_bridge_connector_init(). The bulk of the series is conversion of the adv7511, simple-bridge, rcar-lbds and dw-hdmi drivers to make connector creation optional (through the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag). The series starts with the adv7511 driver, previously posted as "[PATCH 0/4] drm: bridge: adv7511: Enable usage with DRM bridge connector helper" ([1]). Patches 01/27 to 04/27 incorporate all the received review comments. The next three patches address the simple-bridge driver, previously posted as "[PATCH 0/2] drm: bridge: simple-bridge: Enable usage with DRM bridge connector helper". Patch 05/27 is an additional fix that stems from the review, and patches 06/27 and 07/27 incorporate all the received review comments. Patch 08/27 is a new patch that addresses the rcar-lvds driver. Instead of implementing direct support for DRM_BRIDGE_ATTACH_NO_CONNECTOR, it simply removes code that shouldn't have been in the driver in the first place by switching to the panel bridge helper. Patches 09/27 to 22/27 then address the dw-hdmi driver. That's a more sizeable rework, due to the fact that the driver implements a mid-layer for platform-specific glue, with the internal drm_connector being used throughout the whole code. There's no rocket science there, but patch 10/27 should be noted for adding a new argument to the drm_bridge_funcs.mode_valid() function. Please see individual patches for details. Patch 23/27 adds support to the dw-hdmi driver to attach to a downstream bridge if one is specified in DT. As the DT port number corresponding to the video output differs between platforms that integrate the dw-hdmi (some of them even don't have a video output port, which should probably be fixed, but that's out of scope for this series), the port number has to be specified by the platform glue layer. Patch 24/27 does so for the R-Car dw-hdmi driver. Patch 25/27 is a drive-by fix for an error path issue in the rcar-du driver. Patch 26/27 finally makes use of the drm_bridge_connector_init() helper. Unfortunately, this breaks the VGA output on R-Car Gen3 platforms. On those platforms, the VGA DDC lines are not connected, and there is no mean for software to detect the VGA output connection status. When the simple-bridge driver creates a connector, it automatically adds default modes when no DDC is available. This behavious is also present int the DRM probe helper drm_helper_probe_single_connector_modes(), but only when the connector status is connector_status_connected. As the driver (rightfully) reports connector_status_unconnected, no modes are added. Patch 27/27 fixes this issue by extending addition of default modes in drm_helper_probe_single_connector_modes() when the output status is unknown. An alternative approach would be to implement this behaviour in the bridge connector helper (drm_bridge_connector.c). All the modified drivers have been compile-tested, and the series has been tested on a Renesas R-Car Salvator-XS board with the VGA, HDMI and LVDS outputs. [1] https://lore.kernel.org/dri-devel/20200409004610.12346-1-laurent.pinchart+r… [2] https://lore.kernel.org/dri-devel/20200409003636.11792-1-laurent.pinchart+r… Laurent Pinchart (27): drm: bridge: adv7511: Split EDID read to a separate function drm: bridge: adv7511: Split connector creation to a separate function drm: bridge: adv7511: Implement bridge connector operations drm: bridge: adv7511: Make connector creation optional drm: bridge: Return NULL on error from drm_bridge_get_edid() drm: bridge: simple-bridge: Delegate operations to next bridge drm: bridge: simple-bridge: Make connector creation optional drm: rcar-du: lvds: Convert to DRM panel bridge helper drm: edid: Constify connector argument to infoframe functions drm: bridge: Pass drm_display_info to drm_bridge_funcs .mode_valid() drm: bridge: dw-hdmi: Pass private data pointer to .mode_valid() drm: bridge: dw-hdmi: Pass private data pointer to .configure_phy() drm: bridge: dw-hdmi: Remove unused field from dw_hdmi_plat_data drm: meson: dw-hdmi: Use dw_hdmi context to replace hack drm: bridge: dw-hdmi: Pass drm_display_info to .mode_valid() drm: bridge: dw-hdmi: Constify mode argument to dw_hdmi_phy_ops .init() drm: bridge: dw-hdmi: Constify mode argument to internal functions drm: bridge: dw-hdmi: Pass drm_display_info to dw_hdmi_support_scdc() drm: bridge: dw-hdmi: Split connector creation to a separate function drm: bridge: dw-hdmi: Store current connector in struct dw_hdmi drm: bridge: dw-hdmi: Pass drm_connector to internal functions as needed drm: bridge: dw-hdmi: Make connector creation optional drm: bridge: dw-hdmi: Attach to next bridge if available drm: rcar-du: dw-hdmi: Set output port number drm: rcar-du: Fix error handling in rcar_du_encoder_init() drm: rcar-du: Use drm_bridge_connector_init() helper drm: Add default modes for connectors in unknown state drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 159 +++++--- .../drm/bridge/analogix/analogix-anx6345.c | 1 + .../drm/bridge/analogix/analogix-anx78xx.c | 1 + drivers/gpu/drm/bridge/cdns-dsi.c | 1 + drivers/gpu/drm/bridge/chrontel-ch7033.c | 1 + drivers/gpu/drm/bridge/nwl-dsi.c | 1 + drivers/gpu/drm/bridge/sii9234.c | 1 + drivers/gpu/drm/bridge/sil-sii8620.c | 1 + drivers/gpu/drm/bridge/simple-bridge.c | 113 +++--- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 357 ++++++++++++------ drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 1 + drivers/gpu/drm/bridge/tc358767.c | 1 + drivers/gpu/drm/bridge/tc358768.c | 1 + drivers/gpu/drm/bridge/thc63lvd1024.c | 1 + drivers/gpu/drm/bridge/ti-tfp410.c | 11 +- drivers/gpu/drm/drm_atomic_helper.c | 3 +- drivers/gpu/drm/drm_bridge.c | 10 +- drivers/gpu/drm/drm_edid.c | 12 +- drivers/gpu/drm/drm_probe_helper.c | 7 +- drivers/gpu/drm/i2c/tda998x_drv.c | 1 + drivers/gpu/drm/imx/dw_hdmi-imx.c | 6 +- drivers/gpu/drm/meson/meson_dw_hdmi.c | 34 +- drivers/gpu/drm/omapdrm/dss/dpi.c | 1 + drivers/gpu/drm/omapdrm/dss/sdi.c | 1 + drivers/gpu/drm/omapdrm/dss/venc.c | 1 + drivers/gpu/drm/rcar-du/rcar_du_encoder.c | 26 +- drivers/gpu/drm/rcar-du/rcar_dw_hdmi.c | 7 +- drivers/gpu/drm/rcar-du/rcar_lvds.c | 124 +----- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 6 +- drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c | 6 +- drivers/gpu/drm/sun4i/sun8i_dw_hdmi.h | 3 +- drivers/gpu/drm/sun4i/sun8i_hdmi_phy.c | 3 +- include/drm/bridge/dw_hdmi.h | 28 +- include/drm/drm_bridge.h | 3 + include/drm/drm_edid.h | 6 +- include/drm/drm_modeset_helper_vtables.h | 8 +- 36 files changed, 541 insertions(+), 406 deletions(-) -- Regards, Laurent Pinchart

12 68

[PATCH v2 0/2] virtio: modernize DMA quirks
by Michael S. Tsirkin 28 Jun '20

28 Jun '20

Use generic names for the quirks to make it clear it is not just about the IOMMU, it's about DMA access in general. changes from v1: added patch 2 Michael S. Tsirkin (2): virtio: VIRTIO_F_IOMMU_PLATFORM -> VIRTIO_F_ACCESS_PLATFORM virtio: virtio_has_iommu_quirk -> virtio_has_dma_quirk arch/um/drivers/virtio_uml.c | 2 +- drivers/gpu/drm/virtio/virtgpu_object.c | 2 +- drivers/gpu/drm/virtio/virtgpu_vq.c | 4 ++-- drivers/vdpa/ifcvf/ifcvf_base.h | 2 +- drivers/vdpa/vdpa_sim/vdpa_sim.c | 4 ++-- drivers/vhost/net.c | 4 ++-- drivers/vhost/vdpa.c | 2 +- drivers/virtio/virtio_balloon.c | 2 +- drivers/virtio/virtio_ring.c | 4 ++-- include/linux/virtio_config.h | 6 +++--- include/uapi/linux/virtio_config.h | 10 +++++++--- tools/virtio/linux/virtio_config.h | 6 +++--- 12 files changed, 26 insertions(+), 22 deletions(-) -- MST

2 2

Re: [PATCH] fbtft-bus.c: Removing that prohibited space before ')'
by kernel test robot 27 Jun '20

27 Jun '20

1 0

[PATCH] drm: gma500: Drop surplus include
by Linus Walleij 27 Jun '20

27 Jun '20

This file includes <linux/gpio.h> but does not use any symbols from it, drop the include. Cc: Patrik Jakobsson <patrik.r.jakobsson(a)gmail.com> Signed-off-by: Linus Walleij <linus.walleij(a)linaro.org> --- drivers/gpu/drm/gma500/psb_intel_drv.h | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/gma500/psb_intel_drv.h b/drivers/gpu/drm/gma500/psb_intel_drv.h index fb601983cef0..9221d1f545b0 100644 --- a/drivers/gpu/drm/gma500/psb_intel_drv.h +++ b/drivers/gpu/drm/gma500/psb_intel_drv.h @@ -13,7 +13,6 @@ #include <drm/drm_encoder.h> #include <drm/drm_probe_helper.h> #include <drm/drm_vblank.h> -#include <linux/gpio.h> #include "gma_display.h" /* -- 2.25.4

3 3

[RFC v8 0/9] drm/nouveau: Introduce CRC support for gf119+
by Lyude Paul 27 Jun '20

27 Jun '20

Nvidia released some documentation on how CRC support works on their GPUs, hooray! So: this patch series implements said CRC support in nouveau, along with adding some special debugfs interfaces for some relevant igt-gpu-tools tests (already on the ML). First - we add some new functionality to kthread_work in the kernel, and then use this to add a new feature to DRM that Ville Syrjälä came up with: vblank workers. Basically, this is just a generic DRM interface that allows for scheduling high-priority workers that start on a given vblank interrupt. Note that while we're currently only using this in nouveau, Intel has plans to use this for i915 as well (hence why they came up with it!). And finally: in order to implement the last feature, we expose some new functions in the kernel's kthread_worker infrastructure so that we can de-complicate our implementation of this. Anyway-welcome to the future! :) Major changes since v7: * Drop /harm/armh/ patch * Address danvet's comments * Drop "drm/nouveau/kms/nv50-: Unroll error cleanup in nv50_head_create()" Major changes since v6: * Move vblank_work related functions into their own files * Write documentation * Simplify work flushing and cancellation by getting rid of seqcounts and ->pending Major changes since v4: * Remove the interfaces we tried adding to kthread_worker and use a wait queue + seqcount in order to implement flushing vblank workers. * Rebase Major changes since v3: * Style fixes on nouveau patches from checkpatch, no functional changes * Don't integrate so tightly with kthread_work (and use our own lock), instead introduce some new functions for doing simple async flushing and cancelling. I think this interface looks a lot more acceptable then what I was previously trying. * Apply some changes requested by danvet Major changes since v2: * Use kthread_worker instead of kthreadd for vblank workers * Don't check debugfs return values Lyude Paul (9): drm/vblank: Register drmm cleanup action once per drm_vblank_crtc drm/vblank: Use spin_(un)lock_irq() in drm_crtc_vblank_off() drm/vblank: Add vblank works drm/nouveau/kms/nv140-: Don't modify depth in state during atomic commit drm/nouveau/kms/nv50-: Fix disabling dithering drm/nouveau/kms/nv140-: Track wndw mappings in nv50_head_atom drm/nouveau/kms/nv50-: Expose nv50_outp_atom in disp.h drm/nouveau/kms/nv50-: Move hard-coded object handles into header drm/nouveau/kms/nvd9-: Add CRC support Documentation/gpu/drm-kms.rst | 15 + drivers/gpu/drm/Makefile | 2 +- drivers/gpu/drm/drm_internal.h | 27 + drivers/gpu/drm/drm_vblank.c | 72 +- drivers/gpu/drm/drm_vblank_work.c | 267 ++++++++ drivers/gpu/drm/nouveau/dispnv04/crtc.c | 25 +- drivers/gpu/drm/nouveau/dispnv50/Kbuild | 4 + drivers/gpu/drm/nouveau/dispnv50/atom.h | 21 + drivers/gpu/drm/nouveau/dispnv50/core.h | 4 + drivers/gpu/drm/nouveau/dispnv50/core907d.c | 3 + drivers/gpu/drm/nouveau/dispnv50/core917d.c | 3 + drivers/gpu/drm/nouveau/dispnv50/corec37d.c | 3 + drivers/gpu/drm/nouveau/dispnv50/corec57d.c | 3 + drivers/gpu/drm/nouveau/dispnv50/crc.c | 714 ++++++++++++++++++++ drivers/gpu/drm/nouveau/dispnv50/crc.h | 125 ++++ drivers/gpu/drm/nouveau/dispnv50/crc907d.c | 139 ++++ drivers/gpu/drm/nouveau/dispnv50/crcc37d.c | 153 +++++ drivers/gpu/drm/nouveau/dispnv50/disp.c | 58 +- drivers/gpu/drm/nouveau/dispnv50/disp.h | 24 + drivers/gpu/drm/nouveau/dispnv50/handles.h | 16 + drivers/gpu/drm/nouveau/dispnv50/head.c | 98 ++- drivers/gpu/drm/nouveau/dispnv50/head.h | 12 +- drivers/gpu/drm/nouveau/dispnv50/head907d.c | 14 +- drivers/gpu/drm/nouveau/dispnv50/headc37d.c | 27 +- drivers/gpu/drm/nouveau/dispnv50/headc57d.c | 20 +- drivers/gpu/drm/nouveau/dispnv50/wndw.c | 3 +- drivers/gpu/drm/nouveau/nouveau_display.c | 60 +- include/drm/drm_vblank.h | 20 + include/drm/drm_vblank_work.h | 71 ++ 29 files changed, 1861 insertions(+), 142 deletions(-) create mode 100644 drivers/gpu/drm/drm_vblank_work.c create mode 100644 drivers/gpu/drm/nouveau/dispnv50/crc.c create mode 100644 drivers/gpu/drm/nouveau/dispnv50/crc.h create mode 100644 drivers/gpu/drm/nouveau/dispnv50/crc907d.c create mode 100644 drivers/gpu/drm/nouveau/dispnv50/crcc37d.c create mode 100644 drivers/gpu/drm/nouveau/dispnv50/handles.h create mode 100644 include/drm/drm_vblank_work.h -- 2.26.2

1 9

[Bug 207673] New: radeon: crash due to over temperature
by bugzilla-daemon＠bugzilla.kernel.org 27 Jun '20

27 Jun '20

https://bugzilla.kernel.org/show_bug.cgi?id=207673 Bug ID: 207673 Summary: radeon: crash due to over temperature Product: Drivers Version: 2.5 Kernel Version: 5.6.x and previous Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: phil(a)jpmr.org Regression: No Created attachment 289045 --> https://bugzilla.kernel.org/attachment.cgi?id=289045&action=edit kernel log + lspci + glxinfo + patch The radeon driver crashes because of an over temperature of my AMD Cape Verde Pro graphic card. On my system, there's no overclocking, and the power management mode is the default one, with power_method dpm, power_dpm_state balanced and power_dpm_force_performance_level auto. This GPU is used for display and opencl computing. The default over temperature value in r600_dpm is 120C, which seems to be too high for this chip/card. I patched my system to have a 100C limit, and I've no crash anymore. (I tried 110C, and it's still too high). Attached are the full kernel log of the crash event, the lspci and glxinfo for the graphic card, and the proposed patch. -- You are receiving this mail because: You are watching the assignee of the bug.

1 7

Re: [PATCH] fbtft-bus.c:
by kernel test robot 27 Jun '20

27 Jun '20

Hi K, Thank you for the patch! Yet something to improve: [auto build test ERROR on staging/staging-testing] [also build test ERROR on v5.8-rc2 next-20200626] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/B-K-Karthik/fbtft-bus-c/20200627-1… base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git 92cd1b5d65f5c67147c7da39a3c2ad7e6ff81027 config: i386-randconfig-a005-20200624 (attached as .config) compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0 reproduce (this is a W=1 build): # save the attached .config to linux build tree make W=1 ARCH=i386 If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp(a)intel.com> All error/warnings (new ones prefixed by >>): drivers/staging/fbtft/fbtft-bus.c:65:53: error: macro "define_fbtft_write_reg" requires 4 arguments, but only 3 given define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8) ^ >> drivers/staging/fbtft/fbtft-bus.c:15:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' void func(struct fbtft_par *par, int len, ...) \ ^ >> drivers/staging/fbtft/fbtft-bus.c:66:1: note: in expansion of macro 'define_fbtft_write_reg' define_fbtft_write_reg(fbtft_write_reg16_bus8, __be16, u16, cpu_to_be16) ^~~~~~~~~~~~~~~~~~~~~~ drivers/staging/fbtft/fbtft-bus.c:67:57: error: macro "define_fbtft_write_reg" requires 4 arguments, but only 3 given define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, u16) ^ drivers/staging/fbtft/fbtft-bus.c:69:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' void fbtft_write_reg8_bus9(struct fbtft_par *par, int len, ...) ^~~~ vim +15 drivers/staging/fbtft/fbtft-bus.c c296d5f9957c03 Thomas Petazzoni 2014-12-31 7 c296d5f9957c03 Thomas Petazzoni 2014-12-31 8 /***************************************************************************** c296d5f9957c03 Thomas Petazzoni 2014-12-31 9 * c296d5f9957c03 Thomas Petazzoni 2014-12-31 10 * void (*write_reg)(struct fbtft_par *par, int len, ...); c296d5f9957c03 Thomas Petazzoni 2014-12-31 11 * c296d5f9957c03 Thomas Petazzoni 2014-12-31 12 *****************************************************************************/ c296d5f9957c03 Thomas Petazzoni 2014-12-31 13 8d8825b420ffb3 Alfonso Lima Astor 2017-10-17 14 #define define_fbtft_write_reg(func, buffer_type, data_type, modifier) \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 @15 void func(struct fbtft_par *par, int len, ...) \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 16 { \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 17 va_list args; \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 18 int i, ret; \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 19 int offset = 0; \ 8d8825b420ffb3 Alfonso Lima Astor 2017-10-17 20 buffer_type *buf = (buffer_type *)par->buf; \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 21 \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 22 if (unlikely(par->debug & DEBUG_WRITE_REGISTER)) { \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 23 va_start(args, len); \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 24 for (i = 0; i < len; i++) { \ cc1c0eea8527bd Renato Soma 2018-04-17 25 buf[i] = modifier((data_type)va_arg(args, \ cc1c0eea8527bd Renato Soma 2018-04-17 26 unsigned int)); \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 27 } \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 28 va_end(args); \ cc1c0eea8527bd Renato Soma 2018-04-17 29 fbtft_par_dbg_hex(DEBUG_WRITE_REGISTER, par, \ cc1c0eea8527bd Renato Soma 2018-04-17 30 par->info->device, buffer_type, buf, len, \ cc1c0eea8527bd Renato Soma 2018-04-17 31 "%s: ", __func__); \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 32 } \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 33 \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 34 va_start(args, len); \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 35 \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 36 if (par->startbyte) { \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 37 *(u8 *)par->buf = par->startbyte; \ 8d8825b420ffb3 Alfonso Lima Astor 2017-10-17 38 buf = (buffer_type *)(par->buf + 1); \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 39 offset = 1; \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 40 } \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 41 \ 8d8825b420ffb3 Alfonso Lima Astor 2017-10-17 42 *buf = modifier((data_type)va_arg(args, unsigned int)); \ cc1c0eea8527bd Renato Soma 2018-04-17 43 ret = fbtft_write_buf_dc(par, par->buf, sizeof(data_type) + offset, \ cc1c0eea8527bd Renato Soma 2018-04-17 44 0); \ e70065fdc11d86 Heiner Kallweit 2017-03-02 45 if (ret < 0) \ e70065fdc11d86 Heiner Kallweit 2017-03-02 46 goto out; \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 47 len--; \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 48 \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 49 if (par->startbyte) \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 50 *(u8 *)par->buf = par->startbyte | 0x2; \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 51 \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 52 if (len) { \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 53 i = len; \ e70065fdc11d86 Heiner Kallweit 2017-03-02 54 while (i--) \ cc1c0eea8527bd Renato Soma 2018-04-17 55 *buf++ = modifier((data_type)va_arg(args, \ cc1c0eea8527bd Renato Soma 2018-04-17 56 unsigned int)); \ e70065fdc11d86 Heiner Kallweit 2017-03-02 57 fbtft_write_buf_dc(par, par->buf, \ 8d8825b420ffb3 Alfonso Lima Astor 2017-10-17 58 len * (sizeof(data_type) + offset), 1); \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 59 } \ e70065fdc11d86 Heiner Kallweit 2017-03-02 60 out: \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 61 va_end(args); \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 62 } \ c296d5f9957c03 Thomas Petazzoni 2014-12-31 63 EXPORT_SYMBOL(func); c296d5f9957c03 Thomas Petazzoni 2014-12-31 64 31b9aef1a7ba07 B K Karthik 2020-06-27 @65 define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8) 8d8825b420ffb3 Alfonso Lima Astor 2017-10-17 @66 define_fbtft_write_reg(fbtft_write_reg16_bus8, __be16, u16, cpu_to_be16) 31b9aef1a7ba07 B K Karthik 2020-06-27 67 define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, u16) c296d5f9957c03 Thomas Petazzoni 2014-12-31 68 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

1 0

← Newer
1
...
26
27
28
29
30
31
32
...
74
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2020