dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 106901] Brightness / WIFI Key does not generate any events
by bugzilla-daemon＠bugzilla.kernel.org 15 Jan '16

15 Jan '16

1 0

[Bug 106901] Brightness / WIFI Key does not generate any events
by bugzilla-daemon＠bugzilla.kernel.org 15 Jan '16

15 Jan '16

https://bugzilla.kernel.org/show_bug.cgi?id=106901 --- Comment #26 from Roman Gruber <roman.gruber(a)gmx.at> --- uname -a; echo " ";dmesg |grep ACPI Linux ASUS-G75VW 4.4.0-gentoo_14-01-2016 #1 SMP Thu Jan 14 19:15:47 CET 2016 x86_64 Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz GenuineIntel GNU/Linux [ 0.000000] BIOS-e820: [mem 0x00000000dd6ab000-0x00000000ddcabfff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000de586000-0x00000000de805fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000de806000-0x00000000de80afff] ACPI data [ 0.000000] BIOS-e820: [mem 0x00000000de80c000-0x00000000de84efff] ACPI NVS [ 0.000000] efi: ACPI=0xde7de000 ACPI 2.0=0xde7de000 SMBIOS=0xde084398 [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI: RSDP 0x00000000DE7DE000 000024 (v02 _ASUS_) [ 0.000000] ACPI: XSDT 0x00000000DE7DE080 000084 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.000000] ACPI: FACP 0x00000000DE7EE9B8 00010C (v05 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.000000] ACPI: DSDT 0x00000000DE7DE190 010828 (v02 _ASUS_ Notebook 00000013 INTL 20091112) [ 0.000000] ACPI: FACS 0x00000000DE803080 000040 [ 0.000000] ACPI: APIC 0x00000000DE7EEAC8 000092 (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.000000] ACPI: FPDT 0x00000000DE7EEB60 000044 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.000000] ACPI: ECDT 0x00000000DE7EEBA8 0000C1 (v01 _ASUS_ Notebook 01072009 AMI. 00000005) [ 0.000000] ACPI: MCFG 0x00000000DE7EEC70 00003C (v01 _ASUS_ Notebook 01072009 MSFT 00000097) [ 0.000000] ACPI: HPET 0x00000000DE7EECB0 000038 (v01 _ASUS_ Notebook 01072009 AMI. 00000005) [ 0.000000] ACPI: SSDT 0x00000000DE7EECE8 00066E (v01 AhciR1 AhciTab1 00001000 INTL 20091112) [ 0.000000] ACPI: SSDT 0x00000000DE7EF358 00049E (v01 AhciR2 AhciTab2 00001000 INTL 20091112) [ 0.000000] ACPI: SSDT 0x00000000DE7EF7F8 00090A (v01 PmRef Cpu0Ist 00003000 INTL 20051117) [ 0.000000] ACPI: SSDT 0x00000000DE7F0108 000A92 (v01 PmRef CpuPm 00003000 INTL 20051117) [ 0.000000] ACPI: BGRT 0x00000000DE7F0BA0 000038 (v00 _ASUS_ Notebook 01072009 ASUS 00010013) [ 0.000000] ACPI: MSDM 0x00000000DE585E18 000055 (v03 _ASUS_ Notebook 00000000 ASUS 00000001) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: PM-Timer IO Port: 0x408 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000 [ 0.000031] ACPI: Core revision 20150930 [ 0.018220] ACPI: 5 ACPI AML tables successfully acquired and loaded [ 0.158269] PM: Registering ACPI NVS region [mem 0xdd6ab000-0xddcabfff] (6295552 bytes) [ 0.158430] PM: Registering ACPI NVS region [mem 0xde586000-0xde805fff] (2621440 bytes) [ 0.158502] PM: Registering ACPI NVS region [mem 0xde80c000-0xde84efff] (274432 bytes) [ 0.311679] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 0.311690] ACPI: bus type PCI registered [ 1.331723] ACPI: Added _OSI(Module Device) [ 1.331734] ACPI: Added _OSI(Processor Device) [ 1.331745] ACPI: Added _OSI(3.0 _SCP Extensions) [ 1.331755] ACPI: Added _OSI(Processor Aggregator Device) [ 1.333954] ACPI : EC: EC description table is found, configuring boot EC [ 1.333977] ACPI : EC: EC started [ 1.336121] ACPI: Executed 1 blocks of module-level executable AML code [ 1.341939] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 1.342599] ACPI: Dynamic OEM Table Load: [ 1.342618] ACPI: SSDT 0xFFFF88040E15B000 000853 (v01 PmRef Cpu0Cst 00003001 INTL 20051117) [ 1.343557] ACPI: Dynamic OEM Table Load: [ 1.343573] ACPI: SSDT 0xFFFF88040D89E400 000303 (v01 PmRef ApIst 00003000 INTL 20051117) [ 1.344377] ACPI: Dynamic OEM Table Load: [ 1.344392] ACPI: SSDT 0xFFFF88041E433E00 000119 (v01 PmRef ApCst 00003000 INTL 20051117) [ 1.347118] ACPI: Interpreter enabled [ 1.347136] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150930/hwxface-580) [ 1.347152] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150930/hwxface-580) [ 1.347180] ACPI: (supports S0 S3 S4 S5) [ 1.347190] ACPI: Using IOAPIC for interrupt routing [ 1.347238] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 1.357145] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e]) [ 1.358371] pci 0000:00:01.0: System wakeup disabled by ACPI [ 1.358626] pci 0000:00:14.0: System wakeup disabled by ACPI [ 1.359092] pci 0000:00:1a.0: System wakeup disabled by ACPI [ 1.359322] pci 0000:00:1b.0: System wakeup disabled by ACPI [ 1.359539] pci 0000:00:1c.0: System wakeup disabled by ACPI [ 1.359956] pci 0000:00:1c.3: System wakeup disabled by ACPI [ 1.360202] pci 0000:00:1d.0: System wakeup disabled by ACPI [ 1.361589] pci 0000:03:00.0: System wakeup disabled by ACPI [ 1.361966] pci 0000:04:00.0: System wakeup disabled by ACPI [ 1.362801] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. [ 1.362900] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 12) *0, disabled. [ 1.362996] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 12) *0, disabled. [ 1.363090] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 12) *0, disabled. [ 1.363183] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled. [ 1.363278] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled. [ 1.363370] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 12) *0, disabled. [ 1.363463] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 12) *0, disabled. [ 1.363681] ACPI: Enabled 3 GPEs in block 00 to 3F [ 1.363773] ACPI : EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62 [ 1.364150] ACPI: bus type USB registered [ 1.364737] PCI: Using ACPI for IRQ routing [ 1.371343] pnp: PnP ACPI init [ 1.371478] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active) [ 1.371739] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) [ 1.371775] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active) [ 1.371862] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) [ 1.371946] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) [ 1.372033] pnp 00:05: Plug and Play ACPI device, IDs SYN0a19 SYN0a00 SYN0002 PNP0f13 (active) [ 1.372088] pnp 00:06: Plug and Play ACPI device, IDs ATK3001 PNP030b (active) [ 1.372453] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) [ 1.372659] pnp: PnP ACPI: found 8 devices [ 2.121700] ACPI: AC Adapter [AC0] (on-line) [ 2.123472] ACPI: Lid Switch [LID] [ 2.126242] ACPI: Sleep Button [SLPB] [ 2.129171] ACPI: Power Button [PWRF] [ 2.130920] ACPI: Video Device [GFX0] (multi-head: yes rom: yes post: no) [ 2.624774] ACPI: Thermal Zone [THRM] (41 C) [ 2.637846] ACPI: Battery Slot [BAT0] (battery present) [ 2.643427] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000044F (\GPIS) (20150930/utaddress-254) [ 2.644992] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150930/utaddress-254) [ 2.646543] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 2.648102] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20150930/utaddress-254) [ 2.649760] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20150930/utaddress-254) [ 2.651369] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 2.652982] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20150930/utaddress-254) [ 2.654663] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20150930/utaddress-254) [ 2.656323] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 2.657987] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20150930/utaddress-254) [ 2.659737] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20150930/utaddress-254) [ 2.661451] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 2.818844] ACPI Warning: SystemIO range 0x000000000000F000-0x000000000000F01F conflicts with OpRegion 0x000000000000F000-0x000000000000F00F (\SMB0) (20150930/utaddress-254) [ 2.820497] ACPI Warning: SystemIO range 0x000000000000F000-0x000000000000F01F conflicts with OpRegion 0x000000000000F000-0x000000000000F00F (\_SB_.PCI0.SBUS.SMBI) (20150930/utaddress-254) [ 2.822123] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 3.090325] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 3.090357] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded [ 3.090359] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 3.091893] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 3.092032] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded [ 3.092034] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 3.092060] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded [ 3.092062] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 3.094891] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded [ 3.094893] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 3.095557] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 3.095601] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded [ 3.095603] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 3.108406] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 3.108448] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded [ 3.108450] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 12.606217] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 12.606268] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 12.606300] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 12.606330] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 12.606375] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 12.606405] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 12.606435] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 12.606468] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 12.606539] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 12.938291] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.079333] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.079387] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.079420] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.079451] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.079496] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.079526] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.079557] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.079590] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.079661] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) [ 20.184604] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95) -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

