dri-devel March 2014

dri-devel@lists.freedesktop.org

144 participants
926 discussions

HDCP compliance of Linux Intel HD graphics drivers
by Subodh Chiwate 14 Mar '14

14 Mar '14

Hi, I am working on a system with following configuration. 1) I need help in finding if the Linux drivers support HDCP. I need HDCP enabled. 2) Any information regarding understanding graphics drivers overview in linux environments is welcome. 3) any suggestion to test/debug HDCP compliance of linux drivers. *System Specs:* Fedora18/ Debian7.4 Intel(R) Core(TM) i7-3610QE CPU @ 2.30GHz, Intel HD Graphics 4000 *-- lsmod :* i915 crc32c_intel i2c_algo_bit drm_kms_helper ghash_clmulni_intel drm i915,drm_kms_helper i2c_core drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit video i915 *-- libva installed on machine* [ufouser@localhost ~]$ yum list installed | grep libva libva.x86_64 1.1.1-2.fc18 @updates libva-devel.x86_64 1.1.1-2.fc18 @updates libva-intel-driver.x86_64 1.0.20-1.fc18 @rpmfusion-free-updates libva-utils.x86_64 1.1.1-2.fc18 @updates Thanks in advance. -- Regards Subodh

2 2

[Q] tilcdc: cannot allocate buffer
by Robert Kuhn 14 Mar '14

14 Mar '14

Hi, using the code from https://github.com/dvdhrm/docs/blob/master/drm-howto/modeset-vsync.c on my beaglebone black I get sometimes this error: [ 7772.673057] tilcdc 4830e000.lcdc: failed to allocate buffer with size 5242880 [ 7777.663102] tilcdc 4830e000.lcdc: failed to allocate buffer with size 5242880 [ 7783.892790] tilcdc 4830e000.lcdc: failed to allocate buffer with size 5242880 When I restart the programm usually everything works as expected. What is the couse of this error?

2 1

[PATCH 1/2] drm/panel: use gpiod interface for enable GPIO
by Alexandre Courbot 14 Mar '14

14 Mar '14

