dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[Bug 83460] New: [radeon regression] Backlight turned off since kernel upgrade
by bugzilla-daemon＠freedesktop.org 29 Sep '14

29 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=83460 Priority: medium Bug ID: 83460 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeon regression] Backlight turned off since kernel upgrade Severity: normal Classification: Unclassified OS: Linux (All) Reporter: spmf2004-freedesktop(a)yahoo.fr Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Since the upgrade to Ubuntu kernel 3.13.0-35 (from 3.13.0-34), the screen is very dark to the point it's unusable. Backlight seems completely turned off. Using the brightness keys doesn't help. It was working fine with 3.13.0-34. I found that the offending patch is "drm/radeon: set default bl level to something reasonable". I reverted this patch and recompiled 3.13.0-35, and it solved the problem. I also checked that this problem also affects mainline kernel 3.17rc3. More technical details can be found on Ubuntu's bugtracker : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364148 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 70651] New: cannot write to power_dpm_force_performance_level: invalid argument (radeon 7730m)
by bugzilla-daemon＠bugzilla.kernel.org 29 Sep '14

29 Sep '14

https://bugzilla.kernel.org/show_bug.cgi?id=70651 Bug ID: 70651 Summary: cannot write to power_dpm_force_performance_level: invalid argument (radeon 7730m) Product: Drivers Version: 2.5 Kernel Version: 3.13.3 Hardware: x86-64 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: sjh+bugzillakernel(a)sanjioh.org Regression: No Created attachment 126301 --> https://bugzilla.kernel.org/attachment.cgi?id=126301&action=edit 3.13.3 dmesg hi, I'm using a notebook with intel ivy bridge + amd radeon 7730m hybrid graphics. With the latest stable kernel (3.13.3) I can't echo (low, high, auto) to /sys/class/drm/card0/device/power_dpm_force_performance_level: root@darkstar:~# echo "high"> /sys/class/drm/card0/device/power_dpm_force_performance_level -bash: echo: write error: Invalid argument root@darkstar:~# echo "low" /sys/class/drm/card0/device/power_dpm_force_performance_level low /sys/class/drm/card0/device/power_dpm_force_performance_level root@darkstar:~# echo "auto" /sys/class/drm/card0/device/power_dpm_force_performance_level auto /sys/class/drm/card0/device/power_dpm_force_performance_level I cannot say it's a regression since I haven't tried previous kernels. I can echo "battery", "performance" or "balanced" to /sys/class/drm/card0/device/power_dpm_state Some other info: root@darkstar:~# cat /sys/class/drm/card0/device/power_dpm_force_performance_level auto root@darkstar:~# lspci|grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] Chelsea LP [Radeon HD 7730M] (rev ff) root@darkstar:~# cat /sys/kernel/debug/vgaswitcheroo/switch 0:DIS: :DynOff:0000:01:00.0 1:IGD:+:Pwr:0000:00:02.0 root@darkstar:~# for i in /sys/class/drm/card0/device/power/*; do echo "$i: $(cat $i)"; done /sys/class/drm/card0/device/power/autosuspend_delay_ms: 5000 /sys/class/drm/card0/device/power/control: auto /sys/class/drm/card0/device/power/runtime_active_time: 33415 /sys/class/drm/card0/device/power/runtime_status: suspended /sys/class/drm/card0/device/power/runtime_suspended_time: 934700 /sys/class/drm/card0/device/power/wakeup: disabled /sys/class/drm/card0/device/power/wakeup_abort_count: /sys/class/drm/card0/device/power/wakeup_active: /sys/class/drm/card0/device/power/wakeup_active_count: /sys/class/drm/card0/device/power/wakeup_count: /sys/class/drm/card0/device/power/wakeup_expire_count: /sys/class/drm/card0/device/power/wakeup_last_time_ms: /sys/class/drm/card0/device/power/wakeup_max_time_ms: /sys/class/drm/card0/device/power/wakeup_total_time_ms: root@darkstar:~# cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 575000 kHz current engine clock: 210280 kHz default memory clock: 900000 kHz current memory clock: 00 kHz voltage: 825 mV PCIE lanes: 16 (This last output is different from the ones I've seen around) Am I missing something? dmesg attached Thanks -- You are receiving this mail because: You are watching the assignee of the bug.