[PATCH] drm: nouveau: fix nouveau_debugfs_init prototype
by Arnd Bergmann 15 Jan '16

15 Jan '16

The new debugfs initialization code fails to build when CONFIG_DEBUG_FS is disabled: In file included from /git/arm-soc/drivers/gpu/drm/nouveau/nouveau_drm.c:57:0: drivers/gpu/drm/nouveau/nouveau_debugfs.h: In function 'nouveau_debugfs_init': drivers/gpu/drm/nouveau/nouveau_debugfs.h:37:29: error: parameter name omitted nouveau_debugfs_init(struct nouveau_drm *) This fixes the prototypes so we can build it again. Signed-off-by: Arnd Bergmann <arnd(a)arndb.de> Fixes: b126a200e9db ("drm/nouveau/debugfs: we need a ctrl object for debugfs") --- This broke when the nouveau patches got merged into drm-next on Monday. Found on ARM randconfig builds. diff --git a/drivers/gpu/drm/nouveau/nouveau_debugfs.h b/drivers/gpu/drm/nouveau/nouveau_debugfs.h index 52c7161297d7..b8c03ff5bf05 100644 --- a/drivers/gpu/drm/nouveau/nouveau_debugfs.h +++ b/drivers/gpu/drm/nouveau/nouveau_debugfs.h @@ -34,13 +34,13 @@ nouveau_drm_debugfs_cleanup(struct drm_minor *minor) } static inline int -nouveau_debugfs_init(struct nouveau_drm *) +nouveau_debugfs_init(struct nouveau_drm *drm) { return 0; } static inline void -nouveau_debugfs_fini(struct nouveau_drm *) +nouveau_debugfs_fini(struct nouveau_drm *drm) { }

