dri-devel November 2014

dri-devel@lists.freedesktop.org

182 participants
1119 discussions

[PATCH] drm/panel: simple: Add AUO B116XW03 panel support
by Ajay Kumar 06 Nov '14

06 Nov '14

The AUO B116XW03 is a 11.6" HD TFT LCD panel connecting to a LVDS interface and with an integrated LED backlight unit. This panel is used on the Samsung Chromebook(XE303C12). Signed-off-by: Ajay Kumar <ajaykumar.rs(a)samsung.com> --- .../devicetree/bindings/panel/auo,b116xw03.txt | 7 ++++++ drivers/gpu/drm/panel/panel-simple.c | 25 ++++++++++++++++++++ 2 files changed, 32 insertions(+) create mode 100644 Documentation/devicetree/bindings/panel/auo,b116xw03.txt diff --git a/Documentation/devicetree/bindings/panel/auo,b116xw03.txt b/Documentation/devicetree/bindings/panel/auo,b116xw03.txt new file mode 100644 index 0000000..690d0a5 --- /dev/null +++ b/Documentation/devicetree/bindings/panel/auo,b116xw03.txt @@ -0,0 +1,7 @@ +AU Optronics Corporation 11.6" HD (1366x768) color TFT-LCD panel + +Required properties: +- compatible: should be "auo,b116xw03" + +This binding is compatible with the simple-panel binding, which is specified +in simple-panel.txt in this directory. diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index 4ce1db0..51566e0 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -352,6 +352,28 @@ static const struct panel_desc auo_b101aw03 = { }, }; +static const struct drm_display_mode auo_b116xw03_mode = { + .clock = 70589, + .hdisplay = 1366, + .hsync_start = 1366 + 40, + .hsync_end = 1366 + 40 + 40, + .htotal = 1366 + 40 + 40 + 32, + .vdisplay = 768, + .vsync_start = 768 + 10, + .vsync_end = 768 + 10 + 12, + .vtotal = 768 + 10 + 12 + 6, + .vrefresh = 60, +}; + +static const struct panel_desc auo_b116xw03 = { + .modes = &auo_b116xw03_mode, + .num_modes = 1, + .size = { + .width = 256, + .height = 144, + }, +}; + static const struct drm_display_mode auo_b133xtn01_mode = { .clock = 69500, .hdisplay = 1366, @@ -616,6 +638,9 @@ static const struct of_device_id platform_of_match[] = { .compatible = "auo,b101aw03", .data = &auo_b101aw03, }, { + .compatible = "auo,b116xw03", + .data = &auo_b116xw03, + }, { .compatible = "auo,b133htn01", .data = &auo_b133htn01, }, { -- 1.7.9.5

2 1

exynos-drm registration: infinite loop
by Matwey V. Kornilov 06 Nov '14

06 Nov '14

Hi, I run 3.18-rc3 kernel on BeagleBone Black. It doesn't have Exynos DRM of course, but I run multi-platform kernel where CONFIG_DRM_EXYNOS is set to 'y'. The issue here is that the platform probe/init goes to infinite loop as the following: [ 5.717343] platform exynos-drm: Driver exynos-drm requests probe deferral [ 5.726848] exynos-drm-ipp exynos-drm-ipp: drm ipp registered successfully. [ 5.734700] platform exynos-drm: Driver exynos-drm requests probe deferral [ 5.744044] exynos-drm-ipp exynos-drm-ipp: drm ipp registered successfully. [ 5.752010] platform exynos-drm: Driver exynos-drm requests probe deferral [ 5.761377] exynos-drm-ipp exynos-drm-ipp: drm ipp registered successfully. [ 5.769291] platform exynos-drm: Driver exynos-drm requests probe deferral It is quite unexpectable behavior. I would expect that the exynos-drm failed to initialize with 'no device' error. See also for the reference: https://bugzilla.kernel.org/show_bug.cgi?id=87691

4 10

[PATCH] drm/panel: ld9040: Update calls to gpiod_get*()
by Alexandre Courbot 06 Nov '14

06 Nov '14

Add the new flags argument to calls of (devm_)gpiod_get*() and remove any direction setting code afterwards. Currently both forms (with or without the flags argument) are valid thanks to transitional macros in <linux/gpio/consumer.h>. These macros will be removed once all consumers are updated and the flags argument will become compulsary. Signed-off-by: Alexandre Courbot <acourbot(a)nvidia.com> --- drivers/gpu/drm/panel/panel-ld9040.c | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/gpu/drm/panel/panel-ld9040.c b/drivers/gpu/drm/panel/panel-ld9040.c index 42ac67b21e9f..dd1d3f2e624e 100644 --- a/drivers/gpu/drm/panel/panel-ld9040.c +++ b/drivers/gpu/drm/panel/panel-ld9040.c @@ -336,17 +336,12 @@ static int ld9040_probe(struct spi_device *spi) if (ret < 0) return ret; - ctx->reset_gpio = devm_gpiod_get(dev, "reset"); + ctx->reset_gpio = devm_gpiod_get(dev, "reset", GPIOD_OUT_HIGH); if (IS_ERR(ctx->reset_gpio)) { dev_err(dev, "cannot get reset-gpios %ld\n", PTR_ERR(ctx->reset_gpio)); return PTR_ERR(ctx->reset_gpio); } - ret = gpiod_direction_output(ctx->reset_gpio, 1); - if (ret < 0) { - dev_err(dev, "cannot configure reset-gpios %d\n", ret); - return ret; - } spi->bits_per_word = 9; ret = spi_setup(spi); -- 2.1.2

4 4

[Bug 85950] GLAMOR crashes w/ radeon rv6xx GPU when using OpenGL games
by bugzilla-daemon＠freedesktop.org 06 Nov '14

06 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=85950 --- Comment #2 from Shawn Starr <shawn.starr(a)rogers.com> --- Mesa versions now: 10.3.2-1.20141028.fc21.x86_64 Kernel: 3.18.0-0.rc3.git1.2.fc22.1.x86_64 or kernel-3.17.2-300.fc21.x86_64 Previous would have been August-September time frame for no issues such as this, kernels stable were 3.16/pre-3.17 kernels were fine. I reinstalled laptop to get a fresh Fedora 21 vs my Fedora 20/21 transition. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 85950] GLAMOR crashes w/ radeon rv6xx GPU when using OpenGL games
by bugzilla-daemon＠freedesktop.org 06 Nov '14

06 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=85950 Michel Dänzer <michel(a)daenzer.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Server/General |Drivers/Gallium/r600 Assignee|xorg-team(a)lists.x.org |dri-devel(a)lists.freedesktop | |.org Product|xorg |Mesa QA Contact|xorg-team(a)lists.x.org | --- Comment #1 from Michel Dänzer <michel(a)daenzer.net> --- It's more likely an issue in Mesa than in glamor. What were the versions of the kernel, Mesa and xserver/glamor before the problem started, and what's the version of Mesa now? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[PATCH] drm/panel: s6e8aa0: Update calls to gpiod_get*()
by Alexandre Courbot 06 Nov '14

06 Nov '14

Add the new flags argument to calls of (devm_)gpiod_get*() and remove any direction setting code afterwards. Currently both forms (with or without the flags argument) are valid thanks to transitional macros in <linux/gpio/consumer.h>. These macros will be removed once all consumers are updated and the flags argument will become compulsary. Signed-off-by: Alexandre Courbot <acourbot(a)nvidia.com> --- drivers/gpu/drm/panel/panel-s6e8aa0.c | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/gpu/drm/panel/panel-s6e8aa0.c b/drivers/gpu/drm/panel/panel-s6e8aa0.c index b5217fe37f02..6427aa187735 100644 --- a/drivers/gpu/drm/panel/panel-s6e8aa0.c +++ b/drivers/gpu/drm/panel/panel-s6e8aa0.c @@ -1019,17 +1019,12 @@ static int s6e8aa0_probe(struct mipi_dsi_device *dsi) return ret; } - ctx->reset_gpio = devm_gpiod_get(dev, "reset"); + ctx->reset_gpio = devm_gpiod_get(dev, "reset", GPIOD_OUT_HIGH); if (IS_ERR(ctx->reset_gpio)) { dev_err(dev, "cannot get reset-gpios %ld\n", PTR_ERR(ctx->reset_gpio)); return PTR_ERR(ctx->reset_gpio); } - ret = gpiod_direction_output(ctx->reset_gpio, 1); - if (ret < 0) { - dev_err(dev, "cannot configure reset-gpios %d\n", ret); - return ret; - } ctx->brightness = GAMMA_LEVEL_NUM - 1; -- 2.1.2

4 6

[Bug 84021] New: [game][the cave] not rendered properly
by bugzilla-daemon＠freedesktop.org 06 Nov '14

06 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=84021 Priority: medium Bug ID: 84021 Assignee: dri-devel(a)lists.freedesktop.org Summary: [game][the cave] not rendered properly Severity: major Classification: Unclassified OS: Linux (All) Reporter: sylvain.bertrand(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa The intro screen is mainly white and we hardly can see anything -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 82918] New: [tahiti xt] dota2 crashes
by bugzilla-daemon＠freedesktop.org 06 Nov '14

06 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=82918 Priority: medium Bug ID: 82918 Assignee: dri-devel(a)lists.freedesktop.org Summary: [tahiti xt] dota2 crashes Severity: critical Classification: Unclassified OS: Linux (All) Reporter: sylvain.bertrand(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Up-to-date fedora rawhide on x86_64. Linux 3.17.0-0.rc1.git1.2.fc22.1.x86_64 dota2 crashes This is a recent tahiti XT board (marketing name is R9 280X). I have an "old" tahiti XT board (marketing name is HD 7970), I recalled dota2 working fine a few weeks ago (not tested recently though) on that "old" board. Then I don't know if it fits into regression since I guess the atombios is probably different. -- You are receiving this mail because: You are the assignee for the bug.

1 18

Re: Bug#768157: machine hangs when loading cirrus with modeset=1 while booted with vga=791
by Ben Hutchings 05 Nov '14

05 Nov '14

Control: tag -1 upstream confirmed On Wed, 2014-11-05 at 15:02 +0100, Evgeni Golov wrote: > Package: src:linux > Version: 3.16.7-1 > Severity: normal > > Hi, > > while testing the new Grml release, I noticed an interesting hang of QEMU when > the machine is booted. The initial testing was done using [1] in QEMU from Sid > (2.1+dfsg-5), but I also could reproduce it with the same QEMU and a fresh > Jessie install with both, 3.16.5-1 and 3.16.7-1. > > To reproduce: > * boot a fresh Jessie with 3.16 kernel in QEMU and vga=791 as bootparam > * modprobe cirrus modeset=1 > * machine hangs > > I am not sure this will happen on real cirrus HW, as I don't have any, but QEMU > is quite widespread and cirrus is the default VGA driver. [...] The cirrus KMS driver only binds to QEMU Cirrus devices, not real hardware. It has been working for me, but I can reproduce the apparent hang with the 'vga=791' parameter. It's not actually hanging, though - using a serial console, I see the error messages: [ 1.976874] [drm:cirrus_vram_init] *ERROR* can't reserve VRAM [ 1.978067] cirrus 0000:00:02.0: Fatal error during GPU init: -6 and I can log in there. But, as the driver detects this error after the point of no return (remove_conflicting_framebuffers()), the display remains broken. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong.

1 0

[Bug 81644] New: Random crashes on RadeonSI with Chromium.
by bugzilla-daemon＠freedesktop.org 05 Nov '14

05 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=81644 Priority: medium Bug ID: 81644 Assignee: dri-devel(a)lists.freedesktop.org Summary: Random crashes on RadeonSI with Chromium. Severity: normal Classification: Unclassified OS: All Reporter: aaronbottegal(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Chromium randomly crashes with RadeonSI driver when using Chromium. Most usually with Youtube videos. Everything is current git from Oibaf PPA using Mint 17 Cinnamon, although I'm about to move to Arch Linux so I don't know how long I'll be able to provide logs as the problem doesn't exist in Arch's currents AFAIK. But there are logs in Bug #77980 from my crash, which was close sounding, but apparently a different bug. -- You are receiving this mail because: You are the assignee for the bug.

1 150

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel November 2014