Use the new GPIO descriptor interface to handle the panel's enable GPIO. This considerably simplifies the code. Signed-off-by: Alexandre Courbot <acourbot(a)nvidia.com> --- drivers/gpu/drm/panel/panel-simple.c | 69 ++++++++++-------------------------- 1 file changed, 18 insertions(+), 51 deletions(-) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index 94cbf06..d1cabfa 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -22,9 +22,8 @@ */ #include <linux/backlight.h> -#include <linux/gpio.h> +#include <linux/gpio/consumer.h> #include <linux/module.h> -#include <linux/of_gpio.h> #include <linux/of_platform.h> #include <linux/platform_device.h> #include <linux/regulator/consumer.h> @@ -44,9 +43,6 @@ struct panel_desc { } size; }; -/* TODO: convert to gpiod_*() API once it's been merged */ -#define GPIO_ACTIVE_LOW (1 << 0) - struct panel_simple { struct drm_panel base; bool enabled; @@ -57,8 +53,7 @@ struct panel_simple { struct regulator *supply; struct i2c_adapter *ddc; - unsigned long enable_gpio_flags; - int enable_gpio; + struct gpio_desc *enable_gpio; }; static inline struct panel_simple *to_panel_simple(struct drm_panel *panel) @@ -110,12 +105,8 @@ static int panel_simple_disable(struct drm_panel *panel) backlight_update_status(p->backlight); } - if (gpio_is_valid(p->enable_gpio)) { - if (p->enable_gpio_flags & GPIO_ACTIVE_LOW) - gpio_set_value(p->enable_gpio, 1); - else - gpio_set_value(p->enable_gpio, 0); - } + if (p->enable_gpio) + gpiod_set_value(p->enable_gpio, 0); regulator_disable(p->supply); p->enabled = false; @@ -137,12 +128,8 @@ static int panel_simple_enable(struct drm_panel *panel) return err; } - if (gpio_is_valid(p->enable_gpio)) { - if (p->enable_gpio_flags & GPIO_ACTIVE_LOW) - gpio_set_value(p->enable_gpio, 0); - else - gpio_set_value(p->enable_gpio, 1); - } + if (p->enable_gpio) + gpiod_set_value(p->enable_gpio, 1); if (p->backlight) { p->backlight->props.power = FB_BLANK_UNBLANK; @@ -185,7 +172,6 @@ static int panel_simple_probe(struct device *dev, const struct panel_desc *desc) { struct device_node *backlight, *ddc; struct panel_simple *panel; - enum of_gpio_flags flags; int err; panel = devm_kzalloc(dev, sizeof(*panel), GFP_KERNEL); @@ -199,30 +185,19 @@ static int panel_simple_probe(struct device *dev, const struct panel_desc *desc) if (IS_ERR(panel->supply)) return PTR_ERR(panel->supply); - panel->enable_gpio = of_get_named_gpio_flags(dev->of_node, - "enable-gpios", 0, - &flags); - if (gpio_is_valid(panel->enable_gpio)) { - unsigned int value; - - if (flags & OF_GPIO_ACTIVE_LOW) - panel->enable_gpio_flags |= GPIO_ACTIVE_LOW; - - err = gpio_request(panel->enable_gpio, "enable"); + panel->enable_gpio = devm_gpiod_get(dev, "enable"); + if (!IS_ERR(panel->enable_gpio)) { + err = gpiod_direction_output(panel->enable_gpio, 0); if (err < 0) { - dev_err(dev, "failed to request GPIO#%u: %d\n", - panel->enable_gpio, err); + dev_err(dev, "failed to setup enable GPIO: %d\n", err); return err; } - - value = (panel->enable_gpio_flags & GPIO_ACTIVE_LOW) != 0; - - err = gpio_direction_output(panel->enable_gpio, value); - if (err < 0) { - dev_err(dev, "failed to setup GPIO%u: %d\n", - panel->enable_gpio, err); - goto free_gpio; - } + } else if (PTR_ERR(panel->enable_gpio) == -ENOENT) { + panel->enable_gpio = NULL; + } else { + err = PTR_ERR(panel->enable_gpio); + dev_err(dev, "failed to request enable GPIO: %d\n", err); + return err; } backlight = of_parse_phandle(dev->of_node, "backlight", 0); @@ -230,10 +205,8 @@ static int panel_simple_probe(struct device *dev, const struct panel_desc *desc) panel->backlight = of_find_backlight_by_node(backlight); of_node_put(backlight); - if (!panel->backlight) { - err = -EPROBE_DEFER; - goto free_gpio; - } + if (!panel->backlight) + return -EPROBE_DEFER; } ddc = of_parse_phandle(dev->of_node, "ddc-i2c-bus", 0); @@ -265,9 +238,6 @@ free_ddc: free_backlight: if (panel->backlight) put_device(&panel->backlight->dev); -free_gpio: - if (gpio_is_valid(panel->enable_gpio)) - gpio_free(panel->enable_gpio); return err; } @@ -287,9 +257,6 @@ static int panel_simple_remove(struct device *dev) if (panel->backlight) put_device(&panel->backlight->dev); - if (gpio_is_valid(panel->enable_gpio)) - gpio_free(panel->enable_gpio); - regulator_disable(panel->supply); return 0; -- 1.9.0

2 2

[Bug 76054] New: Adobe flash player crashed, because of the function "pipe_context" in si_pipe.c
by bugzilla-daemon＠freedesktop.org 14 Mar '14

14 Mar '14

https://bugs.freedesktop.org/show_bug.cgi?id=76054 Priority: medium Bug ID: 76054 Assignee: dri-devel(a)lists.freedesktop.org Summary: Adobe flash player crashed, because of the function "pipe_context" in si_pipe.c Severity: normal Classification: Unclassified OS: Linux (All) Reporter: chen.bill.bill(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.0 Component: Drivers/Gallium/radeonsi Product: Mesa My video card is ATI hd6470m [Radeon HD 6400M/7400M Series]. The Adobe flash player was running well before mesaLib-10.0.0. After I updated to 10.0 or 10.1, the Adobe flash player is always crashed. I think the problem is at the function called "pipe_context", which is in the file gallium/drivers/radeonsi/si_pipe.c Here are some tips to reappear this bug as I meet. 1, Open a terminal, run "firefox -safe-mode". 2, Open a web page with flash player plugin, if it is a video site like youtube, it is better. (For me, I use http://www.youku.com) 3, Flash player plugin will crash. 4, Goto the terminal, some information is printed. Notice that as below. "si_pipe.c: Unsupported chip class 6." My environment, hd6470m, Arch Linux x86_64, i3_wm /etc/adobe/mms.cfg: EnableLinuxHWVideoDecode=1 This bug is on the version 10.0, 10.1 and git master branch(2014-3-11). -- You are receiving this mail because: You are the assignee for the bug.