3 4

[PATCH v3 0/3] drm/exynos: introduce generic zpos property
by Marek Szyprowski 15 Jan '16

15 Jan '16

Hello all, This patch series is a continuation of rework of blending support in Exynos DRM driver. Some background can be found here: http://www.spinics.net/lists/dri-devel/msg96969.html Daniel Vetter suggested that zpos property should be made generic, with well-defined semantics. This patchset is my proposal for such generic zpos property: - added zpos properties to drm core and plane state structures, - added helpers for normalizing zpos properties of given set of planes, - well defined semantics: planes are sorted by zpos values and then plane id value if zpos equals. Patches are based on top of latest exynos-drm-next branch. Best regards Marek Szyprowski Samsung R&D Institute Poland Changelog: v3: - on request of Daniel Vetter, moved all normalization process to DRM core, drivers can simply use plane_state->normalized_zpos in their atomic_check/update callbacks with no additional changes needed - updated documentation v2: http://www.spinics.net/lists/dri-devel/msg98093.html - dropped 2 fixes for Exynos DRM, which got merged in meantime - added more comments and kernel docs for core functions as suggested by Daniel Vetter - reworked initialization of zpos properties (moved assiging property class to common code), now the code in the driver is even simpler - while reworking of intialization of zpos property code, did the same change to generic rotation property v1: http://www.spinics.net/lists/dri-devel/msg97709.html - initial version Patch summary: Marek Szyprowski (3): drm: add generic zpos property drm/exynos: use generic code for managing zpos plane property drm: simplify initialization of rotation property Documentation/DocBook/gpu.tmpl | 14 ++- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c | 10 +- drivers/gpu/drm/drm_atomic.c | 4 + drivers/gpu/drm/drm_atomic_helper.c | 116 ++++++++++++++++++++++++ drivers/gpu/drm/drm_crtc.c | 82 +++++++++++++++-- drivers/gpu/drm/exynos/exynos_drm_drv.h | 2 - drivers/gpu/drm/exynos/exynos_drm_plane.c | 66 +++----------- drivers/gpu/drm/exynos/exynos_mixer.c | 6 +- drivers/gpu/drm/i915/intel_display.c | 6 +- drivers/gpu/drm/msm/mdp/mdp5/mdp5_plane.c | 3 +- drivers/gpu/drm/omapdrm/omap_drv.c | 3 +- include/drm/drm_crtc.h | 18 +++- 12 files changed, 250 insertions(+), 80 deletions(-) -- 1.9.2