1 14

[PATCH v6 00/11] drm: add support for Atmel HLCDC Display Controller
by Boris Brezillon 29 Sep '14

29 Sep '14

Hello, This patch series adds support for the Atmel HLCDC block (HLCD Controller) available on some Atmel SoCs (i.e. the sama5d3 family). The HLCDC actually provides a Display Controller and a PWM device, hence I decided to declare an MFD device exposing 2 subdevices: a display controller and a PWM chip. This also solves a circular dependency issue preventing HLCDC driver from unloading. The HLCDC request a drm_panel device, which request a backlight device (a PWM backlight), which depends on a PWM which is provided by the HLCDC driver (hlcdc -> panel -> backlight -> hlcdc (pwm part)). The current implementation only supports sama5d3 SoCs but other SoCs should be easily ported by defining new compatible strings and adding HLCDC description structures for these SoCs (Ludovic tested this driver on an at91sam9x5 board). The drivers supports basic CRTC functionalities, several overlays and an hardware cursor. At the moment, it only supports connection to LCD panels through an RGB connector (defined as an LVDS connector in my implementation), though connection to other kind of devices (like DRM bridges) could be added later. It also supports several RGB formats on all planes and some YUV formats on the HEO overlay plane. This series depends those ones: [1], [2] and [3]. Best Regards, Boris [1]http://lkml.iu.edu/hypermail/linux/kernel/1407.1/04171.html [2]https://lkml.org/lkml/2014/9/29/330 [3]https://lkml.org/lkml/2014/9/22/575 Changes since v5: - fix Kconfig dependency bug - use adjusted mode in crtc config - move signal config (clk, hsync, vsync) from connector to crtc mode_set function - use standard rotation property - check display_mode validity in connecto mode_valid function - remove dma_set_coherent mask call (now done in MFD core) - do not use drm_platform_init Changes since v4: - fix a few more bugs in rotation handling (rotation was buggy on some formats) - return connector_status_unknown until a panel is exposed by the drm_panel infrastructure (prevent fbdev creation until everyting is in place) - rework Kconfig MFD_ATMEL_HLCDC selection to simplify the configuration (automatically select this option when selecting the HLCDC PMW or DRM driver, instead of depending on this option) Changes since v3: - rework the layer code to simplify several parts (locking and layer disabling) - make use of the drm_flip_work infrastructure - rely on default HW cursor implementation using on the cursor plane - rework the display controller DT bindings (based on OF graph representation) - add rotation support - retrive RGB bus format from drm_display_info - drop the dynamic pinctrl state selection - rework HLCDC output handling (previously specialized to interface with LCD panels) - drop ".module = THIS_MODULE" lines - change display controller compatible string Changes since v2: - fix coding style issues (macro indentation) - make use of GENMASK in several places - declare regmap config as a static structure - rework hlcdc plane update API - rework cursor handling to make use of the new plane update API - fix backporch config - do not use devm_regmap_init_mmio_clk to avoid extra clk_enable clk disable calls when accessing registers - explicitely include regmap and clk headers instead of relying on atmel-hlcdc.h inclusions - make the atmel-hlcdc driver depends on CONFIG_OF - separate DT bindings documentation from driver implementation - support several pin muxing for HLCDC pins on sama5d3 SoCs Changes since v1: - replace the backlight driver by a PWM driver - make use of drm_panel infrastructure - split driver code in several subsystem: MFD, PWM and DRM - add support for overlays - add support for hardware cursor Boris BREZILLON (10): mfd: add documentation for atmel-hlcdc DT bindings pwm: add support for atmel-hlcdc-pwm device pwm: add DT bindings documentation for atmel-hlcdc-pwm driver drm: add Atmel HLCDC Display Controller support drm: add DT bindings documentation for atmel-hlcdc-dc driver ARM: AT91/dt: split sama5d3 lcd pin definitions to match RGB mode configs ARM: AT91/dt: add alternative pin muxing for sama5d3 lcd pins ARM: at91/dt: define the HLCDC node available on sama5d3 SoCs ARM: at91/dt: add LCD panel description to sama5d3xdm.dtsi ARM: at91/dt: enable the LCD panel on sama5d3xek boards Boris Brezillon (1): mfd: add atmel-hlcdc driver .../devicetree/bindings/drm/atmel-hlcdc-dc.txt | 54 ++ .../devicetree/bindings/mfd/atmel-hlcdc.txt | 50 ++ .../devicetree/bindings/pwm/atmel-hlcdc-pwm.txt | 55 ++ arch/arm/boot/dts/sama5d31ek.dts | 20 + arch/arm/boot/dts/sama5d33ek.dts | 20 + arch/arm/boot/dts/sama5d34ek.dts | 20 + arch/arm/boot/dts/sama5d36ek.dts | 20 + arch/arm/boot/dts/sama5d3_lcd.dtsi | 205 ++++- arch/arm/boot/dts/sama5d3xdm.dtsi | 58 ++ drivers/gpu/drm/Kconfig | 2 + drivers/gpu/drm/Makefile | 1 + drivers/gpu/drm/atmel-hlcdc/Kconfig | 13 + drivers/gpu/drm/atmel-hlcdc/Makefile | 7 + drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 392 ++++++++++ drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 527 +++++++++++++ drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.h | 216 ++++++ drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_layer.c | 659 ++++++++++++++++ drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_layer.h | 403 ++++++++++ drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c | 443 +++++++++++ drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c | 833 +++++++++++++++++++++ drivers/mfd/Kconfig | 6 + drivers/mfd/Makefile | 1 + drivers/mfd/atmel-hlcdc.c | 118 +++ drivers/pwm/Kconfig | 10 + drivers/pwm/Makefile | 1 + drivers/pwm/pwm-atmel-hlcdc.c | 229 ++++++ include/linux/mfd/atmel-hlcdc.h | 78 ++ 27 files changed, 4410 insertions(+), 31 deletions(-) create mode 100644 Documentation/devicetree/bindings/drm/atmel-hlcdc-dc.txt create mode 100644 Documentation/devicetree/bindings/mfd/atmel-hlcdc.txt create mode 100644 Documentation/devicetree/bindings/pwm/atmel-hlcdc-pwm.txt create mode 100644 drivers/gpu/drm/atmel-hlcdc/Kconfig create mode 100644 drivers/gpu/drm/atmel-hlcdc/Makefile create mode 100644 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c create mode 100644 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c create mode 100644 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.h create mode 100644 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_layer.c create mode 100644 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_layer.h create mode 100644 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c create mode 100644 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c create mode 100644 drivers/mfd/atmel-hlcdc.c create mode 100644 drivers/pwm/pwm-atmel-hlcdc.c create mode 100644 include/linux/mfd/atmel-hlcdc.h -- 1.9.1