1 3

[git pull] drm fixes
by Dave Airlie 14 Mar '14

14 Mar '14

Hi Linus, pretty minor set of fixes for radeon, ttm and vmwgfx, ttm ones are a regression and an oops seen on server chipsets. Dave. The following changes since commit fa389e220254c69ffae0d403eac4146171062d08: Linux 3.14-rc6 (2014-03-09 19:41:57 -0700) are available in the git repository at: git://people.freedesktop.org/~airlied/linux drm-fixes for you to fetch changes up to f042cc4a607d675452134884c26e8d0d395dd979: Merge tag 'ttm-fixes-3.14-2014-03-12' of git://people.freedesktop.org/~thomash/linux into drm-fixes (2014-03-13 17:31:24 +1000) ---------------------------------------------------------------- Alex Deucher (4): drm/radeon: fix runpm disabling on non-PX harder drm/radeon/cik: properly set sdma ring status on disable drm/radeon/cik: stop the sdma engines in the enable() function drm/radeon/cik: properly set compute ring status on disable Dave Airlie (3): Merge tag 'vmwgfx-fixes-3.14-2014-03-13' of git://people.freedesktop.org/~thomash/linux into drm-fixes Merge branch 'drm-fixes-3.14' of git://people.freedesktop.org/~agd5f/linux into drm-fixes Merge tag 'ttm-fixes-3.14-2014-03-12' of git://people.freedesktop.org/~thomash/linux into drm-fixes Rob Clark (1): drm/ttm: don't oops if no invalidate_caches() Thomas Hellstrom (2): drm/ttm: Work around performance regression with VM_PFNMAP drm/vmwgfx: Fix a surface reference corner-case in legacy emulation mode drivers/gpu/drm/radeon/cik.c | 5 ++++- drivers/gpu/drm/radeon/cik_sdma.c | 14 +++++++------- drivers/gpu/drm/radeon/radeon_kms.c | 10 +++++++++- drivers/gpu/drm/ttm/ttm_bo.c | 8 +++++--- drivers/gpu/drm/ttm/ttm_bo_vm.c | 12 +++++++----- drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 18 ++++++++++++++++++ 6 files changed, 50 insertions(+), 17 deletions(-)

1 0

nouveau_fan_update: possible circular locking dependency detected
by Marcin Slusarz 13 Mar '14

13 Mar '14