4 9

[PATCH 0/5] Better markup for GPU DocBook
by Daniel Vetter 15 Jan '16

15 Jan '16

Hi all, As you might know the markup improvements have been discussed at kernel summit: https://lwn.net/Articles/662930/ Unfortunately it died in a bikeshed fest due to an alliance of people who think docs are useless and you should just read code and others who didn't know how to build the kerneldoc into something pretty. Oh well. But I still want this, and Dave Airlie is ok with using it for drm kerneldoc as long as I maintain the support. Plan is to merge the first patch to adjust gpu.tmpl into drm properly, and keep everything else in topic/kerneldoc at git://anongit.freedesktop.org/drm-intel topic/kerneldoc If you want to build pretty docs just install asciidoc and base your drm documentation patches on top of drm-intel-nightly. That tree also includes all of Dave's tree. Alternatively pull in the above topic branch. Note that asciidoc is strictly optional, but without it the docbook will look a bit bad since beyond paragraphs there won't be any additional formatting (like tables, quoting for sourcecode snippets or lists). Intel also has an autobuilder that pushes latest drm-intel-nightly docs to http://dri.freedesktop.org/docs/drm/ Cheers, Daniel Daniel Vetter (2): scripts/kernel-doc: Use asciidoc instead of markdown drm: Enable markdown^Wasciidoc for gpu.tmpl Danilo Cesar Lemes de Paula (3): drm/doc: Convert to markdown scripts/kernel-doc: Adding infrastructure for markdown support scripts/kernel-doc: Improve Markdown results Documentation/DocBook/Makefile | 25 +++++--- Documentation/DocBook/gpu.tmpl | 86 -------------------------- drivers/gpu/drm/drm_modes.c | 12 ++-- drivers/gpu/drm/drm_modeset_lock.c | 14 ++--- drivers/gpu/drm/drm_prime.c | 16 ++--- drivers/gpu/drm/i915/i915_reg.h | 48 +++++++-------- scripts/docproc.c | 54 ++++++++++++----- scripts/kernel-doc | 120 ++++++++++++++++++++++++++++++++----- 8 files changed, 203 insertions(+), 172 deletions(-) -- 2.5.1

5 19

[PULL] drm-intel-next-fixes
by Jani Nikula 14 Jan '16

14 Jan '16

Hi Dave - Our first bag of fixes for drm-next/v4.5. BR, Jani. The following changes since commit 7447a2b221cd4df3960e82478a4ee29312589611: drm/i915: Update DRIVER_DATE to 20151218 (2015-12-18 20:26:17 +0100) are available in the git repository at: git://anongit.freedesktop.org/drm-intel tags/drm-intel-next-fixes-2016-01-14 for you to fetch changes up to 48ea1e32c39db94c59b63580b965222c7782112f: drm/i915/gen9: Set PIN_ZONE_4G end to 4GB - 1 page (2016-01-13 10:50:55 +0200) ---------------------------------------------------------------- Chris Wilson (2): drm/i915: Move Braswell stop_machine GGTT insertion workaround drm/i915: Restore inhibiting the load of the default context Daniel Vetter (1): drm/i915: Tune down rpm wakelock debug checks Jani Nikula (1): drm/i915: shut up gen8+ SDE irq dmesg noise, again Lyude (1): drm/i915: intel_hpd_init(): Fix suspend/resume reprobing Maarten Lankhorst (1): drm/i915: Widen return value for reservation_object_wait_timeout_rcu to long. Michał Winiarski (1): drm/i915: Avoid writing relocs with addresses in non-canonical form Michel Thierry (1): drm/i915/gen9: Set PIN_ZONE_4G end to 4GB - 1 page drivers/gpu/drm/i915/i915_gem.c | 2 +- drivers/gpu/drm/i915/i915_gem_context.c | 6 +++- drivers/gpu/drm/i915/i915_gem_execbuffer.c | 52 +++++++++++++++++++++++++++--- drivers/gpu/drm/i915/i915_gem_gtt.c | 50 +++++++++++++++------------- drivers/gpu/drm/i915/i915_irq.c | 10 ++++-- drivers/gpu/drm/i915/intel_display.c | 14 ++++---- drivers/gpu/drm/i915/intel_drv.h | 6 ++-- drivers/gpu/drm/i915/intel_hotplug.c | 9 ++++-- 8 files changed, 108 insertions(+), 41 deletions(-) -- Jani Nikula, Intel Open Source Technology Center

