dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

inverted brightness for HP notebook
by olivier.fambon＠free.fr 18 Jun '15

18 Jun '15

Hi there, $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation ValleyView Gen7 (rev 0e) $ sudo lspci -v -s 00:02 00:02.0 VGA compatible controller: Intel Corporation ValleyView Gen7 (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 2213 Flags: bus master, fast devsel, latency 0, IRQ 107 Memory at 90000000 (32-bit, non-prefetchable) [size=4M] Memory at 80000000 (32-bit, prefetchable) [size=256M] I/O ports at 3050 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [d0] Power Management version 2 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [b0] Vendor Specific Information: Len=07 <?> Kernel driver in use: i915 => requires the following to make brightness control keys work as expected $ cat /etc/modprobe.d/i915.conf options i915 invert_brightness=1 tested on ubuntu 14.04 (with added xorg conf below) $ cat /usr/share/X11/xorg.conf.d/20-intel.conf Section "Device" Identifier "card0" Driver "intel" Option "Backlight" "intel_backlight" BusID "PCI:0:2:0" EndSection Note that the same brightness inversion happened also on ubuntu 14.10 (vanilla install, no xorg conf required) Cheers, Olivier.

3 3

[PULL] drm-intel-fixes
by Jani Nikula 18 Jun '15

18 Jun '15

Hi Dave, final i915 fixes for v4.1. BR, Jani. The following changes since commit 0f57d86787d8b1076ea8f9cbdddda2a46d534a27: Linux 4.1-rc8 (2015-06-14 15:51:10 -1000) are available in the git repository at: git://anongit.freedesktop.org/drm-intel tags/drm-intel-fixes-2015-06-18 for you to fetch changes up to 245ec9d85696c3e539b23e210f248698b478379c: Revert "drm/i915: Don't skip request retirement if the active list is empty" (2015-06-15 14:32:54 +0300) ---------------------------------------------------------------- Chris Wilson (1): drm/i915: Always reset vma->ggtt_view.pages cache on unbinding Jani Nikula (1): Revert "drm/i915: Don't skip request retirement if the active list is empty" drivers/gpu/drm/i915/i915_gem.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) -- Jani Nikula, Intel Open Source Technology Center

1 0

[PATCH] Fixes: 9697dffb098d ("drm: Turn off Legacy Context Functions")
by Eddie Kovsky 18 Jun '15

18 Jun '15

Commit 9697dffb098d ("drm: Turn off Legacy Context Functions") added checks for legacy features to several functions in the drm driver. It is now possible for the void functions changed by this commit to return an int error code. This patch updates the function definitions to return int. This fixes the build warnings: warning: ‘return’ with a value, in function returning void return -EINVAL Signed-off-by: Eddie Kovsky <ewk(a)edkovsky.org> --- drivers/gpu/drm/drm_context.c | 12 +++++++++--- drivers/gpu/drm/drm_legacy.h | 6 +++--- 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/drm_context.c b/drivers/gpu/drm/drm_context.c index f3ea657f6574..3c2f4a76f934 100644 --- a/drivers/gpu/drm/drm_context.c +++ b/drivers/gpu/drm/drm_context.c @@ -51,7 +51,7 @@ struct drm_ctx_list { * in drm_device::ctx_idr, while holding the drm_device::struct_mutex * lock. */ -void drm_legacy_ctxbitmap_free(struct drm_device * dev, int ctx_handle) +int drm_legacy_ctxbitmap_free(struct drm_device * dev, int ctx_handle) { if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && drm_core_check_feature(dev, DRIVER_MODESET)) @@ -60,6 +60,8 @@ void drm_legacy_ctxbitmap_free(struct drm_device * dev, int ctx_handle) mutex_lock(&dev->struct_mutex); idr_remove(&dev->ctx_idr, ctx_handle); mutex_unlock(&dev->struct_mutex); + + return 0; } /** @@ -107,7 +109,7 @@ int drm_legacy_ctxbitmap_init(struct drm_device * dev) * Free all idr members using drm_ctx_sarea_free helper function * while holding the drm_device::struct_mutex lock. */ -void drm_legacy_ctxbitmap_cleanup(struct drm_device * dev) +int drm_legacy_ctxbitmap_cleanup(struct drm_device * dev) { if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && drm_core_check_feature(dev, DRIVER_MODESET)) @@ -116,6 +118,8 @@ void drm_legacy_ctxbitmap_cleanup(struct drm_device * dev) mutex_lock(&dev->struct_mutex); idr_destroy(&dev->ctx_idr); mutex_unlock(&dev->struct_mutex); + + return 0; } /** @@ -127,7 +131,7 @@ void drm_legacy_ctxbitmap_cleanup(struct drm_device * dev) * @file. Note that after this call returns, new contexts might be added if * the file is still alive. */ -void drm_legacy_ctxbitmap_flush(struct drm_device *dev, struct drm_file *file) +int drm_legacy_ctxbitmap_flush(struct drm_device *dev, struct drm_file *file) { struct drm_ctx_list *pos, *tmp; @@ -150,6 +154,8 @@ void drm_legacy_ctxbitmap_flush(struct drm_device *dev, struct drm_file *file) } mutex_unlock(&dev->ctxlist_mutex); + + return 0; } /*@}*/ diff --git a/drivers/gpu/drm/drm_legacy.h b/drivers/gpu/drm/drm_legacy.h index c1dc61473db5..26c16220e475 100644 --- a/drivers/gpu/drm/drm_legacy.h +++ b/drivers/gpu/drm/drm_legacy.h @@ -43,9 +43,9 @@ struct drm_file; #define DRM_RESERVED_CONTEXTS 1 int drm_legacy_ctxbitmap_init(struct drm_device *dev); -void drm_legacy_ctxbitmap_cleanup(struct drm_device *dev); -void drm_legacy_ctxbitmap_free(struct drm_device *dev, int ctx_handle); -void drm_legacy_ctxbitmap_flush(struct drm_device *dev, struct drm_file *file); +int drm_legacy_ctxbitmap_cleanup(struct drm_device *dev); +int drm_legacy_ctxbitmap_free(struct drm_device *dev, int ctx_handle); +int drm_legacy_ctxbitmap_flush(struct drm_device *dev, struct drm_file *file); int drm_legacy_resctx(struct drm_device *d, void *v, struct drm_file *f); int drm_legacy_addctx(struct drm_device *d, void *v, struct drm_file *f); -- 2.4.3

