dri-devel June 2019

dri-devel@lists.freedesktop.org

350 participants
2370 discussions

[PATCH 0/2] drm/panel-simple: Add panel parameters for ortustech-com37h3m05dtc/99dtc and sharp-lq070y3dg3b
by H. Nikolaus Schaller 04 Jun '19

04 Jun '19

Since v5.2-rc1 OMAP is no longer using a special display driver architecture for DPI panels, but uses the general drm/panel/panel-simple. So we finally can add SoC independent panel definitions for two panel models which we already had worked on quite a while ago (before device tree was introduced): https://patchwork.kernel.org/patch/2851295/ H. Nikolaus Schaller (2): drm/panel: simple: Add Sharp LQ070Y3DG3B panel support drm/panel: simple: Add Ortustech COM37H3M panel support drivers/gpu/drm/panel/panel-simple.c | 63 ++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+) -- 2.19.1

1 2

[PATCH] dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc
by Chris Wilson 04 Jun '19

04 Jun '19

If we have to drop the seqcount & rcu lock to perform a krealloc, we have to restart the loop. In doing so, be careful not to lose track of the already acquired exclusive fence. Fixes: fedf54132d24 ("dma-buf: Restart reservation_object_get_fences_rcu() after writes") #v4.10 Signed-off-by: Chris Wilson <chris(a)chris-wilson.co.uk> Cc: Daniel Vetter <daniel.vetter(a)ffwll.ch> Cc: Maarten Lankhorst <maarten.lankhorst(a)linux.intel.com> Cc: Christian König <christian.koenig(a)amd.com> Cc: Alex Deucher <alexander.deucher(a)amd.com> Cc: Sumit Semwal <sumit.semwal(a)linaro.org> Cc: stable(a)vger.kernel.org --- drivers/dma-buf/reservation.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/dma-buf/reservation.c b/drivers/dma-buf/reservation.c index 4d32e2c67862..704503df4892 100644 --- a/drivers/dma-buf/reservation.c +++ b/drivers/dma-buf/reservation.c @@ -365,6 +365,12 @@ int reservation_object_get_fences_rcu(struct reservation_object *obj, GFP_NOWAIT | __GFP_NOWARN); if (!nshared) { rcu_read_unlock(); + + if (fence_excl) { + dma_fence_put(fence_excl); + fence_excl = NULL; + } + nshared = krealloc(shared, sz, GFP_KERNEL); if (nshared) { shared = nshared; -- 2.20.1

2 3

[PATCH v2 1/2] drm: bridge: dw-hdmi: Add hook for resume
by Douglas Anderson 04 Jun '19

04 Jun '19