1 0

[PATCH] drm: Do not set connector->encoder in drivers
by Thierry Reding 14 Jan '16

14 Jan '16

From: Thierry Reding <treding(a)nvidia.com> An encoder is associated with a connector by the DRM core as a result of setting up a configuration. Drivers using the atomic or legacy helpers should never set up this link, even if it is a static one. While at it, try to catch this kind of error in the future by adding a WARN_ON() in drm_mode_connector_attach_encoder(). Note that this doesn't cover all the cases, since drivers could set this up after attaching. Drivers that use the atomic helpers will get a warning later on, though, so hopefully the two combined cover enough to help people avoid this in the future. Cc: Russell King <rmk+kernel(a)arm.linux.org.uk> Cc: Philipp Zabel <p.zabel(a)pengutronix.de> Cc: Laurent Pinchart <laurent.pinchart(a)ideasonboard.com> Cc: Liviu Dudau <Liviu.Dudau(a)arm.com> Cc: Mark yao <mark.yao(a)rock-chips.com> Signed-off-by: Thierry Reding <treding(a)nvidia.com> --- Daniel, I didn't add your Reviewed-by because I included two more fixes for the same errors in the i.MX and shmobile drivers. But I suspect that you will want to pick this up into drm/misc anyway. drivers/gpu/drm/bridge/dw_hdmi.c | 2 -- drivers/gpu/drm/drm_crtc.c | 14 ++++++++++++++ drivers/gpu/drm/i2c/tda998x_drv.c | 1 - drivers/gpu/drm/imx/parallel-display.c | 2 -- drivers/gpu/drm/shmobile/shmob_drm_crtc.c | 2 -- 5 files changed, 14 insertions(+), 7 deletions(-) diff --git a/drivers/gpu/drm/bridge/dw_hdmi.c b/drivers/gpu/drm/bridge/dw_hdmi.c index 56de9f1c95fc..ffef392ccc13 100644 --- a/drivers/gpu/drm/bridge/dw_hdmi.c +++ b/drivers/gpu/drm/bridge/dw_hdmi.c @@ -1648,8 +1648,6 @@ static int dw_hdmi_register(struct drm_device *drm, struct dw_hdmi *hdmi) drm_connector_init(drm, &hdmi->connector, &dw_hdmi_connector_funcs, DRM_MODE_CONNECTOR_HDMIA); - hdmi->connector.encoder = encoder; - drm_mode_connector_attach_encoder(&hdmi->connector, encoder); return 0; diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c index 24c5434abd1c..bc0693c63ca4 100644 --- a/drivers/gpu/drm/drm_crtc.c +++ b/drivers/gpu/drm/drm_crtc.c @@ -4983,6 +4983,20 @@ int drm_mode_connector_attach_encoder(struct drm_connector *connector, { int i; + /* + * In the past, drivers have attempted to model the static association + * of connector to encoder in simple connector/encoder devices using a + * direct assignment of connector->encoder = encoder. This connection + * is a logical one and the responsibility of the core, so drivers are + * expected not to mess with this. + * + * Note that the error return should've been enough here, but a large + * majority of drivers ignores the return value, so add in a big WARN + * to get people's attention. + */ + if (WARN_ON(connector->encoder)) + return -EINVAL; + for (i = 0; i < DRM_CONNECTOR_MAX_ENCODER; i++) { if (connector->encoder_ids[i] == 0) { connector->encoder_ids[i] = encoder->base.id; diff --git a/drivers/gpu/drm/i2c/tda998x_drv.c b/drivers/gpu/drm/i2c/tda998x_drv.c index 896b6aaf8c4d..8b0a402190eb 100644 --- a/drivers/gpu/drm/i2c/tda998x_drv.c +++ b/drivers/gpu/drm/i2c/tda998x_drv.c @@ -1453,7 +1453,6 @@ static int tda998x_bind(struct device *dev, struct device *master, void *data) if (ret) goto err_sysfs; - priv->connector.encoder = &priv->encoder; drm_mode_connector_attach_encoder(&priv->connector, &priv->encoder); return 0; diff --git a/drivers/gpu/drm/imx/parallel-display.c b/drivers/gpu/drm/imx/parallel-display.c index b4deb9cf9d71..57b78226e392 100644 --- a/drivers/gpu/drm/imx/parallel-display.c +++ b/drivers/gpu/drm/imx/parallel-display.c @@ -200,8 +200,6 @@ static int imx_pd_register(struct drm_device *drm, drm_mode_connector_attach_encoder(&imxpd->connector, &imxpd->encoder); - imxpd->connector.encoder = &imxpd->encoder; - return 0; } diff --git a/drivers/gpu/drm/shmobile/shmob_drm_crtc.c b/drivers/gpu/drm/shmobile/shmob_drm_crtc.c index e9272b0a8592..cb72b35d85d1 100644 --- a/drivers/gpu/drm/shmobile/shmob_drm_crtc.c +++ b/drivers/gpu/drm/shmobile/shmob_drm_crtc.c @@ -739,8 +739,6 @@ int shmob_drm_connector_create(struct shmob_drm_device *sdev, if (ret < 0) goto err_backlight; - connector->encoder = encoder; - drm_helper_connector_dpms(connector, DRM_MODE_DPMS_OFF); drm_object_property_set_value(&connector->base, sdev->ddev->mode_config.dpms_property, DRM_MODE_DPMS_OFF); -- 2.5.0

6 9

[PATCH 00/21] drm_event cleanup
by Daniel Vetter 14 Jan '16

14 Jan '16

Hi all, This patch series is inspired by a WIP patch from Rob Clark to consolidate the drm_event handling a bit. I've went a bit further and also moved the pending event handling and unlinking into the core, which allows us to nuke a bunch of code from drivers who all copypasted this themselves. Plus fix up all the others who failed to handle this correctly. Net -500 lines of code, plus kerneldoc for drm_fops.c and all the new functions as bonus. Comments and review highly welcome as usual. Cheers, Daniel Daniel Vetter (21): drm: kerneldoc for drm_fops.c drm: Add functions to setup/tear down drm_events. drm/exynos: Use the new event init/free functions drm/vmwgfx: Use the new event init/free functions drm: Create drm_send_event helpers drm/fsl: Remove preclose hook drm/armada: Remove NULL open/pre/postclose hooks drm/gma500: Remove empty preclose hook drm: Clean up pending events in the core drm/i915: Nuke intel_modeset_preclose drm/atmel: Nuke preclose drm/exynos: Remove event cancelling from postclose drm/imx: Unconfuse preclose logic drm/msm: Nuke preclose hooks drm/omap: Nuke close hooks drm/rcar: Nuke preclose hook drm/shmob: Nuke preclose hook drm/tegra: Stop cancelling page flip events drm/tilcdc: Nuke preclose hook drm/vc4: Nuke preclose hook drm/vmwgfx: Nuke preclose hook Documentation/DocBook/gpu.tmpl | 48 +---- drivers/gpu/drm/armada/armada_drv.c | 3 - drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 18 -- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 10 - drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.h | 3 - drivers/gpu/drm/drm_atomic.c | 44 ++--- drivers/gpu/drm/drm_crtc.c | 36 +--- drivers/gpu/drm/drm_fops.c | 259 ++++++++++++++++++++++--- drivers/gpu/drm/drm_irq.c | 7 +- drivers/gpu/drm/exynos/exynos_drm_drv.c | 14 -- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 36 +--- drivers/gpu/drm/exynos/exynos_drm_ipp.c | 28 +-- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 5 - drivers/gpu/drm/gma500/psb_drv.c | 9 - drivers/gpu/drm/i915/i915_dma.c | 2 - drivers/gpu/drm/i915/intel_display.c | 21 -- drivers/gpu/drm/i915/intel_drv.h | 1 - drivers/gpu/drm/imx/imx-drm-core.c | 13 -- drivers/gpu/drm/imx/ipuv3-crtc.c | 4 - drivers/gpu/drm/msm/mdp/mdp4/mdp4_crtc.c | 7 - drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c | 11 -- drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.h | 1 - drivers/gpu/drm/msm/mdp/mdp5/mdp5_crtc.c | 6 - drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c | 11 -- drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.h | 1 - drivers/gpu/drm/omapdrm/omap_drv.c | 29 --- drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 20 -- drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 2 - drivers/gpu/drm/rcar-du/rcar_du_drv.c | 10 - drivers/gpu/drm/shmobile/shmob_drm_crtc.c | 20 -- drivers/gpu/drm/shmobile/shmob_drm_crtc.h | 2 - drivers/gpu/drm/shmobile/shmob_drm_drv.c | 8 - drivers/gpu/drm/tegra/dc.c | 17 -- drivers/gpu/drm/tegra/drm.c | 3 - drivers/gpu/drm/tegra/drm.h | 1 - drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 20 -- drivers/gpu/drm/tilcdc/tilcdc_drv.c | 8 - drivers/gpu/drm/tilcdc/tilcdc_drv.h | 1 - drivers/gpu/drm/vc4/vc4_crtc.c | 20 -- drivers/gpu/drm/vc4/vc4_drv.c | 10 - drivers/gpu/drm/vc4/vc4_drv.h | 1 - drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 10 - drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 73 +------ drivers/gpu/drm/vmwgfx/vmwgfx_fence.h | 2 - include/drm/drmP.h | 26 ++- 45 files changed, 299 insertions(+), 582 deletions(-) -- 2.6.4

7 47

[Bug 91865] [r600g] GPU hang in 'gsraytrace' - NI/Turks (6670)
by bugzilla-daemon＠freedesktop.org 14 Jan '16

14 Jan '16

https://bugs.freedesktop.org/show_bug.cgi?id=91865 --- Comment #10 from Dieter Nützel <Dieter(a)nuetzel-hh.de> --- OK, is this SOLVED by 'accident'? For RV730 GPU hang (Bug 83319) the above identified commit do NOT solve the hang. (Bug is updated, now.) The observed issues with R600_DEBUG=nosb for all three 'raytrace' variants (vsraytrace/fsraytrace/gsraytrace) stays. latest: Mesa 11.2.0-devel (git-6470435) I'll open a new ticket for this. -- You are receiving this mail because: You are the assignee for the bug.

1 0

re: OMAPDSS: panel-sharp-ls037v7dw01: update to use gpiod
by Dan Carpenter 14 Jan '16

14 Jan '16

[ It's weird that I'm just now getting this warning from 2014... Oh well, looks legit. -dan ] Hello Tony Lindgren, The patch 9522f9fe86f9: "OMAPDSS: panel-sharp-ls037v7dw01: update to use gpiod" from Apr 28, 2014, leads to the following static checker warning: drivers/gpu/drm/omapdrm/displays/panel-sharp-ls037v7dw01.c:213 sharp_ls_get_gpio() warn: 'gd' isn't an ERR_PTR drivers/gpu/drm/omapdrm/displays/panel-sharp-ls037v7dw01.c 200 static int sharp_ls_get_gpio(struct device *dev, int gpio, unsigned long flags, 201 char *desc, struct gpio_desc **gpiod) 202 { 203 struct gpio_desc *gd; 204 int r; 205 206 *gpiod = NULL; 207 208 r = devm_gpio_request_one(dev, gpio, flags, desc); 209 if (r) 210 return r == -ENOENT ? 0 : r; 211 212 gd = gpio_to_desc(gpio); 213 if (IS_ERR(gd)) 214 return PTR_ERR(gd) == -ENOENT ? 0 : PTR_ERR(gd); ^^^^^^^^^^^^^^^^^^^^^^ gd can be an ERR_PTR if gpio_to_desc is defined out but it's never -ENOENT. 215 216 *gpiod = gd; 217 return 0; 218 } regards, dan carpenter

3 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016