2 1

drm/i915: WARN_ON(dev_priv->mm.busy)
by Jeremiah Mahler 18 Jun '15

18 Jun '15

all, On all my machines with Intel graphics I get the following warning in the logs when the machine is suspended. Apparently some part of the graphics system is busy when it should be idle. This is present on the latest linux-next 20150604. ... [ 33.141747] Suspending console(s) (use no_console_suspend to debug) [ 33.142146] wlan0: deauthenticating from 00:1a:70:5a:6e:0b by local choice (Reason: 3=DEAUTH_LEAVING) [ 33.147395] queueing ieee80211 work while going to suspend [ 33.151597] cfg80211: Calling CRDA to update world regulatory domain [ 33.190430] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 33.190523] sd 0:0:0:0: [sda] Stopping disk [ 33.275743] ------------[ cut here ]------------ [ 33.275764] WARNING: CPU: 0 PID: 1617 at drivers/gpu/drm/i915/i915_gem.c:4808 i915_gem_suspend+0xe4/0xf0 [i915]() [ 33.275766] WARN_ON(dev_priv->mm.busy) [ 33.275811] Modules linked in: binfmt_misc snd_hda_codec_hdmi hid_generic isl29018(C) industrialio regmap_i2c cyapatp crc_itu_t usbhid hid arc4 x86_pkg_temp_thermal intel_powerclamp intel_rapl iosf_mbi coretemp ath9k tpm_infineon kvm_intel kvm ath9k_common ath9k_hw crct10dif_pclmul crc32_pclmul crc32c_intel chromeos_laptop ath mac80211 ghash_clmulni_intel cryptd i915 cfg80211 pcspkr serio_raw sg ath3k btusb btrtl lpc_ich snd_hda_codec_realtek shpchp i2c_i801 mfd_core snd_hda_codec_generic btbcm btintel bluetooth snd_hda_intel battery snd_hda_codec ac i2c_algo_bit drm_kms_helper tpm_tis snd_hwdep tpm snd_hda_core drm snd_pcm video rfkill processor button snd_timer snd soundcore i2c_designware_pci i2c_designware_core evdev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev [ 33.275825] media i2c_core fuse autofs4 ext4 crc16 mbcache jbd2 sd_mod fan xhci_pci sdhci_acpi sdhci xhci_hcd mmc_core thermal thermal_sys usbcore ahci libahci usb_common libata scsi_mod [ 33.275828] CPU: 0 PID: 1617 Comm: kworker/u4:4 Tainted: G C 4.1.0-rc6-next-20150604+ #207 [ 33.275829] Hardware name: Acer Peppy, BIOS 04/30/2014 [ 33.275834] Workqueue: events_unbound async_run_entry_fn [ 33.275838] 0000000000000000 ffffffffa05b7908 ffffffff8152ca4d ffff880035effc58 [ 33.275840] ffffffff8106bce1 ffff880073587f20 0000000000000000 ffff880073580000 [ 33.275842] ffff88003534f860 ffff880073580000 ffffffff8106bd5a ffffffffa05c74c1 [ 33.275843] Call Trace: [ 33.275849] [<ffffffff8152ca4d>] ? dump_stack+0x40/0x50 [ 33.275853] [<ffffffff8106bce1>] ? warn_slowpath_common+0x81/0xb0 [ 33.275855] [<ffffffff8106bd5a>] ? warn_slowpath_fmt+0x4a/0x50 [ 33.275865] [<ffffffffa0520264>] ? i915_gem_suspend+0xe4/0xf0 [i915] [ 33.275872] [<ffffffffa04f48c1>] ? i915_drm_suspend+0x61/0x1b0 [i915] [ 33.275876] [<ffffffff81302381>] ? pci_pm_suspend+0x71/0x140 [ 33.275878] [<ffffffff81302310>] ? pci_pm_freeze+0xd0/0xd0 [ 33.275881] [<ffffffff813e1699>] ? dpm_run_callback+0x39/0xd0 [ 33.275883] [<ffffffff813e20d4>] ? __device_suspend+0xe4/0x300 [ 33.275884] [<ffffffff813e230e>] ? async_suspend+0x1e/0x90 [ 33.275887] [<ffffffff8108a893>] ? async_run_entry_fn+0x43/0x150 [ 33.275890] [<ffffffff810828f8>] ? process_one_work+0x148/0x3b0 [ 33.275892] [<ffffffff81082e8a>] ? worker_thread+0x4a/0x440 [ 33.275895] [<ffffffff81082e40>] ? rescuer_thread+0x2e0/0x2e0 [ 33.275898] [<ffffffff81088121>] ? kthread+0xc1/0xe0 [ 33.275901] [<ffffffff81088060>] ? kthread_create_on_node+0x190/0x190 [ 33.275904] [<ffffffff8153365f>] ? ret_from_fork+0x3f/0x70 [ 33.275907] [<ffffffff81088060>] ? kthread_create_on_node+0x190/0x190 [ 33.275908] ---[ end trace e1c3eb5e163b3520 ]--- [ 33.560558] PM: suspend of devices complete after 423.034 msecs [ 33.577985] PM: late suspend of devices complete after 17.589 msecs [ 33.579036] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI [ 33.594059] PM: noirq suspend of devices complete after 16.226 msecs [ 33.594498] ACPI: Preparing to enter system sleep state S3 [ 33.595066] ACPI : EC: EC stopped ... -- - Jeremiah Mahler