2 12

[PATCH] drm/tegra: Setup PHY_TIMING & BTA_TIMING registers in setup_clock()
by Sean Paul 29 Sep '14

29 Sep '14

Make sure we initialize the dsi PHY_TIMING and BTA_TIMING registers when we setup the clocks, as opposed to in dsi_configure. The phy timings must be initialized before drm_panel prepare() so that any DCS commands sent at this time are using the appropriate timings. Signed-off-by: Sean Paul <seanpaul(a)chromium.org> --- drivers/gpu/drm/tegra/dsi.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/tegra/dsi.c b/drivers/gpu/drm/tegra/dsi.c index c0258ae..6923c9b 100644 --- a/drivers/gpu/drm/tegra/dsi.c +++ b/drivers/gpu/drm/tegra/dsi.c @@ -369,6 +369,9 @@ static int tegra_dsi_set_phy_timing(struct tegra_dsi *dsi) DSI_TIMING_FIELD(timing.tago, period, 1); tegra_dsi_writel(dsi, value, DSI_BTA_TIMING); + if (dsi->slave) + return tegra_dsi_set_phy_timing(dsi->slave); + return 0; } @@ -482,10 +485,6 @@ static int tegra_output_dsi_enable(struct tegra_output *output) value &= ~DSI_CONTROL_HOST_ENABLE; tegra_dsi_writel(dsi, value, DSI_CONTROL); - err = tegra_dsi_set_phy_timing(dsi); - if (err < 0) - return err; - for (i = 0; i < NUM_PKT_SEQ; i++) tegra_dsi_writel(dsi, pkt_seq[i], DSI_PKT_SEQ_0_LO + i); @@ -660,6 +659,12 @@ static int tegra_output_dsi_setup_clock(struct tegra_output *output, value = DSI_TALLY_TA(0) | DSI_TALLY_LRX(0) | DSI_TALLY_HTX(0); tegra_dsi_writel(dsi, value, DSI_TO_TALLY); + err = tegra_dsi_set_phy_timing(dsi); + if (err) { + dev_err(dsi->dev, "failed to setup phy timing: %d\n", err); + return err; + } + return 0; } -- 2.1.1