[ 326.168487] ====================================================== [ 326.168491] [ INFO: possible circular locking dependency detected ] [ 326.168496] 3.13.6 #1270 Not tainted [ 326.168500] ------------------------------------------------------- [ 326.168504] ldconfig/22297 is trying to acquire lock: [ 326.168507] (&(&priv->fan->lock)->rlock){-.-...}, at: [<ffffffffa00d5363>] nouveau_fan_update+0xeb/0x252 [nouveau] [ 326.168551] but task is already holding lock: [ 326.168555] (&(&priv->sensor.alarm_program_lock)->rlock){-.-...}, at: [<ffffffffa00d6a8a>] alarm_timer_callback+0xf1/0x179 [nouveau] [ 326.168587] which lock already depends on the new lock. [ 326.168592] the existing dependency chain (in reverse order) is: [ 326.168596] -> #1 (&(&priv->sensor.alarm_program_lock)->rlock){-.-...}: [ 326.168606] [<ffffffff900a5656>] lock_acquire+0xce/0x117 [ 326.168615] [<ffffffff905a367e>] _raw_spin_lock_irqsave+0x3f/0x51 [ 326.168623] [<ffffffffa00d6a8a>] alarm_timer_callback+0xf1/0x179 [nouveau] [ 326.168651] [<ffffffffa00da895>] nv04_timer_alarm_trigger+0x1b1/0x1cb [nouveau] [ 326.168679] [<ffffffffa00daaa0>] nv04_timer_alarm+0xb5/0xbe [nouveau] [ 326.168708] [<ffffffffa00d54ac>] nouveau_fan_update+0x234/0x252 [nouveau] [ 326.168735] [<ffffffffa00d54df>] nouveau_fan_alarm+0x15/0x17 [nouveau] [ 326.168763] [<ffffffffa00da895>] nv04_timer_alarm_trigger+0x1b1/0x1cb [nouveau] [ 326.168790] [<ffffffffa00da90a>] nv04_timer_intr+0x5b/0x13c [nouveau] [ 326.168817] [<ffffffffa00d0e9b>] nouveau_mc_intr+0x2e2/0x3b1 [nouveau] [ 326.168838] [<ffffffff900ad359>] handle_irq_event_percpu+0x5c/0x1dc [ 326.168846] [<ffffffff900ad515>] handle_irq_event+0x3c/0x5c [ 326.168852] [<ffffffff900afa5e>] handle_edge_irq+0xc4/0xeb [ 326.168860] [<ffffffff9003a828>] handle_irq+0x120/0x12d [ 326.168868] [<ffffffff9003a2f8>] do_IRQ+0x48/0xaf [ 326.168873] [<ffffffff905a41ef>] ret_from_intr+0x0/0x13 [ 326.168881] [<ffffffff90040ea2>] arch_cpu_idle+0x13/0x1d [ 326.168887] [<ffffffff900acb2e>] cpu_startup_entry+0x140/0x218 [ 326.168895] [<ffffffff9005b0a0>] start_secondary+0x1bf/0x1c4 [ 326.168902] -> #0 (&(&priv->fan->lock)->rlock){-.-...}: [ 326.168913] [<ffffffff900a49cc>] __lock_acquire+0x10be/0x182b [ 326.168920] [<ffffffff900a5656>] lock_acquire+0xce/0x117 [ 326.168924] [<ffffffff905a367e>] _raw_spin_lock_irqsave+0x3f/0x51 [ 326.168931] [<ffffffffa00d5363>] nouveau_fan_update+0xeb/0x252 [nouveau] [ 326.168958] [<ffffffffa00d5508>] nouveau_therm_fan_set+0x14/0x16 [nouveau] [ 326.168984] [<ffffffffa00d4c6b>] nouveau_therm_update+0x303/0x312 [nouveau] [ 326.169011] [<ffffffffa00d4c8d>] nouveau_therm_alarm+0x13/0x15 [nouveau] [ 326.169038] [<ffffffffa00da895>] nv04_timer_alarm_trigger+0x1b1/0x1cb [nouveau] [ 326.169059] [<ffffffffa00daaa0>] nv04_timer_alarm+0xb5/0xbe [nouveau] [ 326.169079] [<ffffffffa00d6af7>] alarm_timer_callback+0x15e/0x179 [nouveau] [ 326.169101] [<ffffffffa00da895>] nv04_timer_alarm_trigger+0x1b1/0x1cb [nouveau] [ 326.169121] [<ffffffffa00da90a>] nv04_timer_intr+0x5b/0x13c [nouveau] [ 326.169142] [<ffffffffa00d0e9b>] nouveau_mc_intr+0x2e2/0x3b1 [nouveau] [ 326.169160] [<ffffffff900ad359>] handle_irq_event_percpu+0x5c/0x1dc [ 326.169165] [<ffffffff900ad515>] handle_irq_event+0x3c/0x5c [ 326.169170] [<ffffffff900afa5e>] handle_edge_irq+0xc4/0xeb [ 326.169175] [<ffffffff9003a828>] handle_irq+0x120/0x12d [ 326.169179] [<ffffffff9003a2f8>] do_IRQ+0x48/0xaf [ 326.169183] [<ffffffff905a41ef>] ret_from_intr+0x0/0x13 [ 326.169189] other info that might help us debug this: [ 326.169193] Possible unsafe locking scenario: [ 326.169195] CPU0 CPU1 [ 326.169197] ---- ---- [ 326.169199] lock(&(&priv->sensor.alarm_program_lock)->rlock); [ 326.169205] lock(&(&priv->fan->lock)->rlock); [ 326.169211] lock(&(&priv->sensor.alarm_program_lock)->rlock); [ 326.169216] lock(&(&priv->fan->lock)->rlock); [ 326.169221] *** DEADLOCK *** [ 326.169225] 1 lock held by ldconfig/22297: [ 326.169229] #0: (&(&priv->sensor.alarm_program_lock)->rlock){-.-...}, at: [<ffffffffa00d6a8a>] alarm_timer_callback+0xf1/0x179 [nouveau] [ 326.169253] stack backtrace: [ 326.169258] CPU: 7 PID: 22297 Comm: ldconfig Not tainted 3.13.6 #1270 [ 326.169260] Hardware name: System manufacturer System Product Name/P6T SE, BIOS 0603 09/02/2009 [ 326.169264] ffffffff90fb6360 ffff8801bfdc3a38 ffffffff9059e369 0000000000000006 [ 326.169273] ffffffff90fb61b0 ffff8801bfdc3a88 ffffffff905998cf 0000000000000002 [ 326.169282] ffff8800b148dbe0 0000000000000001 ffff8800b148e1e0 0000000000000001 [ 326.169342] Call Trace: [ 326.169344] <IRQ> [<ffffffff9059e369>] dump_stack+0x4e/0x71 [ 326.169352] [<ffffffff905998cf>] print_circular_bug+0x2ad/0x2be [ 326.169356] [<ffffffff900a49cc>] __lock_acquire+0x10be/0x182b [ 326.169360] [<ffffffff900a3273>] ? check_irq_usage+0x99/0xab [ 326.169365] [<ffffffff900a5656>] lock_acquire+0xce/0x117 [ 326.169384] [<ffffffffa00d5363>] ? nouveau_fan_update+0xeb/0x252 [nouveau] [ 326.169388] [<ffffffff905a367e>] _raw_spin_lock_irqsave+0x3f/0x51 [ 326.169407] [<ffffffffa00d5363>] ? nouveau_fan_update+0xeb/0x252 [nouveau] [ 326.169426] [<ffffffffa00da871>] ? nv04_timer_alarm_trigger+0x18d/0x1cb [nouveau] [ 326.169445] [<ffffffffa00d5363>] nouveau_fan_update+0xeb/0x252 [nouveau] [ 326.169465] [<ffffffffa00d5508>] nouveau_therm_fan_set+0x14/0x16 [nouveau] [ 326.169483] [<ffffffffa00d4c6b>] nouveau_therm_update+0x303/0x312 [nouveau] [ 326.169502] [<ffffffffa00d4c8d>] nouveau_therm_alarm+0x13/0x15 [nouveau] [ 326.169521] [<ffffffffa00da895>] nv04_timer_alarm_trigger+0x1b1/0x1cb [nouveau] [ 326.169541] [<ffffffffa00daaa0>] nv04_timer_alarm+0xb5/0xbe [nouveau] [ 326.169560] [<ffffffffa00d6af7>] alarm_timer_callback+0x15e/0x179 [nouveau] [ 326.169579] [<ffffffffa00da895>] nv04_timer_alarm_trigger+0x1b1/0x1cb [nouveau] [ 326.169598] [<ffffffffa00da90a>] nv04_timer_intr+0x5b/0x13c [nouveau] [ 326.169617] [<ffffffffa00d0e9b>] nouveau_mc_intr+0x2e2/0x3b1 [nouveau] [ 326.169621] [<ffffffff900ad359>] handle_irq_event_percpu+0x5c/0x1dc [ 326.169624] [<ffffffff900ad515>] handle_irq_event+0x3c/0x5c [ 326.169628] [<ffffffff900afa5e>] handle_edge_irq+0xc4/0xeb [ 326.169631] [<ffffffff9003a828>] handle_irq+0x120/0x12d [ 326.169636] [<ffffffff90073e8c>] ? irq_enter+0x13/0x64 [ 326.169640] [<ffffffff9003a2f8>] do_IRQ+0x48/0xaf [ 326.169644] [<ffffffff905a41ef>] common_interrupt+0x6f/0x6f [ 326.169646] <EOI> [<ffffffff905a428d>] ? retint_swapgs+0xe/0x13

