Re: [radeon-alex:drm-next-4.12-wip 34/40] drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c:620:4: warning: left shift count >= width of type

Mhm, guys any idea why the build bot is spamming us with that warning? The type is 64bit and the shift is 63, so that should work fine. Regards, Christian. Am 10.02.2017 um 20:48 schrieb kbuild test robot: tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.12-wip head: d32ff0ea

[bug report] drm/msm/dsi: Move PHY operations out of host

Hello Hai Li, This is a semi-automatic email about new static checker warnings. The patch b62aa70a98c5: "drm/msm/dsi: Move PHY operations out of host" from Jan 7, 2017, leads to the following Smatch complaint: ./drivers/gpu/drm/msm/dsi/dsi_manager.c:174 dsi_mgr_phy_enable() error: we p

[Bug 193341] AMDGPU: kernel NULL pointer dereferenced with hybrid graphics

https://bugzilla.kernel.org/show_bug.cgi?id=193341 --- Comment #5 from Alex Deucher (alexdeuc...@gmail.com) --- Created attachment 254699 --> https://bugzilla.kernel.org/attachment.cgi?id=254699&action=edit possible fix This should fix it (along with the previous patch). -- You are receiving

[Bug 99387] Kernel 4.9: Kaveri + Hainan choked on boot using amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=99387 --- Comment #15 from Alex Deucher --- Created attachment 129497 --> https://bugs.freedesktop.org/attachment.cgi?id=129497&action=edit possible fix This should fix it (in addition to the previous patch). -- You are receiving this mail because

[Bug 193341] AMDGPU: kernel NULL pointer dereferenced with hybrid graphics

https://bugzilla.kernel.org/show_bug.cgi?id=193341 Marco Piazza (mpia...@gmail.com) changed: What|Removed |Added CC||mpia...@gmail.com ---

[Bug 99387] Kernel 4.9: Kaveri + Hainan choked on boot using amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=99387 --- Comment #14 from Marco --- Created attachment 129496 --> https://bugs.freedesktop.org/attachment.cgi?id=129496&action=edit oops in 4.9.2 For the sake of being complete, find attached log of kernel oops on kernel 4.9.2 (before patch was app

[Bug 97879] [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)

https://bugs.freedesktop.org/show_bug.cgi?id=97879 --- Comment #80 from Jani Kärkkäinen --- I think this is merged now? Using the padoka git ppa which just so happened to be updated, which included this patch (as it was just merged?), I can confirm the findings others had. The lag spikes effect

[Bug 99387] Kernel 4.9: Kaveri + Hainan choked on boot using amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=99387 --- Comment #13 from Marco --- Created attachment 129495 --> https://bugs.freedesktop.org/attachment.cgi?id=129495&action=edit Oops 4.9.9 Jumping in, I have a similar hybrid GPU: 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/AT

[Bug 99748] [radeonsi] Civ6 Assert in LLVM SIMachineScheduler.cpp with R600_DEBUG=sisched

https://bugs.freedesktop.org/show_bug.cgi?id=99748 Mike Lothian changed: What|Removed |Added CC||m...@fireburn.co.uk --- Comment #1 from M

[Bug 97879] [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)

https://bugs.freedesktop.org/show_bug.cgi?id=97879 --- Comment #79 from Timothee Besset --- (testing done - it may take a few days before this rolls out in a steam update) -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.__

[radeon-alex:drm-next-4.12-wip 34/40] drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c:620:16: note: in expansion of macro 'AMDGPU_PTE_PRT'

tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.12-wip head: d32ff0ea8e22964abcc6406e00a0646f2bfb94c7 commit: 382a21d981661dbc8198c37dc95707e1e381ce76 [34/40] drm/amdgpu: IOCTL interface for PRT support v4 config: parisc-allmodconfig (attached as .config) compiler: hppa-linux-gn

[PATCH] drm: Reduce EDID warnings from DRM_ERROR to DRM_NOTE

The warnings from parsing the EDID are not driver errors, but the "normal but significant" conditions from the external device. As such, they do not need the ferocity of an *ERROR*, but can use the less harsh DRM_NOTE instead. Signed-off-by: Chris Wilson --- drivers/gpu/drm/drm_edid.c | 15 +

[radeon-alex:drm-next-4.12-wip 33/40] drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h:68:30: warning: left shift count >= width of type

tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.12-wip head: d32ff0ea8e22964abcc6406e00a0646f2bfb94c7 commit: 7958b9959ea9dd544675adebddab255f7c536da7 [33/40] drm/amdgpu: add basic PRT support (v2) config: parisc-allmodconfig (attached as .config) compiler: hppa-linux-gnu-gcc (D

[radeon-alex:drm-next-4.12-wip 34/40] drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c:620:4: warning: left shift count >= width of type

tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.12-wip head: d32ff0ea8e22964abcc6406e00a0646f2bfb94c7 commit: 382a21d981661dbc8198c37dc95707e1e381ce76 [34/40] drm/amdgpu: IOCTL interface for PRT support v4 config: xtensa-allmodconfig (attached as .config) compiler: xtensa-linux-

[radeon-alex:drm-next-4.12-wip 33/40] drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:1222:2: warning: left shift count >= width of type

tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.12-wip head: d32ff0ea8e22964abcc6406e00a0646f2bfb94c7 commit: 7958b9959ea9dd544675adebddab255f7c536da7 [33/40] drm/amdgpu: add basic PRT support (v2) config: xtensa-allmodconfig (attached as .config) compiler: xtensa-linux-gcc (GCC

[Bug 95306] Random Blank(black) screens on "Carrizo"

https://bugs.freedesktop.org/show_bug.cgi?id=95306 --- Comment #58 from Tom St Denis --- The only deltas I can see from rc4 to now are in powerplay... so does booting with amdgpu.powerplay=0 help? -- You are receiving this mail because: You are the assignee for the bug._

[Bug 95306] Random Blank(black) screens on "Carrizo"

https://bugs.freedesktop.org/show_bug.cgi?id=95306 --- Comment #57 from Patrick Laurin --- I was finally able to get another laptop from my company. No more AMDGPU for me! Core i3 with Intel HD Graphics 520 = Heaven But hey, i'll still follow that thread :) On 9 February 2017 at 20:18, wrote:

[Bug 97879] [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)

https://bugs.freedesktop.org/show_bug.cgi?id=97879 --- Comment #78 from Timothee Besset --- Testing a game side fix for this problem atm (doesn't require the patched drivers). If someone wants to give it a spin before I send it to Psyonix, catch me on freenode (TTimo). -- You are receiving this

[PATCH v2] drm/atmel-hlcdc: Simplify the HLCDC layer logic

An HLCDC layers in Atmel's nomenclature is either a DRM plane or a 'Post Processing Layer' which can be used to output the results of the HLCDC composition in a memory buffer. atmel_hlcdc_layer.c was designed to be generic enough to be re-usable in both cases, but we're not exposing the post-proce

[Bug 99476] Forcing perf level to high doesn't change memory clock

https://bugs.freedesktop.org/show_bug.cgi?id=99476 Samuel Pitoiset changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 99765] Make Octopus OpenCL support work on Clover and RadeonSI

https://bugs.freedesktop.org/show_bug.cgi?id=99765 Vedran Miletić changed: What|Removed |Added Blocks||99553 URL|

[Bug 99553] Tracker bug for runnning OpenCL applications on Clover

https://bugs.freedesktop.org/show_bug.cgi?id=99553 Vedran Miletić changed: What|Removed |Added Depends on||99765 Referenced Bugs: https://bugs.f

[Bug 99765] Make Octopus OpenCL support work on Clover and RadeonSI

https://bugs.freedesktop.org/show_bug.cgi?id=99765 Bug ID: 99765 Summary: Make Octopus OpenCL support work on Clover and RadeonSI Product: Mesa Version: git Hardware: Other OS: All Status: NEW

Re: [PATCH v2 7/7] drm: Rename connector list iterator API

On Fri, Feb 10, 2017 at 06:14:14PM +0100, Thierry Reding wrote: [...] > /** > - * drm_connector_list_iter_get - initialize a connector_list iterator > + * drm_connector_list_iter_begin - initialize a connector_list iterator > * @dev: DRM device > * @iter: connector_list iterator > * > * Se

Re: [PATCH v3 21/24] drm/rockchip: dw-mipi-dsi: defer probe if panel is not loaded

On Tue, 31 Jan 2017 14:21:17 -0500, Sean Paul wrote: > On Sun, Jan 29, 2017 at 01:24:41PM +, John Keeping wrote: > > This ensures that the output resolution is known before fbcon loads. > > > > Signed-off-by: John Keeping > > --- > > Unchanged in v3 > > Unchanged in v2 > > > > drivers/gpu/

[PATCH v2 5/7] drm: Introduce drm_gem_object_{get,put}()

From: Thierry Reding For consistency with other reference counting APIs in the kernel, add drm_gem_object_get() and drm_gem_object_put(), as well as an unlocked variant of the latter, to reference count GEM buffer objects. Compatibility aliases are added to keep existing code working. To help sp

[PATCH v2 7/7] drm: Rename connector list iterator API

From: Thierry Reding Currently the functions that initialize and tear down a connector iterator use the _get() and _put() suffixes. However, these suffixes are typically used by reference counting functions. Make these function names a little more consistent by changing the suffixes to _begin()

[PATCH v2 6/7] drm: Introduce drm_property_blob_{get,put}()

From: Thierry Reding For consistency with other reference counting APIs in the kernel, add drm_property_blob_get() and drm_property_blob_put() to reference count DRM blob properties. Compatibility aliases are added to keep existing code working. To help speed up the transition, all the instances

[PATCH v2 2/7] drm: Introduce drm_mode_object_{get,put}()

From: Thierry Reding For consistency with other reference counting APIs in the kernel, add drm_mode_object_get() and drm_mode_object_put() to reference count DRM mode objects. Compatibility aliases are added to keep existing code working. To help speed up the transition, all the instances of the

[PATCH v2 1/7] drm: Rename drm_mode_object_get()

From: Thierry Reding Subsequent patches will introduce reference counting APIs that are more consistent with similar APIs throughout the Linux kernel. These APIs use the _get() and _put() suffixes and will collide with this existing function. Rename the function to drm_mode_object_add() which is

[PATCH v2 4/7] drm: Introduce drm_framebuffer_{get,put}()

From: Thierry Reding For consistency with other reference counting APIs in the kernel, add drm_framebuffer_get() and drm_framebuffer_put() to reference count DRM framebuffers. Compatibility aliases are added to keep existing code working. To help speed up the transition, all the instances of the

[PATCH v2 3/7] drm: Introduce drm_connector_{get,put}()

From: Thierry Reding For consistency with other reference counting APIs in the kernel, add drm_connector_get() and drm_connector_put() functions to reference count connectors. Compatibility aliases are added to keep existing code working. To help speed up the transition, all the instances of the

[PATCH v2 0/7] drm: Introduce consistent reference counting APIs

From: Thierry Reding This series introduces DRM reference counting APIs that are consistent with other reference counting APIs in the kernel. They are also much shorter. Compatibility aliases are added to keep existing code working and will stay in place until all users of the old APIs are gone.

[PATCH 8/8] Revert "drm/amdgpu: Refactor flip into prepare submit and submit. (v3)"

This reverts commit cb341a319f7e66f879d69af929c3dadfc1a8f31e. --- drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 136 ++-- drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h| 15 --- 2 files changed, 28 insertions(+), 123 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdg

[PATCH 6/8] drm/amd/display: Refactor atomic commit implementation.

From: Andrey Grodzovsky Modify amdgpu_dm_atomic_comit to implement atomic_comit_tail hook. Unify Buffer objects allocation and dealocation for surface updates and page flips. Simplify wait for fences and target_vbank logic for non blockiing commit. Remove hacky update surface to page flip synchro

[PATCH 7/8] drm/amd/display: Refactor headless to use atomic commit.

From: Andrey Grodzovsky Headless mode set needs to be synchronized against outstanding nonblocking commits. This achieved by building atomic state and commiting it. Change-Id: Ie5e778afb33dd5c303a169216a7bb8c2d857037e Signed-off-by: Andrey Grodzovsky --- .../drm/amd/display/amdgpu_dm/amdgpu_dm

[PATCH 5/8] drm/amdgpu: Add a few members to support DAL atomic refactor.

From: Andrey Grodzovsky Signed-off-by: Andrey Grodzovsky --- drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h b/drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h index fda53fa0313f..1e77136d6f0c 100644 --- a/driver

[PATCH 4/8] drm/amd/display: Remove unused define from amdgpu_dm_types

Change-Id: Idfd0d0d6e537eddbc75378ba394b0f36bd89dd50 Signed-off-by: Harry Wentland --- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_types.h | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_types.h b/drivers/gpu/drm/amd/display/amdgpu_dm/a

[PATCH 3/8] drm/amd/display: Use atomic helpers for gamma

We were using set_properties and gamma in a weird way. This change aligns the properties with other drivers and allows us to remove a private gamma flag and reuse atomic helpers for most of this. Change-Id: Ic74b692ee6c6d3e4fd938c6226e65b54075ff983 Signed-off-by: Harry Wentland --- .../drm/amd/d

[PATCH 1/8] drm/amdgpu: Expose mode_config functions for DM

Signed-off-by: Harry Wentland --- drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 4 ++-- drivers/gpu/drm/amd/amdgpu/amdgpu_display.h | 33 + 2 files changed, 35 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/amd/amdgpu/amdgpu_display.h diff --git a/

[PATCH 2/8] drm/amd/display: Use amdgpu mode funcs statically

No need to assign them dynamically. This is much more readable. Change-Id: I2d8a356e8d916800c4553c4e9b19ce42f7f1c391 Signed-off-by: Harry Wentland --- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/amd

[PATCH 0/8] Refactor DC atomic commit and gamma

Resending with CC to dri-devel as per Alex's suggestions. This might be of interest to a wider audience. These patches are first steps of addressing some of the problems in DC's atomic implementation. Please take a look and provide feedback if possible. Our hope is that we can start setting a dire

[PATCH v3 6/6] drm/i915: allow HDMI 2.0 clock rates

Geminilake has a native HDMI 2.0 controller, which is capable of driving clocks upto 594Mhz. This patch updates the max tmds clock limit for the same. V2: rebase V3: rebase Cc: Ander Conselvan De Oliveira Signed-off-by: Shashank Sharma --- drivers/gpu/drm/i915/intel_hdmi.c | 2 ++ 1 file chang

[PATCH v3 5/6] drm/i915: enable scrambling

Geminilake platform sports a native HDMI 2.0 controller, and is capable of driving pixel-clocks upto 594Mhz. HDMI 2.0 spec mendates scrambling for these higher clocks, for reduced RF footprint. This patch checks if the monitor supports scrambling, and if required, enables it during the modeset. V

[PATCH v3 4/6] drm: scrambling support in drm layer

HDMI 2.0 spec mandates scrambling for modes with pixel clock higher than 340 MHz. This patch adds few new functions in drm layer for core drivers to enable/disable scrambling. This patch adds: - A function to detect scrambling support parsing HF-VSDB - A function to check scrambling status runtime

[PATCH v3 0/6] HDMI 2.0: Scrambling in DRM layer

HDMI 2.0 spec defines a method to reduce the RF footprint while operating at higher pixel clocks, which is called Scrambling. Scrambling can be controlled over a new set of I2C registers which are accessible over existing DDC I2C lines, called SCDC register set. This patch series contains 6 patche

[PATCH v3 1/6] drm: Add SCDC helpers

From: Thierry Reding SCDC is a mechanism defined in the HDMI 2.0 specification that allows the source and sink devices to communicate. This commit introduces helpers to access the SCDC and provides the symbolic names for the various registers defined in the specification. V2: Rebase. V3: Added

[PATCH v3 2/6] drm/edid: check for HF-VSDB block

From: Thierry Reding This patch implements a small function that finds if a given CEA db is hdmi-forum vendor specific data block or not. V2: Rebase. V3: Added R-B from Jose. Signed-off-by: Thierry Reding Signed-off-by: Shashank Sharma Reviewed-by: Jose Abreu --- drivers/gpu/drm/drm_edid.c

[PATCH v3 3/6] drm/edid: detect SCDC support in HF-VSDB

This patch does following: - Adds a new structure (drm_hdmi_info) in drm_display_info. This structure will be used to save and indicate if sink supports advanced HDMI 2.0 features - Adds another structure drm_scdc within drm_hdmi_info, to reflect scdc support and capabilities in connected HDM

Re: [PATCH 0/8] Refactor DC atomic commit and gamma

On Thu, Feb 9, 2017 at 4:41 PM, Harry Wentland wrote: > These patches are first steps of addressing some of the problems > in DC's atomic implementation. Please take a look and provide > feedback if possible. Our hope is that we can start setting a > direction on fixing up DC to do atomic correctl

[Bug 99553] Tracker bug for runnning OpenCL applications on Clover

https://bugs.freedesktop.org/show_bug.cgi?id=99553 Vedran Miletić changed: What|Removed |Added Depends on||99764 Referenced Bugs: https://bugs.f

Re: [PATCH 0/6] drm: Introduce consistent reference counting APIs

On Fri, Feb 10, 2017 at 8:29 AM, Jani Nikula wrote: > On Thu, 09 Feb 2017, Thierry Reding wrote: >> On Thu, Feb 09, 2017 at 08:07:41PM +0100, Daniel Vetter wrote: >>> On Thu, Feb 09, 2017 at 07:39:33PM +0200, Jani Nikula wrote: >>> > On Thu, 09 Feb 2017, Daniel Vetter wrote: >>> > > On Thu, Feb

Re: [PATCH v2 1/2] drm/cma-helper: Add multi buffer support for cma fbdev

Hi Daniel, On Thu, Feb 09, 2017 at 06:04:38PM +0100, Daniel Vetter wrote: > On Thu, Feb 02, 2017 at 11:31:56AM +0100, Maxime Ripard wrote: > > From: Xinliang Liu > > > > This patch add a config to support to create multi buffer for cma fbdev. > > Such as double buffer and triple buffer. > > > >

[PATCH v2 2/7] drm/st: Add STM32 LTDC driver

This patch adds support for the STM32 LCD-TFT display controller. Signed-off-by: Yannick Fertre --- drivers/gpu/drm/Kconfig |2 + drivers/gpu/drm/Makefile |1 + drivers/gpu/drm/stm/Kconfig | 14 + drivers/gpu/drm/stm/Makefile |7 + drivers/gpu/drm/stm/drv.c| 232

[PATCH v2 6/7] ARM: dts: stm32: Enable ltdc & simple panel on stm32f429-Eval board

Enable ltdc & enable am-480272h3tmqw-t01h panel. Signed-off-by: Yannick Fertre --- arch/arm/boot/dts/stm32429i-eval.dts | 59 1 file changed, 59 insertions(+) diff --git a/arch/arm/boot/dts/stm32429i-eval.dts b/arch/arm/boot/dts/stm32429i-eval.dts index 601

[PATCH v2 7/7] ARM: configs: stm32: ADD LDTC support

Signed-off-by: Yannick Fertre --- arch/arm/configs/stm32_defconfig | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig index e995209..d6a00b8 100644 --- a/arch/arm/configs/stm32_defconfig +++ b/arch/arm/configs/stm32_defconf

[PATCH v2 1/7] dt-bindings: display: add STM32 LTDC driver

Signed-off-by: Yannick Fertre --- .../devicetree/bindings/display/st,stm32-ltdc.txt | 37 ++ 1 file changed, 37 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/st,stm32-ltdc.txt diff --git a/Documentation/devicetree/bindings/display/st,stm32-ltdc.

[PATCH v2 0/7] STM32 LCD-TFT display controller

Version 2: - Rename driver directory from st to stm. - Rename compatiblity from st,ltdc to st,stm32-ltdc. - Remove compatibility st,display-subsystem. - Rename driver from st-drm to stm-drm. - Rework probe sequence & remove display-subsystem part. - I keep clock name which is necessary for devm_reg

[PATCH v2 5/7] ARM: dts: stm32: Add ltdc support on stm32f429 MCU

Add LTDC (Lcd-tft Display Controller) support. Signed-off-by: Yannick Fertre --- arch/arm/boot/dts/stm32f429.dtsi | 19 ++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi index e4dae0e..00f6681 100

[PATCH v2 4/7] drm/panel: simple: Add support for Ampire AM-480272H3TMQW-T01H

Add simple-panel support for the Ampire AM-480272H3TMQW-T01H, which is a 4.3" WQVGA panel. Signed-off-by: Yannick Fertre --- drivers/gpu/drm/panel/panel-simple.c | 29 + 1 file changed, 29 insertions(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu

[PATCH v2 3/7] dt-bindings: Add Ampire AM-480272H3TMQW-T01H panel

Signed-off-by: Yannick Fertre --- .../bindings/display/panel/ampire,am-480272h3tmqw-t01h.txt | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/ampire,am-480272h3tmqw-t01h.txt diff --git a/Documentation/devicetree/bindings/d

[PATCH v2 2/9] drm/st: Add STM32 LTDC driver

This patch adds support for the STM32 LCD-TFT display controller. Signed-off-by: Yannick Fertre --- drivers/gpu/drm/Kconfig |2 + drivers/gpu/drm/Makefile |1 + drivers/gpu/drm/stm/Kconfig | 14 + drivers/gpu/drm/stm/Makefile |7 + drivers/gpu/drm/stm/drv.c| 232

[PATCH v2 9/9] ARM: configs: stm32: ADD LDTC support

Signed-off-by: Yannick Fertre --- arch/arm/configs/stm32_defconfig | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig index e995209..d6a00b8 100644 --- a/arch/arm/configs/stm32_defconfig +++ b/arch/arm/configs/stm32_defconf

[PATCH v2 7/9] ARM: dts: stm32: Add ltdc support on stm32f429 MCU

Add LTDC (Lcd-tft Display Controller) support. Signed-off-by: Yannick Fertre --- arch/arm/boot/dts/stm32f429.dtsi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi index 47351e2..00f6681 100644 --- a/arch/

[PATCH v2 1/9] dt-bindings: display: add STM32 LTDC driver

Signed-off-by: Yannick Fertre --- .../devicetree/bindings/display/st,stm32-ltdc.txt | 37 ++ 1 file changed, 37 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/st,stm32-ltdc.txt diff --git a/Documentation/devicetree/bindings/display/st,stm32-ltdc.

[PATCH v2 5/9] drm/panel: simple: Add support for Ampire AM-480272H3TMQW-T01H

Add simple-panel support for the Ampire AM-480272H3TMQW-T01H, which is a 4.3" WQVGA panel. Signed-off-by: Yannick Fertre --- drivers/gpu/drm/panel/panel-simple.c | 29 + 1 file changed, 29 insertions(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu

[PATCH v2 6/9] ARM: dts: stm32: Add ltdc support on stm32f429 MCU

Add LTDC (Lcd-tft Display Controller) support. Signed-off-by: Yannick Fertre --- arch/arm/boot/dts/stm32f429.dtsi | 18 +- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi index e4dae0e..47351e2 1006

[PATCH v2 4/9] dt-bindings: Add Ampire AM-480272H3TMQW-T01H panel

Signed-off-by: Yannick Fertre --- .../bindings/display/panel/ampire,am-480272h3tmqw-t01h.txt | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/ampire,am-480272h3tmqw-t01h.txt diff --git a/Documentation/devicetree/bindings/d

[PATCH v2 3/9] drm/st: Add STM32 LTDC driver

This patch adds support for the STM32 LCD-TFT display controller. Signed-off-by: Yannick Fertre --- drivers/gpu/drm/stm/ltdc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/gpu/drm/stm/ltdc.c index 0a393e2..148607d 100644 --- a/drive

[PATCH v2 0/9] STM32 LCD-TFT display controller

Version 2: - Rename driver directory from st to stm. - Rename compatiblity from st,ltdc to st,stm32-ltdc. - Remove compatibility st,display-subsystem. - Rename driver from st-drm to stm-drm. - Rework probe sequence & remove display-subsystem part. - I keep clock name which is necessary for devm_reg

[PATCH v2 8/9] ARM: dts: stm32: Enable ltdc & simple panel on stm32f429-Eval board

Enable ltdc & enable am-480272h3tmqw-t01h panel. Signed-off-by: Yannick Fertre --- arch/arm/boot/dts/stm32429i-eval.dts | 59 1 file changed, 59 insertions(+) diff --git a/arch/arm/boot/dts/stm32429i-eval.dts b/arch/arm/boot/dts/stm32429i-eval.dts index 601

Re: [PATCH 0/6] drm: Introduce consistent reference counting APIs

Am 08.02.2017 um 19:24 schrieb Thierry Reding: From: Thierry Reding This series introduces DRM reference counting APIs that are consistent with other reference counting APIs in the kernel. They are also much shorter. Compatibility aliases are added to keep existing code working and will stay in

[Bug 99747] Problems with mesa 13.0.x and ubuntu 17.04

https://bugs.freedesktop.org/show_bug.cgi?id=99747 --- Comment #4 from APoliTech --- But upgrading to llvm-toolchain-3.9 (1:3.9.1-4ubuntu3) fixed "The problem is that all the pictures that i open on this os i will see them blue-is (look at the pics)" -- You are receiving this mail because: Yo

[Bug 99747] Problems with mesa 13.0.x and ubuntu 17.04

https://bugs.freedesktop.org/show_bug.cgi?id=99747 --- Comment #3 from APoliTech --- sudo apt-cache policy libllvm3.9 libllvm3.9: Installed: 1:3.9.1-2ubuntu1 Candidate: 1:3.9.1-2ubuntu1 Version table: *** 1:3.9.1-2ubuntu1 500 500 http://ro.archive.ubuntu.com/ubuntu zesty/main amd

Re: [PATCH v2 2/2] drm/fb_helper: implement ioctl FBIO_WAITFORVSYNC

On Thu, Feb 02, 2017 at 11:31:57AM +0100, Maxime Ripard wrote: > From: Stefan Christ > > Implement legacy framebuffer ioctl FBIO_WAITFORVSYNC in the generic > framebuffer emulation driver. Legacy framebuffer users like non kms/drm > based OpenGL(ES)/EGL implementations may require the ioctl to >

[Bug 99762] "Black Mesa" not launching

https://bugs.freedesktop.org/show_bug.cgi?id=99762 Samuel Pitoiset changed: What|Removed |Added Summary|black mesa not launching|"Black Mesa" not launching -- You are

[Bug 99762] black mesa not launching

https://bugs.freedesktop.org/show_bug.cgi?id=99762 --- Comment #1 from Samuel Pitoiset --- At first look, I thought "Black Mesa" was a joke but it's not. Funny name! :-) According to https://steamcommunity.com/app/362890/discussions/0/312265327168384714/, the Linux version seems to have various

[Bug 99762] black mesa not launching

https://bugs.freedesktop.org/show_bug.cgi?id=99762 Bug ID: 99762 Summary: black mesa not launching Product: Mesa Version: 13.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: mediu

[Bug 97879] [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)

https://bugs.freedesktop.org/show_bug.cgi?id=97879 --- Comment #77 from freedesk...@bremsspur.org --- (In reply to Michel Dänzer from comment #75) > (In reply to Clemens Eisserer from comment #73) > > just to be curious, does it actually map the buffer with the READ flag? > > According to Timothe

Re: [PATCH] drm/i915: Fix not finding the VBT when it overlaps with OPREGION_ASLE_EXT

On Fri, 10 Feb 2017, Hans de Goede wrote: > On 06-02-17 08:04, Jani Nikula wrote: >> First, I want a big fat warning comment about what's going on >> here. Otherwise someone's bound to "fix" this later on. > > Done for v2, which I will send shortly. Thanks. >> Second, per the spec, the ASLE ext

[PATCH v2] drm/i915: Fix not finding the VBT when it overlaps with OPREGION_ASLE_EXT

If there is no OPREGION_ASLE_EXT then a VBT stored in mailbox #4 may use the ASLE_EXT parts of the opregion. Adjust the vbt_size calculation for a vbt in mailbox #4 for this. This fixes the driver not finding the VBT on a jumper ezpad mini3 cherrytrail tablet and on a ACER SW5_017 machine. Cc: st

Re: [PATCH] drm/i915: Fix not finding the VBT when it overlaps with OPREGION_ASLE_EXT

Hi, On 06-02-17 08:04, Jani Nikula wrote: On Sun, 25 Dec 2016, Hans de Goede wrote: If there is no OPREGION_ASLE_EXT then a VBT stored in mailbox #4 may use the ASLE_EXT parts of the opregion. Adjust the vbt_size calculation for a vbt in mailbox #4 for this. This fixes the driver not finding

[Bug 99136] Blood Effects Total War: Warhammer

https://bugs.freedesktop.org/show_bug.cgi?id=99136 --- Comment #25 from siyia --- This is what it spams when the bug happens apitrace: warning: glNamedBufferStorage: MAP_NOTIFY_EXPLICIT_BIT_VMWX set w/o MAP_PERSISTENT_BIT -- You are receiving this mail because: You are the assignee for the bug

[PATCH v3 11/12] drm/i915: Add intel_uncore_suspend / resume functions

Rename intel_uncore_early_sanitize to intel_uncore_resume, dropping the (always true) restore_forcewake argument and add a new intel_uncore_resume function to replace the intel_uncore_forcewake_reset(dev_priv, false) calls done from the suspend / runtime_suspend functions and make intel_uncore_forc

[PATCH v3 10/12] i2c: designware-baytrail: Call pmic_bus_access_notifier_chain

Call the iosf_mbi pmic_bus_access_notifier_chain on bus acquire / release. BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=155241 Signed-off-by: Hans de Goede Tested-by: tagorereddy Reviewed-by: Andy Shevchenko Acked-by: Wolfram Sang Acked-by: Jarkko Nikula --- Changes in v2: -Spelling:

[PATCH v3 12/12] drm/i915: Listen for PMIC bus access notifications

Listen for PMIC bus access notifications and get FORCEWAKE_ALL while the bus is accessed to avoid needing to do any forcewakes, which need PMIC bus access, while the PMIC bus is busy: This fixes errors like these showing up in dmesg, usually followed by a gfx or system freeze: [drm:fw_domains_get

[PATCH v3 09/12] i2c: designware-baytrail: Acquire P-Unit access on bus acquire

Acquire P-Unit access to stop others from accessing the P-Unit while the PMIC i2c bus is in use. This is necessary because accessing the P-Unit from the kernel may result in the P-Unit trying to access the PMIC i2c bus, which results in a hang when it happens while we own the PMIC i2c bus semaphore

[PATCH v3 06/12] i2c: designware-baytrail: Disallow the CPU to enter C6 or C7 while holding the punit semaphore

On my cherrytrail tablet with axp288 pmic, just doing a bunch of repeated reads from the pmic, e.g. "i2cdump -y 14 0x34" would lookup the tablet in 1 - 3 runs guaranteed. This seems to be causes by the cpu trying to enter C6 or C7 while we hold the punit bus semaphore, at which point everything ju

[PATCH v3 07/12] i2c: designware-baytrail: Fix race when resetting the semaphore

Use iosf_mbi_modify instead of iosf_mbi_read + iosf_mbi_write so that we keep the iosf_mbi_lock locked during the read-modify-write done to reset the semaphore. Signed-off-by: Hans de Goede Reviewed-by: Andy Shevchenko Acked-by: Jarkko Nikula Acked-by: Wolfram Sang --- Changes in v5: -New patc

[PATCH v3 08/12] i2c: designware-baytrail: Add support for cherrytrail

The cherrytrail punit has the pmic i2c bus access semaphore at a different register address. Signed-off-by: Hans de Goede Reviewed-by: Takashi Iwai Tested-by: Takashi Iwai Reviewed-by: Andy Shevchenko Acked-by: Jarkko Nikula Acked-by: Wolfram Sang --- Changes in v2: -Adjust for accessor_flag

[PATCH v3 05/12] i2c: designware-baytrail: Only check iosf_mbi_available() for shared hosts

If (!shared_host) simply return 0, this avoids delaying the probe if iosf_mbi_available() returns false when an i2c bus is not using the punit semaphore. Also move the if (!iosf_mbi_available()) check to above the dev_info, so that we do not repeat the dev_info on every probe until iosf_mbi_availa

[PATCH v3 03/12] i2c: designware: Rename accessor_flags to flags

Rename accessor_flags to flags, so that we can use the field for other flags too. This is a preparation patch for adding cherrytrail support to the punit semaphore code. Signed-off-by: Hans de Goede Reviewed-by: Andy Shevchenko Acked-by: Jarkko Nikula Tested-by: Takashi Iwai Acked-by: Wolfram

[PATCH v3 02/12] x86/platform/intel/iosf_mbi: Add a PMIC bus access notifier

Some drivers may need to acquire P-Unit managed resources from interrupt context, where they cannot call iosf_mbi_punit_acquire(). This commit adds a notifier chain which allows a driver to get notified (in a process context) before other drivers start accessing the PMIC bus, so that the driver ca

[PATCH v3 04/12] i2c: designware-baytrail: Pass dw_i2c_dev into helper functions

Pass dw_i2c_dev into the helper functions, this is a preparation patch for the punit semaphore fixes done in the other patches in this set. Signed-off-by: Hans de Goede Reviewed-by: Takashi Iwai Tested-by: Takashi Iwai Reviewed-by: Andy Shevchenko Acked-by: Jarkko Nikula Acked-by: Wolfram San

[PATCH v3 01/12] x86/platform/intel/iosf_mbi: Add a mutex for P-Unit access

One some systems the P-Unit accesses the PMIC to change various voltages through the same bus as other kernel drivers use for e.g. battery monitoring. If a driver sends requests to the P-Unit which require the P-Unit to access the PMIC bus while another driver is also accessing the PMIC bus variou

[PATCH v3 00/12] coordinate cht i2c-pmic and i915-punit accesses

Hi All, Here is v3 of my cht i2c-pmic and i915-punit access coordination patchset. New in this version is the dropping of the punit_acquire / _release calls around punit accesses in the i915 driver, these seem to be unnecessary in this case acquiring the pmic-bus semaphore in the punit seems to be

Re: [PATCH v2 13/13] drm/i915: Acquire P-Unit access when modifying P-Unit settings

Hi, On 30-01-17 16:11, Ville Syrjälä wrote: On Mon, Jan 30, 2017 at 04:02:19PM +0100, Hans de Goede wrote: Hi, On 30-01-17 14:10, Ville Syrjälä wrote: On Sat, Jan 28, 2017 at 06:18:45PM +0100, Hans de Goede wrote: Hi, On 01/28/2017 05:25 PM, Hans de Goede wrote: Hi, On 01/27/2017 02:51 PM

[PULL] sti-drm-next-2017-02-10

Hi Dave, Here is an update of the STI drm driver containing; - remove deprecated stih416 chip functionnalities - fix issues met around gdp panes - fix STI driver unbind procedure - DVI/HDMI mode is automatically detected - allow fps statisitics resetting Regard, Vincent The following changes si

[Bug 98869] Electronic Super Joy graphic artefacts (regression,bisected)

https://bugs.freedesktop.org/show_bug.cgi?id=98869 --- Comment #20 from cosiek...@o2.pl --- Yes of course. I have tested this patch and it resolved the problem :) Thank you very much!!! -- You are receiving this mail because: You are the assignee for the bug._