1 1

[Bug 22312] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
by bugzilla-daemon＠bugzilla.kernel.org 29 Sep '14

29 Sep '14

https://bugzilla.kernel.org/show_bug.cgi?id=22312 --- Comment #16 from Alex Deucher <alexdeucher(a)gmail.com> --- (In reply to Jarkko K from comment #15) > Did you notice what I said? > > "I also have the error and and suddenly these lines" > > I also had the not able to find bios rom error. line and also those other > lines which i pasted. The unable to find bios errors can be ignored on your system they print on just about every system. They are only a problem when the driver is not able to load. The driver is able to eventually find the rom and load successfully on your system. The VM faults are a different issue. -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

[Bug 22312] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
by bugzilla-daemon＠bugzilla.kernel.org 29 Sep '14

29 Sep '14

https://bugzilla.kernel.org/show_bug.cgi?id=22312 --- Comment #15 from Jarkko K <jarkko_korpi(a)hotmail.com> --- Did you notice what I said? "I also have the error and and suddenly these lines" I also had the not able to find bios rom error. line and also those other lines which i pasted. -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

[Bug 22312] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
by bugzilla-daemon＠bugzilla.kernel.org 29 Sep '14

29 Sep '14

https://bugzilla.kernel.org/show_bug.cgi?id=22312 --- Comment #14 from Alex Deucher <alexdeucher(a)gmail.com> --- Note that this message is still present even when the driver is able to find the vbios rom due to changes in the pci subsystem for the order of methods it uses for fetching the rom. If the kernel driver loads successfully, these messages can be ignored. -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

[PATCH:drm 1/4] intel: Only define variable when it's used.
by Thomas Klausner 29 Sep '14

29 Sep '14

Signed-off-by: Thomas Klausner <wiz(a)NetBSD.org> --- intel/test_decode.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/intel/test_decode.c b/intel/test_decode.c index b710f34..f9127cf 100644 --- a/intel/test_decode.c +++ b/intel/test_decode.c @@ -90,7 +90,10 @@ compare_batch(struct drm_intel_decode *ctx, const char *batch_filename) { FILE *out = NULL; void *ptr, *ref_ptr, *batch_ptr; - size_t size, ref_size, batch_size; +#ifdef HAVE_OPEN_MEMSTREAM + size_t size; +#endif + size_t ref_size, batch_size; const char *ref_suffix = "-ref.txt"; char *ref_filename; -- 1.9.4

1 5

[Bug 22312] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
by bugzilla-daemon＠bugzilla.kernel.org 29 Sep '14

29 Sep '14

https://bugzilla.kernel.org/show_bug.cgi?id=22312 --- Comment #13 from Cesko Voeten <cvoeten(a)gmail.com> --- (In reply to Michel Dänzer from comment #12) > P.S. Cesko, if you could change the title of this report to something like > '[drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM', that might help > prevent others from incorrectly considering this report related to their > problem. Done! And perhaps it should also be pointed out that my specific problem was that the driver indeed could not locate the BIOS ROM *while my Intel iGPU was set as primary in the BIOS*. Perhaps that might have been a relevant factor. -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

[Bug 22312] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
by bugzilla-daemon＠bugzilla.kernel.org 29 Sep '14

29 Sep '14

https://bugzilla.kernel.org/show_bug.cgi?id=22312 Cesko Voeten <cvoeten(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|radeon 0000:01:00.0: |[drm:radeon_get_bios] |Invalid ROM contents |*ERROR* Unable to locate a | |BIOS ROM -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2014