3 3

(no subject)
by Thomas Hellstrom 13 Mar '14

13 Mar '14

After a previous patch series and a discussion with Daniel Vetter and David Herrmann, I've reworked the patches a bit. Please review. Patch 5 is already reviewed. /Thomas >From Thomas Hellstrom <thellstrom(a)vmware.com> # This line is ignored. From: Thomas Hellstrom <thellstrom(a)vmware.com> Subject: In-Reply-To:

3 13

[RFC PATCH v2 00/21] Add DSI display support for Exynos based boards
by Andrzej Hajda 13 Mar '14

13 Mar '14

Hi, This patchset adds drivers and bindings to the following devices: - Exynos DSI master, - S6E8AA0 DSI panel, - TC358764 DSI/LVDS bridge, - HV070WSA-100 LVDS panel. It adds also display support in DTS files for the following boards: - Exynos4210/Trats, - Exynos4412/Trats2, - Exynos5250/Arndale. Things worth mentioning: 1. I have implemented DSI/LVDS bridge using drm_panel framework, ie. the driver exposes drm_panel interface on DSI side, and interact with panels on LVDS side using drm_panel framework. This approach seems to me simpler and more natural than using drm_bridge. 2. I have used video interface bindings to make link between bridge and LVDS panel. Other places where such links can be created are: a) link between DSI master and slave, I wonder if it is always neccessary, DSI bus is also video bus, b) link between FIMD(display controller) and DSI Master, currently Exynos DRM framework uses driver's hardcoded links, converting it to video interface bindings should be done (if required) by separate patches. The patchset is based on Sean's Paul Exynos refactor patches v4 [1]. To work properly porch calculation should be fixed according to my comment [2]. It is the 2nd iteration of the patches, main changes: - based on v4 refactor patches, - added arndale related stuff. Other changes are described in individual patches. [1] http://permalink.gmane.org/gmane.comp.video.dri.devel/99264 [2] http://permalink.gmane.org/gmane.comp.video.dri.devel/99826 Regards Andrzej Andrzej Hajda (21): drm_mipi_dsi: add flags to DSI messages drm/exynos: delay fbdev initialization until an output is connected exynos/dsim: add DT bindings drm/exynos: add DSIM driver panel/s6e8aa0: add DT bindings drm/panel: add S6E8AA0 driver panel/tc358764: add DT bindings drm/panel: add TC358764 driver panel/simple: add video interface DT bindings panel/hv070wsa-100: add DT bindings drm/panel: add support for BOE HV070WSA-100 panel to simple-panel ARM: dts: exynos4: add MIPI DSI Master node ARM: dts: exynos4210-trats: add panel node ARM: dts: exynos4412-trats2: add panel node ARM: dts: exynos5250: add mipi-phy node ARM: dts: exynos5250: add display power domain node ARM: dts: exynos5250: add DSI node ARM: dts: exynos5250-arndale: add display regulators ARM: dts: exynos5250-arndale: add dsi and panel nodes ARM: dts: exynos4210-trats: enable exynos/fimd node ARM: dts: exynos4412-trats2: enable exynos/fimd node .../devicetree/bindings/panel/boe,hv070wsa-100.txt | 7 + .../devicetree/bindings/panel/samsung,s6e8aa0.txt | 51 + .../devicetree/bindings/panel/simple-panel.txt | 6 + .../devicetree/bindings/panel/toshiba,tc358764.txt | 41 + .../devicetree/bindings/video/exynos_dsim.txt | 53 + arch/arm/boot/dts/exynos4.dtsi | 14 + arch/arm/boot/dts/exynos4210-trats.dts | 42 + arch/arm/boot/dts/exynos4412-trats2.dts | 51 + arch/arm/boot/dts/exynos5250-arndale.dts | 63 + arch/arm/boot/dts/exynos5250.dtsi | 25 + drivers/gpu/drm/exynos/Kconfig | 9 + drivers/gpu/drm/exynos/Makefile | 1 + drivers/gpu/drm/exynos/exynos_drm_drv.c | 26 +- drivers/gpu/drm/exynos/exynos_drm_drv.h | 1 + drivers/gpu/drm/exynos/exynos_drm_dsi.c | 1402 ++++++++++++++++++++ drivers/gpu/drm/exynos/exynos_drm_fb.c | 3 + drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 4 +- drivers/gpu/drm/panel/Kconfig | 14 + drivers/gpu/drm/panel/Makefile | 2 + drivers/gpu/drm/panel/panel-s6e8aa0.c | 1064 +++++++++++++++ drivers/gpu/drm/panel/panel-simple.c | 25 + drivers/gpu/drm/panel/panel-tc358764.c | 505 +++++++ include/drm/drm_mipi_dsi.h | 6 + 23 files changed, 3402 insertions(+), 13 deletions(-) create mode 100644 Documentation/devicetree/bindings/panel/boe,hv070wsa-100.txt create mode 100644 Documentation/devicetree/bindings/panel/samsung,s6e8aa0.txt create mode 100644 Documentation/devicetree/bindings/panel/toshiba,tc358764.txt create mode 100644 Documentation/devicetree/bindings/video/exynos_dsim.txt create mode 100644 drivers/gpu/drm/exynos/exynos_drm_dsi.c create mode 100644 drivers/gpu/drm/panel/panel-s6e8aa0.c create mode 100644 drivers/gpu/drm/panel/panel-tc358764.c -- 1.8.3.2