4 7

4.1-rc7: Xorg broken after resume on thinkpad T40p, radeon problem?
by Pavel Machek 17 Jun '15

17 Jun '15

Hi! Video is broken on thinkpad T40p after resume from suspend. (In X only, text console still works.) Maybe this is related? [ 5430.193071] radeon 0000:01:00.0: putting AGP V2 device into 4x mode [ 5430.193107] radeon 0000:01:00.0: GTT: 256M 0xD0000000 - 0xDFFFFFFF [ 5430.214670] radeon 0000:01:00.0: WB disabled [ 5430.214675] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000d0000000 and cpu addr 0xf841a000 [ 5430.214721] [drm] radeon: ring at 0x00000000D0001000 [ 5430.370867] [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E8)=0xCAFEDEAD) [ 5430.370869] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22). [ 5430.370872] radeon 0000:01:00.0: failed initializing CP (-22). Hibernation works well here, including X. (Which has small glitch with mouse cursor being corrupted until it is changed by application). Any ideas? Pavel [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 4.1.0-rc7+ (pavel@amd) (gcc version 4.9.2 (Debian 4.9.2-10) ) #89 SMP Wed Jun 17 10:27:56 CEST 2015 [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000000d2000-0x00000000000d3fff] reserved ... [ 5427.867556] PM: Syncing filesystems ... done. [ 5428.043929] PM: Preparing system for mem sleep [ 5428.044503] Freezing user space processes ... (elapsed 0.219 seconds) done. [ 5428.264427] Freezing remaining freezable tasks ... (elapsed 0.007 seconds) done. [ 5428.272397] PM: Entering mem sleep [ 5428.272445] Suspending console(s) (use no_console_suspend to debug) [ 5428.468800] wlan1: deauthenticating from 00:11:95:05:30:d7 by local choice (Reason: 3=DEAUTH_LEAVING) [ 5428.529996] parport_pc 00:07: disabled [ 5428.530278] serial 00:06: disabled [ 5428.530637] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 5428.530909] sd 0:0:0:0: [sda] Stopping disk [ 5428.530986] cfg80211: Calling CRDA to update world regulatory domain [ 5428.531296] serial 00:06: System wakeup disabled by ACPI [ 5428.585816] pci 0000:00:1e.0: System wakeup enabled by ACPI [ 5428.588374] radeon 0000:01:00.0: Refused to change power state, currently in D0 [ 5428.960707] PM: suspend of devices complete after 687.029 msecs [ 5428.960711] PM: suspend devices took 0.688 seconds [ 5428.963240] PM: late suspend of devices complete after 2.522 msecs [ 5428.965743] pci0000:00: System wakeup enabled by ACPI [ 5428.965965] uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI [ 5429.044103] uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI [ 5429.044148] PM: noirq suspend of devices complete after 80.904 msecs [ 5429.044391] ACPI: Preparing to enter system sleep state S3 [ 5429.428156] ACPI : EC: EC stopped [ 5429.428158] PM: Saving platform NVS memory [ 5429.428203] Disabling non-boot CPUs ... [ 5429.428203] ACPI: Low-level resume complete [ 5429.428203] ACPI : EC: EC started [ 5429.428203] PM: Restoring platform NVS memory [ 5429.428357] ACPI: Waking up from system sleep state S3 [ 5430.188112] uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI [ 5430.188223] uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI [ 5430.188273] pci0000:00: System wakeup disabled by ACPI [ 5430.188675] PM: noirq resume of devices complete after 80.536 msecs [ 5430.192180] PM: early resume of devices complete after 2.138 msecs [ 5430.192754] usb usb2: root hub lost power or was reset [ 5430.192796] usb usb3: root hub lost power or was reset [ 5430.192835] usb usb4: root hub lost power or was reset [ 5430.192986] [drm] AGP mode requested: 4 [ 5430.192990] agpgart-intel 0000:00:00.0: AGP 2.0 bridge [ 5430.193015] agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode [ 5430.193071] radeon 0000:01:00.0: putting AGP V2 device into 4x mode [ 5430.193107] radeon 0000:01:00.0: GTT: 256M 0xD0000000 - 0xDFFFFFFF [ 5430.214670] radeon 0000:01:00.0: WB disabled [ 5430.214675] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000d0000000 and cpu addr 0xf841a000 [ 5430.214721] [drm] radeon: ring at 0x00000000D0001000 [ 5430.370867] [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E8)=0xCAFEDEAD) [ 5430.370869] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22). [ 5430.370872] radeon 0000:01:00.0: failed initializing CP (-22). [ 5430.858899] pci 0000:00:1e.0: System wakeup disabled by ACPI [ 5430.865104] rtc_cmos 00:02: System wakeup disabled by ACPI [ 5430.866275] serial 00:06: activated [ 5430.867674] parport_pc 00:07: activated [ 5430.871577] sd 0:0:0:0: [sda] Starting disk [ 5431.032503] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES) filtered out [ 5431.032507] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out [ 5431.032712] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded [ 5431.032913] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded [ 5431.056386] ata2.00: configured for UDMA/33 [ 5431.200097] usb 4-1: reset full-speed USB device number 2 using uhci_hcd [ 5431.808764] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 5431.808768] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 5431.808772] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out [ 5431.808775] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out [ 5431.824335] ata1.00: configured for UDMA/100 [ 5432.197993] PM: resume of devices complete after 2005.805 msecs [ 5432.200591] PM: resume devices took 2.008 seconds [ 5432.200718] PM: Finishing wakeup. [ 5432.200722] Restarting tasks ... done. [ 5434.742039] cfg80211: World regulatory domain updated: [ 5434.742049] cfg80211: DFS Master region: unset [ 5434.742053] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 5434.742061] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 5434.742066] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 5434.742071] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 5434.742076] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 5434.742082] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 5434.742087] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 5434.742092] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 5434.742096] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 5437.929693] wlan1: authenticate with 00:11:95:05:30:d7 [ 5438.016901] wlan1: send auth to 00:11:95:05:30:d7 (try 1/3) [ 5438.018898] wlan1: authenticated [ 5438.025830] ath5k 0000:02:02.0 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 5438.025842] ath5k 0000:02:02.0 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 5438.025863] wlan1: associating with AP with corrupt beacon [ 5438.028549] wlan1: associate with 00:11:95:05:30:d7 (try 1/3) [ 5438.030604] wlan1: RX AssocResp from 00:11:95:05:30:d7 (capab=0x401 status=0 aid=9) [ 5438.030759] wlan1: associated -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

3 7

[PATCH 0/2] RFC: Secure Memory Allocation Framework
by Benjamin Gaignard 17 Jun '15

17 Jun '15

The outcome of the previous RFC about how do secure data path was the need of a secure memory allocator (https://lkml.org/lkml/2015/5/5/551) SMAF goal is to provide a framework that allow allocating and securing memory by using dma_buf. Each platform have it own way to perform those two features so SMAF design allow to register helper modules to perform them. To be sure to select the best allocation method for devices SMAF implement deferred allocation mechanism: memory allocation is only done when the first device effectively required it. Allocator modules have to implement a match() to let SMAF know if they are compatibles with devices needs. This patch set provide an example of allocator module which use dma_{alloc/free/mmap}_attrs() and check if at least one device have coherent_dma_mask set to DMA_BIT_MASK(32) in match function. I have named smaf-cma.c like it is done for drm_gem_cma_helper.c even if a better name could be found for this file. Secure modules are responsibles of granting and revoking devices access rights on the memory. Secure module is also called to check if CPU map memory into kernel and user address spaces. An example of secure module implementation can be found here: http://git.linaro.org/people/benjamin.gaignard/optee-sdp.git This code isn't yet part of the patch set because it depends on generic TEE which is still under discussion (https://lwn.net/Articles/644646/) For allocation part of SMAF code I get inspirated by Sumit Semwal work about constraint aware allocator. Benjamin Gaignard (2): create SMAF module SMAF: add CMA allocator drivers/Kconfig | 2 + drivers/Makefile | 1 + drivers/smaf/Kconfig | 11 + drivers/smaf/Makefile | 2 + drivers/smaf/smaf-cma.c | 198 ++++++++++++ drivers/smaf/smaf-core.c | 674 +++++++++++++++++++++++++++++++++++++++++ include/linux/smaf-allocator.h | 43 +++ include/linux/smaf-secure.h | 62 ++++ include/uapi/linux/smaf.h | 48 +++ 9 files changed, 1041 insertions(+) create mode 100644 drivers/smaf/Kconfig create mode 100644 drivers/smaf/Makefile create mode 100644 drivers/smaf/smaf-cma.c create mode 100644 drivers/smaf/smaf-core.c create mode 100644 include/linux/smaf-allocator.h create mode 100644 include/linux/smaf-secure.h create mode 100644 include/uapi/linux/smaf.h -- 1.9.1

1 2

[Bug 82428] New: [radeonsi,R9 270X] System lockup when using mplayer/mpv with VDPAU
by bugzilla-daemon＠freedesktop.org 17 Jun '15

17 Jun '15

https://bugs.freedesktop.org/show_bug.cgi?id=82428 Priority: medium Bug ID: 82428 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi,R9 270X] System lockup when using mplayer/mpv with VDPAU Severity: normal Classification: Unclassified OS: All Reporter: custos.mentis(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa With mesa from today's git repository I am getting hard system lockups while trying to play a movie with mplayer/mpv configured to use hardware acceleration (vdpau). I was able to bisect the commit causing those lockups. The responsible commit is 1c03a690bfc3265c7fefa7f87e69782a6672a9b2 "radeonsi: use gpu_address from r600_resource". There is no related message in the logs, since the lockup is immediate and hard reset is required. I use libdrm, glamour, mesa, and xf86-video-ati from today's git with xorg-server-1.15.0; mpv-0.3.11 with libav-9.14 and libvdpau-0.7. -- You are receiving this mail because: You are the assignee for the bug.

1 17

[RFC 0/2] drm/msm: HDMI PHY rework for MSM8x94 support
by Stephane Viau 16 Jun '15

16 Jun '15

The RFC concerns a code restructuring of the HDMI module, which mainly has two purposes: 1. architectural HDMI registers are divided in two parts: HDMI core and HDMI PHY. The HDMI Core registers are common to all chipsets sharing the MDP version (MDP5 here). On the other hand, HDMI PHY registers depend on the interface and process (28nm, 20nm, ...) being used for the same chipsets. Some chipsets (eg: msm8x94) don't require us to access HDMI PHY registers. >From a software architecture point of view, it would make sense that all HDMI PHY registers should only be accessed by (PHY) hdmi_phy_*.c files, while all HDMI Core registers are read/written by the (core) hdmi.c and hdmi_connector.c files. 2. readability Once we add msm8x94, which does not program HDMI PHY registers, it will be easier to handle the HDMI core register programming because a hdmi_phy_*.c file won't be created for this chipset. Instead of creating such a stub file or some kind of workaround, it only makes sense to bring the HDMI core register programming where it is supposed to be. To summarize, this re-structuring is to improve the code architecture, facilitate the introduction of msm8x94 support and won't change the current functionality. Stephane Viau (2): [RFC] drm/msm/hdmi: remove ->reset() from HDMI PHY drm/msm: Add support for msm8x94 drivers/gpu/drm/msm/hdmi/hdmi.c | 30 ++++++---- drivers/gpu/drm/msm/hdmi/hdmi.h | 1 - drivers/gpu/drm/msm/hdmi/hdmi_bridge.c | 8 ++- drivers/gpu/drm/msm/hdmi/hdmi_connector.c | 94 +++++++++++++++++++++++++------ drivers/gpu/drm/msm/hdmi/hdmi_phy_8960.c | 52 ----------------- drivers/gpu/drm/msm/hdmi/hdmi_phy_8x60.c | 32 ----------- drivers/gpu/drm/msm/hdmi/hdmi_phy_8x74.c | 57 ------------------- drivers/gpu/drm/msm/mdp/mdp5/mdp5_cfg.c | 73 +++++++++++++++++++++++- drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c | 8 ++- 9 files changed, 179 insertions(+), 176 deletions(-) -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project

1 2

[Bug 100001] New: Can't Change Resolution on MacBook w/ Hybrid Graphics and Nouveau
by bugzilla-daemon＠bugzilla.kernel.org 16 Jun '15

16 Jun '15

https://bugzilla.kernel.org/show_bug.cgi?id=100001 Bug ID: 100001 Summary: Can't Change Resolution on MacBook w/ Hybrid Graphics and Nouveau Product: Drivers Version: 2.5 Kernel Version: 3.16 & 3.19 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: dmrickert(a)gmail.com Regression: No When changing the resolution from the native display, the screen goes black and does not revert to the last setting. At this point, a reboot is required to fix it. I have tested on multiple Macbooks, if it does not have an NVIDIA graphics card than there is no problem. I'm booting 14.04 off of a USB stick and using the Nouveau drivers. I've seen this with both the 3.16 and 3.19 kernels. Steps to Reproduce: -On a MacBook Pro with hybrid graphics, boot into a fresh Ubuntu 14.04 installation with kernels 3.16 or 3.19. -System Settings > Displays > Pick a new resolution Also happens if you use xrandr from the command line. Additional Information: -My problem seems to be identical to this user https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1… -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

Implement GLX_EXT_buffer_age for DRI2
by Chris Wilson 16 Jun '15

16 Jun '15

In order to suport GLX_EXT_buffer_age in DRI2, we need to pass back the last swap buffer count that the back buffer was defined for. For simplicity, we can reuse an existing field in the DRI2GetBuffers reply that is not used by current drivers, the flags. Since we change the interpretation of this flag, we also declare the semantic change with a DRI2 parameter and depend upon the DDX to enable the change responsibility (which is just a matter of reviewing whether the flags field has ever been used for a non-zero value). Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=701801 This series add the core support to X, mesa and -ati/-nouveau. [dri2proto] Declare DRI2ParamXHasBufferAge [xorg 1/3] dri2: Allow GetBuffers to match any format [xorg 2/3] dri2: Pass swap-interval=0 ScheduleSwap requests to the [xorg 3/3] dri2: Reuse unused flags in GetBuffers protocol to pass [xf86-video-ati] dri2: Enable BufferAge support [xf86-video-nouveau] dri2: Enable BufferAge support [mesa 7/9] glx/dri2: Add DRI2GetParam() [mesa 8/9] glx/dri2: Move the wait after SwapBuffers into the next [mesa 9/9] glx/dri2: Implement getBufferAge

8 25

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015