On Rockchip rk3288-based Chromebooks when you do a suspend/resume cycle: 1. You lose the ability to detect an HDMI device being plugged in. 2. If you're using the i2c bus built in to dw_hdmi then it stops working. Let's add a hook to the core dw-hdmi driver so that we can call it in dw_hdmi-rockchip in the next commit. NOTE: the exact set of steps I've done here in resume come from looking at the normal dw_hdmi init sequence in upstream Linux plus the sequence that we did in downstream Chrome OS 3.14. Testing show that it seems to work, but if an extra step is needed or something here is not needed we could improve it. As part of this change we'll refactor the hardware init bits of dw-hdmi to happen all in one function and all at the same time. Since we need to init the interrupt mutes before we request the IRQ, this means moving the hardware init earlier in the function, but there should be no problems with that. Also as part of this we now unconditionally init the "i2c" parts of dw-hdmi, but again that ought to be fine. Signed-off-by: Douglas Anderson <dianders(a)chromium.org> --- Changes in v2: - No empty stub for suspend (Laurent) - Refactor to use the same code in probe and resume (Laurent) - Unconditionally init i2c (seems OK + needed before hdmi->i2c init) - Combine "init" of i2c and "setup" of i2c (no reason to split) drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 50 ++++++++++++++--------- include/drm/bridge/dw_hdmi.h | 2 + 2 files changed, 33 insertions(+), 19 deletions(-) diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c index ab7968c8f6a2..636d55d1398c 100644 --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c @@ -227,6 +227,13 @@ static void hdmi_mask_writeb(struct dw_hdmi *hdmi, u8 data, unsigned int reg, static void dw_hdmi_i2c_init(struct dw_hdmi *hdmi) { + hdmi_writeb(hdmi, HDMI_PHY_I2CM_INT_ADDR_DONE_POL, + HDMI_PHY_I2CM_INT_ADDR); + + hdmi_writeb(hdmi, HDMI_PHY_I2CM_CTLINT_ADDR_NAC_POL | + HDMI_PHY_I2CM_CTLINT_ADDR_ARBITRATION_POL, + HDMI_PHY_I2CM_CTLINT_ADDR); + /* Software reset */ hdmi_writeb(hdmi, 0x00, HDMI_I2CM_SOFTRSTZ); @@ -1925,16 +1932,6 @@ static int dw_hdmi_setup(struct dw_hdmi *hdmi, struct drm_display_mode *mode) return 0; } -static void dw_hdmi_setup_i2c(struct dw_hdmi *hdmi) -{ - hdmi_writeb(hdmi, HDMI_PHY_I2CM_INT_ADDR_DONE_POL, - HDMI_PHY_I2CM_INT_ADDR); - - hdmi_writeb(hdmi, HDMI_PHY_I2CM_CTLINT_ADDR_NAC_POL | - HDMI_PHY_I2CM_CTLINT_ADDR_ARBITRATION_POL, - HDMI_PHY_I2CM_CTLINT_ADDR); -} - static void initialize_hdmi_ih_mutes(struct dw_hdmi *hdmi) { u8 ih_mute; @@ -2435,6 +2432,21 @@ static const struct regmap_config hdmi_regmap_32bit_config = { .max_register = HDMI_I2CM_FS_SCL_LCNT_0_ADDR << 2, }; +static void dw_hdmi_init_hw(struct dw_hdmi *hdmi) +{ + initialize_hdmi_ih_mutes(hdmi); + + /* + * Reset HDMI DDC I2C master controller and mute I2CM interrupts. + * Even if we are using a separate i2c adapter doing this doesn't + * hurt. + */ + dw_hdmi_i2c_init(hdmi); + + if (hdmi->phy.ops->setup_hpd) + hdmi->phy.ops->setup_hpd(hdmi, hdmi->phy.data); +} + static struct dw_hdmi * __dw_hdmi_probe(struct platform_device *pdev, const struct dw_hdmi_plat_data *plat_data) @@ -2586,7 +2598,7 @@ __dw_hdmi_probe(struct platform_device *pdev, prod_id1 & HDMI_PRODUCT_ID1_HDCP ? "with" : "without", hdmi->phy.name); - initialize_hdmi_ih_mutes(hdmi); + dw_hdmi_init_hw(hdmi); irq = platform_get_irq(pdev, 0); if (irq < 0) { @@ -2625,10 +2637,6 @@ __dw_hdmi_probe(struct platform_device *pdev, hdmi->bridge.of_node = pdev->dev.of_node; #endif - dw_hdmi_setup_i2c(hdmi); - if (hdmi->phy.ops->setup_hpd) - hdmi->phy.ops->setup_hpd(hdmi, hdmi->phy.data); - memset(&pdevinfo, 0, sizeof(pdevinfo)); pdevinfo.parent = dev; pdevinfo.id = PLATFORM_DEVID_AUTO; @@ -2681,10 +2689,6 @@ __dw_hdmi_probe(struct platform_device *pdev, hdmi->cec = platform_device_register_full(&pdevinfo); } - /* Reset HDMI DDC I2C master controller and mute I2CM interrupts */ - if (hdmi->i2c) - dw_hdmi_i2c_init(hdmi); - return hdmi; err_iahb: @@ -2788,6 +2792,14 @@ void dw_hdmi_unbind(struct dw_hdmi *hdmi) } EXPORT_SYMBOL_GPL(dw_hdmi_unbind); +int dw_hdmi_resume(struct dw_hdmi *hdmi) +{ + dw_hdmi_init_hw(hdmi); + + return 0; +} +EXPORT_SYMBOL_GPL(dw_hdmi_resume); + MODULE_AUTHOR("Sascha Hauer <s.hauer(a)pengutronix.de>"); MODULE_AUTHOR("Andy Yan <andy.yan(a)rock-chips.com>"); MODULE_AUTHOR("Yakir Yang <ykk(a)rock-chips.com>"); diff --git a/include/drm/bridge/dw_hdmi.h b/include/drm/bridge/dw_hdmi.h index 66e70770cce5..1626731e1681 100644 --- a/include/drm/bridge/dw_hdmi.h +++ b/include/drm/bridge/dw_hdmi.h @@ -154,6 +154,8 @@ struct dw_hdmi *dw_hdmi_bind(struct platform_device *pdev, struct drm_encoder *encoder, const struct dw_hdmi_plat_data *plat_data); +int dw_hdmi_resume(struct dw_hdmi *hdmi); + void dw_hdmi_setup_rx_sense(struct dw_hdmi *hdmi, bool hpd, bool rx_sense); void dw_hdmi_set_sample_rate(struct dw_hdmi *hdmi, unsigned int rate); -- 2.21.0.1020.gf2820cf01a-goog

3 4

[PATCH 0/4] Document fixes for DRM UAPI and HDR
by Uma Shankar 04 Jun '19

04 Jun '19

This series adds DRM UAPI header structure documentation to kernel docs. Fixes issues with existing structure documentation in drm uapi header. This also fixes warnings in HDR doc and addresses suggestions from Daniel Vetter. Also dropped static function documentation in hdmi core. Uma Shankar (4): drm: Drop a redundant unused variable drm: Fix docbook warnings in hdr metadata helper structures drm: Fixed doc warnings in drm uapi header video/hdmi: Dropped static functions from kernel doc Documentation/gpu/drm-uapi.rst | 9 +++++++ drivers/gpu/drm/drm_connector.c | 31 ++++++++++++++++++++++ drivers/video/hdmi.c | 32 +++++++++++----------- include/drm/drm_connector.h | 3 +-- include/drm/drm_mode_config.h | 4 +-- include/linux/hdmi.h | 1 + include/uapi/drm/drm_mode.h | 59 ++++++++++++++++++++++++++++++++++++++++- 7 files changed, 118 insertions(+), 21 deletions(-) -- 1.9.1

3 13

[RESEND PATCH v2] drm/vmwgfx: fix a warning due to missing dma_parms
by Qian Cai 04 Jun '19

04 Jun '19

Booting up with DMA_API_DEBUG_SG=y generates a warning due to the driver forgot to set dma_parms appropriately. Set it just after vmw_dma_masks() in vmw_driver_load(). DMA-API: vmwgfx 0000:00:0f.0: mapping sg segment longer than device claims to support [len=2097152] [max=65536] WARNING: CPU: 2 PID: 261 at kernel/dma/debug.c:1232 debug_dma_map_sg+0x360/0x480 Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/13/2018 RIP: 0010:debug_dma_map_sg+0x360/0x480 Call Trace: vmw_ttm_map_dma+0x3b1/0x5b0 [vmwgfx] vmw_bo_map_dma+0x25/0x30 [vmwgfx] vmw_otables_setup+0x2a8/0x750 [vmwgfx] vmw_request_device_late+0x78/0xc0 [vmwgfx] vmw_request_device+0xee/0x4e0 [vmwgfx] vmw_driver_load.cold+0x757/0xd84 [vmwgfx] drm_dev_register+0x1ff/0x340 [drm] drm_get_pci_dev+0x110/0x290 [drm] vmw_probe+0x15/0x20 [vmwgfx] local_pci_probe+0x7a/0xc0 pci_device_probe+0x1b9/0x290 really_probe+0x1b5/0x630 driver_probe_device+0xa3/0x1a0 device_driver_attach+0x94/0xa0 __driver_attach+0xdd/0x1c0 bus_for_each_dev+0xfe/0x150 driver_attach+0x2d/0x40 bus_add_driver+0x290/0x350 driver_register+0xdc/0x1d0 __pci_register_driver+0xda/0xf0 vmwgfx_init+0x34/0x1000 [vmwgfx] do_one_initcall+0xe5/0x40a do_init_module+0x10f/0x3a0 load_module+0x16a5/0x1a40 __se_sys_finit_module+0x183/0x1c0 __x64_sys_finit_module+0x43/0x50 do_syscall_64+0xc8/0x606 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Fixes: fb1d9738ca05 ("drm/vmwgfx: Add DRM driver for VMware Virtual GPU") Suggested-by: Thomas Hellstrom <thellstrom(a)vmware.com> Signed-off-by: Qian Cai <cai(a)lca.pw> --- drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c index 4ff11a0077e1..5f690429eb89 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c @@ -747,6 +747,8 @@ static int vmw_driver_load(struct drm_device *dev, unsigned long chipset) if (unlikely(ret != 0)) goto out_err0; + dma_set_max_seg_size(dev->dev, U32_MAX); + if (dev_priv->capabilities & SVGA_CAP_GMR2) { DRM_INFO("Max GMR ids is %u\n", (unsigned)dev_priv->max_gmr_ids); -- 1.8.3.1

2 1

[PATCH v7 0/8] drm/fb-helper: Move modesetting code to drm_client
by Noralf Trønnes 04 Jun '19

04 Jun '19

This moves the modesetting code from drm_fb_helper to drm_client so it can be shared by all internal clients. Changes this time: - Declare drm_mode_set and drm_plane_state in patch 1 - Export drm_client_panel_rotation() (Gerd Hoffmann) - Rebase Noralf. Cc: Gerd Hoffmann <kraxel(a)redhat.com> Noralf Trønnes (8): drm/atomic: Move __drm_atomic_helper_disable_plane/set_config() drm/fb-helper: Remove drm_fb_helper_crtc drm/fb-helper: Prepare to move out commit code drm/fb-helper: Move out commit code drm/fb-helper: Remove drm_fb_helper_connector drm/fb-helper: Prepare to move out modeset config code drm/fb-helper: Move out modeset config code drm/client: Hack: Add bootsplash example Documentation/gpu/drm-client.rst | 3 + Documentation/gpu/todo.rst | 7 + drivers/gpu/drm/Kconfig | 5 + drivers/gpu/drm/Makefile | 3 +- drivers/gpu/drm/drm_atomic.c | 168 ++++ drivers/gpu/drm/drm_atomic_helper.c | 164 ---- drivers/gpu/drm/drm_bootsplash.c | 358 +++++++ drivers/gpu/drm/drm_client.c | 17 +- drivers/gpu/drm/drm_client_modeset.c | 1087 +++++++++++++++++++++ drivers/gpu/drm/drm_crtc_internal.h | 7 + drivers/gpu/drm/drm_drv.c | 4 + drivers/gpu/drm/drm_fb_helper.c | 1305 ++------------------------ include/drm/drm_atomic_helper.h | 4 - include/drm/drm_client.h | 49 + include/drm/drm_fb_helper.h | 92 +- 15 files changed, 1803 insertions(+), 1470 deletions(-) create mode 100644 drivers/gpu/drm/drm_bootsplash.c create mode 100644 drivers/gpu/drm/drm_client_modeset.c -- 2.20.1

1 9

[PATCH 00/22] Some documentation fixes
by Mauro Carvalho Chehab 04 Jun '19

04 Jun '19

Fix several warnings and broken links. This series was generated against linux-next, but was rebased to be applied at docs-next. It should apply cleanly on either tree. There's a git tree with all of them applied on the top of docs/docs-next at: https://git.linuxtv.org/mchehab/experimental.git/log/?h=fix_doc_links_v2 Mauro Carvalho Chehab (21): ABI: sysfs-devices-system-cpu: point to the right docs isdn: mISDN: remove a bogus reference to a non-existing doc dt: fix broken references to nand.txt docs: zh_CN: get rid of basic_profiling.txt doc: it_IT: fix reference to magic-number.rst docs: mm: numaperf.rst: get rid of a build warning docs: bpf: get rid of two warnings docs: mark orphan documents as such docs: amd-memory-encryption.rst get rid of warnings gpu: amdgpu: fix broken amdgpu_dma_buf.c references gpu: i915.rst: Fix references to renamed files docs: zh_CN: avoid duplicate citation references docs: vm: hmm.rst: fix some warnings docs: it: license-rules.rst: get rid of warnings docs: gpio: driver.rst: fix a bad tag docs: soundwire: locking: fix tags for a code-block docs: security: trusted-encrypted.rst: fix code-block tag docs: security: core.rst: Fix several warnings docs: net: dpio-driver.rst: fix two codeblock warnings docs: net: sja1105.rst: fix table format docs: fix broken documentation links Otto Sabart (1): mfd: madera: Fix bad reference to pinctrl.txt file .../ABI/testing/sysfs-devices-system-cpu | 3 +- Documentation/accelerators/ocxl.rst | 2 + Documentation/acpi/dsd/leds.txt | 2 +- .../admin-guide/kernel-parameters.rst | 6 +- .../admin-guide/kernel-parameters.txt | 16 ++--- Documentation/admin-guide/mm/numaperf.rst | 5 +- Documentation/admin-guide/ras.rst | 2 +- Documentation/arm/stm32/overview.rst | 2 + .../arm/stm32/stm32f429-overview.rst | 2 + .../arm/stm32/stm32f746-overview.rst | 2 + .../arm/stm32/stm32f769-overview.rst | 2 + .../arm/stm32/stm32h743-overview.rst | 2 + .../arm/stm32/stm32mp157-overview.rst | 2 + Documentation/bpf/btf.rst | 2 + .../bindings/mtd/amlogic,meson-nand.txt | 2 +- .../devicetree/bindings/mtd/gpmc-nand.txt | 2 +- .../devicetree/bindings/mtd/marvell-nand.txt | 2 +- .../devicetree/bindings/mtd/tango-nand.txt | 2 +- .../devicetree/bindings/net/fsl-enetc.txt | 7 +- .../bindings/pci/amlogic,meson-pcie.txt | 2 +- .../regulator/qcom,rpmh-regulator.txt | 2 +- .../devicetree/booting-without-of.txt | 2 +- Documentation/driver-api/gpio/board.rst | 2 +- Documentation/driver-api/gpio/consumer.rst | 2 +- Documentation/driver-api/gpio/driver.rst | 2 +- .../driver-api/soundwire/locking.rst | 4 +- .../firmware-guide/acpi/enumeration.rst | 2 +- .../firmware-guide/acpi/method-tracing.rst | 2 +- Documentation/gpu/amdgpu.rst | 4 +- Documentation/gpu/i915.rst | 6 +- Documentation/gpu/msm-crash-dump.rst | 2 + Documentation/i2c/instantiating-devices | 2 +- Documentation/interconnect/interconnect.rst | 2 + Documentation/laptops/lg-laptop.rst | 2 + .../freescale/dpaa2/dpio-driver.rst | 4 +- Documentation/networking/dsa/sja1105.rst | 6 +- Documentation/powerpc/isa-versions.rst | 2 + Documentation/security/keys/core.rst | 16 +++-- .../security/keys/trusted-encrypted.rst | 4 +- Documentation/sysctl/kernel.txt | 4 +- .../translations/it_IT/process/howto.rst | 2 +- .../it_IT/process/license-rules.rst | 28 ++++---- .../it_IT/process/magic-number.rst | 2 +- .../it_IT/process/stable-kernel-rules.rst | 4 +- .../translations/zh_CN/basic_profiling.txt | 71 ------------------- .../translations/zh_CN/process/4.Coding.rst | 2 +- .../zh_CN/process/management-style.rst | 4 +- .../zh_CN/process/programming-language.rst | 28 ++++---- .../virtual/kvm/amd-memory-encryption.rst | 5 ++ Documentation/virtual/kvm/vcpu-requests.rst | 2 + Documentation/vm/hmm.rst | 9 ++- Documentation/x86/x86_64/5level-paging.rst | 2 +- Documentation/x86/x86_64/boot-options.rst | 4 +- .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- MAINTAINERS | 6 +- arch/arm/Kconfig | 2 +- arch/arm64/kernel/kexec_image.c | 2 +- arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 16 ++--- arch/x86/Kconfig.debug | 2 +- arch/x86/boot/header.S | 2 +- arch/x86/entry/entry_64.S | 2 +- arch/x86/include/asm/bootparam_utils.h | 2 +- arch/x86/include/asm/page_64_types.h | 2 +- arch/x86/include/asm/pgtable_64_types.h | 2 +- arch/x86/kernel/cpu/microcode/amd.c | 2 +- arch/x86/kernel/kexec-bzimage64.c | 2 +- arch/x86/kernel/pci-dma.c | 2 +- arch/x86/mm/tlb.c | 2 +- arch/x86/platform/pvh/enlighten.c | 2 +- drivers/acpi/Kconfig | 10 +-- drivers/isdn/mISDN/dsp_core.c | 2 - drivers/net/ethernet/faraday/ftgmac100.c | 2 +- .../fieldbus/Documentation/fieldbus_dev.txt | 4 +- drivers/vhost/vhost.c | 2 +- include/acpi/acpi_drivers.h | 2 +- include/linux/fs_context.h | 2 +- include/linux/lsm_hooks.h | 2 +- include/linux/mfd/madera/pdata.h | 3 +- mm/Kconfig | 2 +- security/Kconfig | 2 +- tools/include/linux/err.h | 2 +- .../Documentation/stack-validation.txt | 4 +- tools/testing/selftests/x86/protection_keys.c | 2 +- 84 files changed, 183 insertions(+), 212 deletions(-) delete mode 100644 Documentation/translations/zh_CN/basic_profiling.txt -- 2.21.0

7 10

[Bug 203779] New: drm:amdgpu_ib_ring_tests [amdgpu] *ERROR* IB test failed on gfx (-110)
by bugzilla-daemon＠bugzilla.kernel.org 04 Jun '19

04 Jun '19

https://bugzilla.kernel.org/show_bug.cgi?id=203779 Bug ID: 203779 Summary: drm:amdgpu_ib_ring_tests [amdgpu] *ERROR* IB test failed on gfx (-110) Product: Drivers Version: 2.5 Kernel Version: 5.1.6 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: gobinda.joy(a)gmail.com Regression: No My hardware is as follows: CPU: i7 3770 at stock clock Motherboard: Gigabyte G1.Sniper 3 latest BIOS available RAM: 24 GB DDR3 at 1600 mhz GPU: RX 580 8GB (Sapphire) latest VBIOS The problem is with kernel 5.1.0 or higher (currently 5.1.6) Display hangs when amdgpu driver loads. I'm unable to determine if the booting is continued or hangs as well. Disk activity stops after couple seconds and not possible to switch TTY. Ctrl+Alt+Del is unresponsive as well. This problem goes away when amdgpu.dpm=0 is used but in that case dynamic power scaling is not available and gpu stuck at low clock, graphics performance is abysmal. Also GPU temp/fan speed utilities doesn't work. Here is the excerpt of the problematic log lines: Jun 02 09:54:05 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:06 kernel: amdgpu: [powerplay] failed to send message 15b ret is 65535 Jun 02 09:54:06 kernel: hrtimer: interrupt took 287743313 ns Jun 02 09:54:06 kernel: clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jun 02 09:54:06 kernel: clocksource: 'hpet' wd_now: 628dd7b wd_last: 5fef431 mask: ffffffff Jun 02 09:54:06 kernel: clocksource: 'tsc' cs_now: 254aa24747 cs_last: 25104a5bfd mask: ffffffffffffffff Jun 02 09:54:06 kernel: tsc: Marking TSC unstable due to clocksource watchdog Jun 02 09:54:07 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:07 kernel: amdgpu: [powerplay] failed to send message 148 ret is 65535 Jun 02 09:54:07 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:07 kernel: amdgpu: [powerplay] failed to send message 145 ret is 65535 Jun 02 09:54:08 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:08 kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jun 02 09:54:08 kernel: sched_clock: Marking unstable (8791691311, 362291)<-(8817904668, -25851212) Jun 02 09:54:08 kernel: amdgpu: [powerplay] failed to send message 146 ret is 65535 Jun 02 09:54:08 kernel: hid-generic 0003:09DA:FC7C.0003: input,hidraw2: USB HID v1.11 Mouse [COMPANY USB Device] on usb-0000:00:1a.0-1.5.3/input0 Jun 02 09:54:09 kernel: hid-generic 0003:09DA:FC7C.0004: hiddev97,hidraw3: USB HID v1.11 Device [COMPANY USB Device] on usb-0000:00:1a.0-1.5.3/input1 Jun 02 09:54:11 kernel: clocksource: Switched to clocksource hpet Jun 02 09:54:13 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:13 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:14 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:15 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:15 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:15 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:15 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] last message was failed ret is 65535 Jun 02 09:54:16 kernel: amdgpu: [powerplay] failed to send message 260 ret is 65535 Jun 02 09:54:17 kernel: [drm] Initialized amdgpu 3.30.0 20150101 for 0000:04:00.0 on minor 0 Jun 02 09:54:17 kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) Jun 02 09:54:20 kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx (-110). Jun 02 09:54:21 kernel: [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110). Any help is appreciated. Also let me know if I can help in any way. -- You are receiving this mail because: You are watching the assignee of the bug.

1 5

[PATCH v4 0/5] drm: Fix fb changes for async updates
by Helen Koike 04 Jun '19

04 Jun '19

Hello, I'm re-sending this series with the acked by in the msm patch and updating the docs in the last patch, the rest is the same. v3 link: https://patchwork.kernel.org/project/dri-devel/list/?series=91353 Thanks! Helen Changes in v4: - add acked by tag - update docs in atomic_async_update callback Changes in v3: - use swap() to swap old and new framebuffers in async_update - get the reference to old_fb and set the worker after vop_plane_atomic_update() - add a FIXME tag for when we have multiple fbs to be released when vblank happens. - update commit message - Add Reviewed-by tags - Add TODO in drm_atomic_helper_async_commit() Changes in v2: - added reviewed-by tag - update CC stable and Fixes tag - Added reviewed-by tag - updated CC stable and Fixes tag - Change the order of the patch in the series, add this as the last one. - Add documentation - s/ballanced/balanced Helen Koike (5): drm/rockchip: fix fb references in async update drm/amd: fix fb references in async update drm/msm: fix fb references in async update drm/vc4: fix fb references in async update drm: don't block fb changes for async plane updates .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 3 +- drivers/gpu/drm/drm_atomic_helper.c | 22 ++++---- drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c | 4 ++ drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 51 ++++++++++--------- drivers/gpu/drm/vc4/vc4_plane.c | 2 +- include/drm/drm_modeset_helper_vtables.h | 8 +++ 6 files changed, 52 insertions(+), 38 deletions(-) -- 2.20.1

2 9

Panfrost impossible to probe without opp table
by Clément Péron 04 Jun '19

04 Jun '19

Hi, I have rebase my kernel on latest 5.2-rc2, and my panfrost driver is no more probing. The issue is coming from f3617b449d0bcf3b5d80a97f51498dcf7463cf7e drm/panfrost: Select devfreq Currently, there is some logic for the driver to work without devfreq. However, the driver actually fails to probe if !CONFIG_PM_DEVFREQ. Fix this by selecting devfreq, and drop the additional checks for devfreq. It seems that with this commit the OPP table is now mandatory. is it intentional? Actually [ 3.046237] panfrost 1800000.gpu: clock rate = 432000000 [ 3.051593] panfrost 1800000.gpu: bus_clock rate = 100000000 [ 3.096012] panfrost 1800000.gpu: mali-t720 id 0x720 major 0x1 minor 0x1 status 0x0 [ 3.103682] panfrost 1800000.gpu: features: 00000000,10309e40, issues: 00000000,21054400 [ 3.111789] panfrost 1800000.gpu: Features: L2:0x07110206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002821 AS:0xf JS:0x7 [ 3.123435] panfrost 1800000.gpu: shader_present=0x3 l2_present=0x1 [ 3.130405] panfrost 1800000.gpu: Fatal error during devfreq init With commit reverted [ 3.038236] panfrost 1800000.gpu: clock rate = 432000000 [ 3.043593] panfrost 1800000.gpu: bus_clock rate = 100000000 [ 3.087994] panfrost 1800000.gpu: mali-t720 id 0x720 major 0x1 minor 0x1 status 0x0 [ 3.095658] panfrost 1800000.gpu: features: 00000000,10309e40, issues: 00000000,21054400 [ 3.103763] panfrost 1800000.gpu: Features: L2:0x07110206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002821 AS:0xf JS:0x7 [ 3.115410] panfrost 1800000.gpu: shader_present=0x3 l2_present=0x1 [ 3.122798] [drm] Initialized panfrost 1.0.0 20180908 for 1800000.gpu on minor 0 Thanks, Clément

3 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2019