5 48

[PATCH 0/5] Control node master fixes v2
by Thomas Hellstrom 13 Mar '14

13 Mar '14

After a previous patch series and a discussion with Daniel Vetter and David Herrmann, I've reworked the patches a bit. Please review. Patch 1,2 and 5 already reviewed. Thanks, Thomas

1 5

WARN_ON() and X session lost from i915 on 3.14-rc6
by Pavel Machek 13 Mar '14

13 Mar '14

Hi! This cost me two half-written mails... So far it happened once, so it may be very infrequent; but I do not think I seen similar failure from i915 before, so it may be an regression. Well... -22 should be EINVAL afaict. Any ideas? Pavel [drm:i915_gem_object_get_pages] *ERROR* Attempting to obtain a purgeable object [drm:i915_gem_object_get_pages] *ERROR* Attempting to obtain a purgeable object ------------[ cut here ]------------ WARNING: CPU: 0 PID: 2945 at drivers/gpu/drm/i915/i915_gem.c:1459 i915_gem_fault+0x10c/0x240() unhandled error in i915_gem_fault: -22 Modules linked in: CPU: 0 PID: 2945 Comm: Xorg Tainted: G W 3.14.0-rc6+ #325 Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 ) 03/31/2011 000005b3 f00ade08 c47db94b c4a318f4 f00ade38 c4037f9a c4a31ed0 f00ade64 00000b81 c4a318f4 000005b3 c436cb9c c436cb9c 00000002 ea35af00 f00adebc f00ade50 c403803e 00000009 f00ade48 c4a31ed0 f00ade64 f00ade90 c436cb9c Call Trace: [<c47db94b>] dump_stack+0x41/0x52 [<c4037f9a>] warn_slowpath_common+0x7a/0xa0 [<c436cb9c>] ? i915_gem_fault+0x10c/0x240 [<c436cb9c>] ? i915_gem_fault+0x10c/0x240 [<c403803e>] warn_slowpath_fmt+0x2e/0x30 [<c436cb9c>] i915_gem_fault+0x10c/0x240 [<c40d2fa7>] __do_fault+0x57/0x490 [<c4074e6e>] ? __lock_acquire+0x3ae/0xc80 [<c436ca90>] ? i915_gem_pwrite_ioctl+0x8a0/0x8a0 [<c40d428b>] handle_mm_fault+0x14b/0x750 [<c402f54f>] ? __do_page_fault+0xaf/0x410 [<c402f8b0>] ? __do_page_fault+0x410/0x410 [<c402f8b0>] ? __do_page_fault+0x410/0x410 [<c402f59c>] __do_page_fault+0xfc/0x410 [<c403abb5>] ? SyS_setitimer+0x45/0xd0 [<c40fc3e5>] ? SyS_ioctl+0x45/0x70 [<c402f8b0>] ? __do_page_fault+0x410/0x410 [<c402f8bb>] do_page_fault+0xb/0x10 [<c47e0a17>] error_code+0x67/0x6c ---[ end trace c124d19552341c51 ]--- wlan0: deauthenticating from 00:33:13:01:31:45 by local choice (reason=3) cfg80211: Calling CRDA to update world regulatory domain Chrome_IOThread[20585]: segfault at 0 ip b459e086 sp ad7f9da0 error 4 in chromium-browser[b3ecd000+390f000] wlan0: authenticate with 00:33:13:01:31:45 wlan0: send auth to 00:33:13:01:31:45 (try 1/3) wlan0: authenticated wlan0: associate with 00:33:13:01:31:45 (try 1/3) -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

2 3

← Newer
1
...
78
79
80
81
82
83
84
...
93
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2014