Re: [RFC v3 5/8] drm/msm: update cursors asynchronously through atomic

On 05/17/2017 05:05 PM, Daniel Vetter wrote: On Wed, May 17, 2017 at 10:56:25AM +0530, Archit Taneja wrote: Hi, On 05/16/2017 08:14 PM, Archit Taneja wrote: On 5/13/2017 12:40 AM, Gustavo Padovan wrote: From: Gustavo Padovan Add support to async updates

Re: [PATCH 3/4] drm/dp: start a DPCD based DP sink/branch device quirk database

On 18.05.2017 13:10, Jani Nikula wrote: > Face the fact, there are Display Port sink and branch devices out there > in the wild that don't follow the Display Port specifications, or they > have bugs, or just otherwise require special treatment. Start a common > quirk database the drivers can query

linux-next: manual merge of the drm-intel tree with the drm tree

Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/intel_dp_mst.c between commit: f424f55e3177 ("drm/i915: Track MST link bandwidth") from the drm tree and commit: 3d65a735d834 ("drm/i915/mst: use max link not sink lane count") from the

Re: [PATCH v3 01/21] clk: divider: Make divider_round_rate take the parent clock

On 05/17, Maxime Ripard wrote: > So far, divider_round_rate only considers the parent clock returned by > clk_hw_get_parent. > > This works fine on clocks that have a single parents, this doesn't work on > muxes, since we will only consider the first parent, while other parents > may totally be

[Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)

https://bugs.freedesktop.org/show_bug.cgi?id=99851 --- Comment #34 from Michel Dänzer --- For any commits that you can't test, run "git bisect skip". Eventually, it will either identify the first bad commit or specify the minimum set of candidates. -- You are receiving this

[Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)

https://bugs.freedesktop.org/show_bug.cgi?id=99851 Michel Dänzer changed: What|Removed |Added Attachment #131410|text/x-log |text/plain

[PATCH v4 07/10] drm/bridge/synopsys: dw-hdmi: Use bridge->mode_valid() callback

Now that we have a callback to check if bridge supports a given mode we can use it in Synopsys Designware HDMI bridge so that we restrict the number of probbed modes to the ones we can actually display. Also, there is no need to use mode_fixup() callback as mode_valid() will handle the mode

[PATCH] drm/cirrus: implement create_handle for framebuffers

This fixes the DRM_IOCTL_MODE_GETFB ioctl for cirrus so that it returns an actual handle instead of failing with ENODEV. Tested in a QEMU VM with "-vga cirrus" by running this script: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/client/bin/screenshot.py

[PATCH v4 04/10] drm: Use mode_valid() in atomic modeset

This patches makes use of the new mode_valid() callbacks introduced previously to validate the full video pipeline when modesetting. This calls the connector->mode_valid(), encoder->mode_valid(), bridge->mode_valid() and crtc->mode_valid() so that we can make sure that the mode will be accepted

[PATCH v4 10/10] drm: vc4: Use crtc->mode_valid() and encoder->mode_valid() callbacks

Now that we have a callback to check if crtc and encoder supports a given mode we can use it in vc4 so that we restrict the number of probbed modes to the ones we can actually display. Also, remove the mode_fixup() calls as these are no longer needed because mode_valid() will be called before.

Re: [Intel-gfx] [PATCH 3/4] drm/dp: start a DPCD based DP sink/branch device quirk database

On Thu, 2017-05-18 at 14:10 +0300, Jani Nikula wrote: > Face the fact, there are Display Port sink and branch devices out there > in the wild that don't follow the Display Port specifications, or they > have bugs, or just otherwise require special treatment. Start a common > quirk database the

[PATCH v4 02/10] drm: Introduce drm_bridge_mode_valid()

Introduce a new helper function which calls mode_valid() callback for all bridges in an encoder chain. Signed-off-by: Jose Abreu Reviewed-by: Daniel Vetter Cc: Carlos Palminha Cc: Alexey Brodkin Cc:

[PATCH v4 06/10] drm/bridge: analogix-anx78xx: Use bridge->mode_valid() callback

Now that we have a callback to check if bridge supports a given mode we can use it in Analogix bridge so that we restrict the number of probbed modes to the ones we can actually display. Also, there is no need to use mode_fixup() callback as mode_valid() will handle the mode validation. NOTE:

[PATCH v4 08/10] drm/arm: malidp: Use crtc->mode_valid() callback

Now that we have a callback to check if crtc supports a given mode we can use it in malidp so that we restrict the number of probbed modes to the ones we can actually display. Also, remove the mode_fixup() callback as this is no longer needed because mode_valid() will be called before. NOTE: Not

[PATCH -next] drm/i915: Fix return value check in kfence selftests

From: Wei Yongjun Fix the return value check which testing the wrong variable. Signed-off-by: Wei Yongjun --- drivers/gpu/drm/i915/selftests/i915_sw_fence.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH v4 05/10] drm: arc: Use crtc->mode_valid() callback

Now that we have a callback to check if crtc supports a given mode we can use it in arcpgu so that we restrict the number of probbed modes to the ones we can actually display. This is specially useful because arcpgu crtc is responsible to set a clock value in the commit() stage but unfortunatelly

[PATCH v4 00/10] Introduce new mode validation callbacks

This series is a follow up from the discussion at [1]. We start by introducing crtc->mode_valid(), encoder->mode_valid() and bridge->mode_valid() callbacks which will be used in followup patches and also by cleaning the documentation a little bit. This patch is available at [2] and the series

[PATCH v4 03/10] drm: Use new mode_valid() helpers in connector probe helper

This changes the connector probe helper function to use the new encoder->mode_valid(), bridge->mode_valid() and crtc->mode_valid() helper callbacks to validate the modes. The new callbacks are optional so the behaviour remains the same if they are not implemented. If they are, then the code loops

Re: [Intel-gfx] [PATCH v8 1/5] drm/i915: Drop AUX backlight enable check for backlight control

On Wed, 2017-05-17 at 14:04 -0700, Puthikorn Voravootivat wrote: > > On Wed, May 17, 2017 at 1:09 PM, Pandiyan, Dhinakaran > wrote: > > > From: Puthikorn Voravootivat [put...@google.com] on behalf of

[PATCH v4 01/10] drm: Add drm_{crtc/encoder/connector}_mode_valid()

Add a new helper to call crtc->mode_valid, connector->mode_valid and encoder->mode_valid callbacks. Suggested-by: Ville Syrjälä Signed-off-by: Jose Abreu Reviewed-by: Daniel Vetter Reviewed-by: Andrzej Hajda

[PATCH v4 09/10] drm/atmel-hlcdc: Use crtc->mode_valid() callback

Now that we have a callback to check if crtc supports a given mode we can use it in atmel-hlcdc so that we restrict the number of probbed modes to the ones we can actually display. Also, remove the mode_fixup() callback as this is no longer needed because mode_valid() will be called before.

Re: [PATCH v2] drm/pl111: Register the clock divider and use it.

On 05/08, Eric Anholt wrote: > This is required for the panel to work on bcm911360, where CLCDCLK is > the fixed 200Mhz AXI41 clock. The rate set is still passed up to the > CLCDCLK, for platforms that have a settable rate on that one. > > v2: Set SET_RATE_PARENT (caught by Linus Walleij),

[Bug 195321] nouveau?/DRI3?: dual monitors unusable without running compton --paint-on-overlay

https://bugzilla.kernel.org/show_bug.cgi?id=195321 --- Comment #3 from Jimi (jimijames.b...@gmail.com) --- Hello? I still can't upgrade my kernel until this gets fixed. -- You are receiving this mail because: You are watching the assignee of the bug.

Re: [RFC 7/7] drm/vc4: update cursors asynchronously through atomic

Sorry about the spam, but the previous reply was intended for [RFC v3 7/8] drm/vc4: update cursors asynchronously through atomic On 2017-05-18 06:52 PM, Robert Foss wrote: Hey, I ran the series on a RPi2 and the cursor seems to behave correctly. Tested-by: Robert Foss

Re: [RFC v3 7/8] drm/vc4: update cursors asynchronously through atomic

Hey, I just tested this patch on a RPi2, and the cursor behaves correctly with no unexpected errors. Tested-by: Robert Foss On 2017-05-12 03:10 PM, Gustavo Padovan wrote: From: Gustavo Padovan Add support to async updates of

Re: [RFC 7/7] drm/vc4: update cursors asynchronously through atomic

Hey, I ran the series on a RPi2 and the cursor seems to behave correctly. Tested-by: Robert Foss On 2017-04-09 08:24 PM, Gustavo Padovan wrote: From: Gustavo Padovan Add support to async updates of cursors by using the new atomic

Re: [PATCH v1 2/3] dt-bindings: display: Add STM32 DSI host driver

On Fri, May 12, 2017 at 04:56:28PM +0200, Philippe CORNU wrote: > This patch adds documentation of device tree bindings for the STM32 > DSI host driver based on the Synopsys DW MIPI DSI driver from Rockchip. > > Signed-off-by: Philippe CORNU > --- >

[PATCH v8 3/5] nouveau/hwmon: Remove old code, add .write/.read operations

This patch removes old code related to the old api and transforms the functions for the new api. It also adds the .write and .read operations. Signed-off-by: Oscar Salvador Reviewed-by: Martin Peres ---

[PATCH v8 5/5] nouveau/hwmon: Change permissions to numeric

This patch replaces the symbolic permissions with the numeric ones. Signed-off-by: Oscar Salvador Reviewed-by: Martin Peres --- drivers/gpu/drm/nouveau/nouveau_hwmon.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff

[PATCH v8 4/5] nouveau/hwmon: expose the auto_point and pwm_min/max attrs

This patch creates a special group attributes for attrs like "*auto_point*". We check if we have support for them, and if we do, we gather them all in an attribute_group's structure which is the parameter regarding special groups of hwmon_device_register_with_info We also do the same for

[PATCH v8 2/5] nouveau/hwmon: Add nouveau_hwmon_ops structure with .is_visible/.read_string

This patch introduces the nouveau_hwmon_ops structure, sets up .is_visible and .read_string operations and adds all the functions for these operations. This is also a preparation for the next patches, where most of the work is being done. This code doesn't interacture with the old one. It's just

[PATCH v8 1/5] nouveau/hwmon: Add config for all sensors and their settings

This is a preparation for the next patches. It just adds the sensors with their possible configurable settings and then fills the struct hwmon_channel_info with all this information. Signed-off-by: Oscar Salvador Reviewed-by: Martin Peres

[PATCH v8 0/5] replace hwmon_device_register for hwmon_device_register_with_info

This v8 fixes removes dummy functions which only had a return and moves the code into the switch statements. Versions: v1 -> v2: * Keep temp attrs as read only v2 -> v3: * Code fix-ups: struct and string as const and add return within switch due to fallthrough *

[Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)

https://bugs.freedesktop.org/show_bug.cgi?id=99851 --- Comment #33 from erhar...@mailbox.org --- Created attachment 131411 --> https://bugs.freedesktop.org/attachment.cgi?id=131411=edit bisect kernel .config -- You are receiving this mail because: You are the assignee for the

[Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)

https://bugs.freedesktop.org/show_bug.cgi?id=99851 --- Comment #32 from erhar...@mailbox.org --- Created attachment 131410 --> https://bugs.freedesktop.org/attachment.cgi?id=131410=edit incomplete bisect.log -- You are receiving this mail because: You are the assignee for the

[Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)

https://bugs.freedesktop.org/show_bug.cgi?id=99851 --- Comment #31 from erhar...@mailbox.org --- Unfortunately my bisect efforts came to a halt as the current kernel won't boot. Early OpenFirmware boot console shows "Kernel panic - not syncing: Couldn't allocate pmd pagetable caches". The G5

[PATCH v2] drm/omap: Implement CTM property for CRTC using OVL managers CPR matrix

Implement CTM color management property for OMAP CRTC using DSS overlay manager's Color Phase Rotation matrix. The CPR matrix does not exactly match the CTM property documentation. On DSS the CPR matrix is applied after gamma table look up. However, it seems stupid to add a custom property just

Re: [PATCH] drm: trivial documentation fix to drm_for_each_connector_iter

Daniel Vetter writes: > On Wed, May 17, 2017 at 03:43:18PM -0300, Gabriel Krisman Bertazi wrote: >> Daniel Vetter writes: >> >> > On Thu, Apr 20, 2017 at 09:38:19PM -0300, Gabriel Krisman Bertazi wrote: >> >> While reading drm_for_each_connector_iter, I

Re: [drm:qxl] BUG: sleeping function called from invalid context - qxl_bo_kmap_atomic_page()...splat

Mike Galbraith writes: > On Mon, 2017-05-08 at 16:48 -0300, Gabriel Krisman Bertazi wrote: > >> Thanks for reporting this. Can you confirm the following patch prevents >> the issue? > > Nope, it still gripes. Oops... Thanks for checking. The following patch fixes the issue for

[PATCH] drm/cirrus: implement create_handle for framebuffers

This fixes the DRM_IOCTL_MODE_GETFB ioctl for cirrus so that it returns an actual handle instead of failing with ENODEV. Tested in a QEMU VM with "-vga cirrus" by running this script: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/client/bin/screenshot.py

[PATCH v4 1/2] drm: Add const to name field declaration in struct drm_prop_enum_list

There is no reason why the name field should not be const, but several why it should. The struct should only be used by drm_property_create_enum() and there the name-field from the struct is passed to drm_property_add_enum(), which takes a const char * as a parameter. Signed-off-by: Jyri Sarha

[PATCH v4 2/2] drm: Add optinal COLOR_ENCODING and COLOR_RANGE properties to drm_plane

Add a standard optional properties to support different non RGB color encodings in DRM planes. COLOR_ENCODING select the supported non RGB color encoding, for instance ITU-R BT.709 YCbCr. COLOR_RANGE selects the value ranges within the selected color encoding. The properties are stored to

[PATCH v4 0/2] drm: Add properties to control YCbCr to RGB conversion

Changes since v3 RFC version: - Add: "drm: Add const to name field declaration in struct drm_prop_enum_list" - Fix typos found by Eric Engestrom - Restructure kernel doc - Add consts to name sting tables - Loop variables from unsigned to signed int - Use len variable to index temporary

[PATCH 1/2] drm/atomic: Consitfy mode parameter to drm_atomic_set_mode_for_crtc()

From: Ville Syrjälä drm_atomic_set_mode_for_crtc() doesn't modify the passed mode, so let's make it const. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/drm_atomic.c | 2 +- include/drm/drm_atomic.h | 2 +- 2 files changed,

[PATCH 2/2] drm/i915: Constify load detect mode

From: Ville Syrjälä Make the mode used for load detection const, and adjust all relevant functions to accept a const mode. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_display.c | 12 ++--

[PATCH] drm/radeon: Fix oops upon driver load on PowerXpress laptops

Nicolai Stange reports the following oops which is caused by dereferencing rdev->pdev before it's subsequently set by radeon_device_init(). Fix it. BUG: unable to handle kernel NULL pointer dereference at 07cb IP: radeon_driver_load_kms+0xeb/0x230 [radeon] PGD 0 P4D 0

[PATCH] drm/amd/display: default spd packet to invalid

Signed-off-by: Jeff Smith --- All of the encoder_info_frame's info packets are initialized to invalid in resource_build_info_frame except for spd. This appears to be simply an oversight. drivers/gpu/drm/amd/display/dc/core/dc_resource.c | 1 + 1 file changed, 1 insertion(+)

[Bug 101029] notebook does not work when not booted using nomodeset AMD APU

https://bugs.freedesktop.org/show_bug.cgi?id=101029 --- Comment #22 from Craig --- in that case, when will this patch be applied permanently in a kernel versus having to use the patch? I will be attempting to apply the patch soon and verify as well on the Ubuntu side. --

Re: [PATCH v1 1/3] drm/stm: ltdc: Add bridge support

Philippe CORNU writes: > Add the bridge support, used by DSI host and HDMI/LVDS bridges. > > Signed-off-by: Philippe CORNU > @@ -987,19 +1024,36 @@ static struct drm_panel *ltdc_get_panel(struct > drm_device *ddev) > > port =

[Bug 101029] notebook does not work when not booted using nomodeset AMD APU

https://bugs.freedesktop.org/show_bug.cgi?id=101029 --- Comment #21 from Jan Vesely --- I have the same problem on carrizo+iceland nb (reported at [0,1]). I can confirm that the linked patch applied on top of 4.10.x fixes boot, and the machine can run 3d applications

Re: [PATCH] drm/amd/powerplay: fix a signedness bugs

Reviewed-by: Eric Huang On 2017-05-16 10:42 AM, Dan Carpenter wrote: Smatch complains about a signedness bug here: vega10_hwmgr.c:4202 vega10_force_clock_level() warn: always true condition '(i >= 0) => (0-u32max >= 0)' Fixes: 7b52db39a4c2

[PATCH v3 05/16] drm/i810: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/i810/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/i810/Makefile

[PATCH v3 07/16] drm/mga: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/mga/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/mga/Makefile

[PATCH v3 11/16] drm/sis: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/sis/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/sis/Makefile

[PATCH v3 00/16] gpu/drm: remove -Iinclude/drm compiler flags from Makefile

Many Makefiles needed to add -Iinclude/drm as an include path, but the right thing to do is to include headers in the form #include This series fixes the source files, then rip off -Iinclude/drm flags. V3: rebased on commit bb2af9bda33 (drm-misc-next) Masahiro Yamada (16): drm/vc4: fix

[PATCH 4/5] ASoC: hdmi-codec: add .get_dai_id support

From: Kuninori Morimoto ALSA SoC needs to know connected DAI ID for probing. It is not a big problem if device/driver was only for sound, but getting DAI ID will be difficult if device includes both Video/Sound, like HDMI. To solve this issue, this patch adds

[PATCH v3 01/16] drm/vc4: fix include notation and remove -Iinclude/drm flag

Include instead of relative path from include/drm, then remove the -Iinclude/drm compiler flag. While we are here, use <...> instead of "..." for include/linux/*.h and include/sound/*.h headers too. Signed-off-by: Masahiro Yamada --- Changes in v3: - Rebase

Re: [PATCH v2 15/29] drm/vc4: fix include notation and remove -Iinclude/drm flag

Hi Daniel, 2017-05-17 21:40 GMT+09:00 Daniel Vetter : > On Mon, Apr 24, 2017 at 01:50:33PM +0900, Masahiro Yamada wrote: >> Include instead of relative path from include/drm, then >> remove the -Iinclude/drm compiler flag. >> >> While we are here, use <...> instead of "..." for

[PATCH 2/5] ASoC: simple-card-utils: support snd_soc_get_dai_id()

From: Kuninori Morimoto ALSA SoC needs to know connected DAI ID for detecting. It is not a big problem if device/driver was only for sound, but getting DAI ID will be difficult if device includes both Video/Sound, like HDMI. To solve this issue, this patch adds

[PATCH v3 15/16] drm/vgem: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/vgem/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/vgem/Makefile

Re: [PATCH v4 4/4] drm: rcar-du: Register a completion callback with VSP1

Em Fri, 5 May 2017 16:21:10 +0100 Kieran Bingham escreveu: > Currently we process page flip events on every display interrupt, > however this does not take into consideration the processing time needed > by the VSP1 utilised in the pipeline. > >

Re: [PATCH] drm/atmel-hlcdc: Fix output initialization

On 18/05/2017 at 14:35:21 +0200, Boris Brezillon wrote: > drm_of_find_panel_or_bridge() is expecting np to point to the encoder > node, not the bridge or panel this encoder is feeding. > Moreover, the endpoint parameter passed to drm_of_find_panel_or_bridge() > is always set to zero, which

[PATCH] drm/stm: add COMPILE_TEST to Kconfig

Add COMPILE_TEST for the compilation test coverage. Signed-off-by: Masahiro Yamada --- drivers/gpu/drm/stm/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/stm/Kconfig b/drivers/gpu/drm/stm/Kconfig index 2c4817f..722ad11

[PATCH v3 13/16] drm/tdfx: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/tdfx/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/tdfx/Makefile

[PATCH v3 06/16] drm/i2c: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/i2c/Makefile | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/gpu/drm/i2c/Makefile

[PATCH v3 09/16] drm/r128: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/r128/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/r128/Makefile

[PATCH v3 08/16] drm/omap: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/omapdrm/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/omapdrm/Makefile

[PATCH v3 03/16] drm/vmwgfx: fix include notation and remove -Iinclude/drm flag

Include instead of relative path from include/drm, then remove the -Iinclude/drm compiler flag. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/vmwgfx/Makefile | 3 --- drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 3 ++-

Re: [PATCH] gpu: host1x: Refactor/fix channel allocation code

On 18.05.2017 14:42, Dmitry Osipenko wrote: On 20.03.2017 21:44, Mikko Perttunen wrote: ... struct host1x_channel *host1x_channel_request(struct device *dev) { struct host1x *host = dev_get_drvdata(dev->parent); + struct host1x_channel_list *chlist = >channel_list;

Re: [PATCH] gpu: host1x: Refactor/fix channel allocation code

On 18.05.2017 14:55, Mikko Perttunen wrote: > On 18.05.2017 14:42, Dmitry Osipenko wrote: >> On 20.03.2017 21:44, Mikko Perttunen wrote: >>> ... >>> struct host1x_channel *host1x_channel_request(struct device *dev) >>> { >>> struct host1x *host = dev_get_drvdata(dev->parent); >>> +

[PATCH v3 10/16] drm/savage: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/savage/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/savage/Makefile

[PATCH 0/5] ASoC: add HDMI sound support for Codec

Hi Mark, Archit These supports HDMI sound for Codec. Now, SYNOPSYS dw-hdmi-i2s-audio driver is supporting HDMI I2S and is using hdmi-codec driver. Now, ALSA SoC supports OF-graph DT style, this means V4L2/ALSA SoC can share same DT bindings. But 1 issue is that ALSA SoC side needs to adjust port

Re: [PATCH] gpu: host1x: Refactor/fix channel allocation code

On 20.03.2017 21:44, Mikko Perttunen wrote: > This is largely a rewrite of the Host1x channel allocation > code in channel.c, bringing several changes: > > - The previous code could deadlock due to an interaction > between the 'reflock' mutex and CDMA timeout handling. > This gets rid of the

[PATCH 5/5] drm: dw-hdmi-i2s: add .get_dai_id callback for ALSA SoC

From: Kuninori Morimoto ALSA SoC needs to know connected DAI ID for probing. It is not a big problem if device/driver was only for sound, but getting DAI ID will be difficult if device includes both Video/Sound, like HDMI. To solve this issue, this patch adds

[PATCH] drm/amd: include instead of "linux/delay.h"

Use <...> notation to include headers located in include/linux. While we are here, tweak the includes order a bit to sort them alphabetically. Signed-off-by: Masahiro Yamada --- drivers/gpu/drm/amd/powerplay/hwmgr/hwmgr.c| 4 ++--

[PATCH v3 14/16] drm/udl: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/udl/Makefile | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/gpu/drm/udl/Makefile

[PATCH v3 04/16] drm/gma500: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/gma500/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/gma500/Makefile

[PATCH 1/5] ASoC: add snd_soc_get_dai_id() function

From: Kuninori Morimoto ALSA SoC needs to know connected DAI ID for detecting. It is not a big problem if device/driver was only for sound, but getting DAI ID will be difficult if device includes both Video/Sound, like HDMI. To solve this issue, this patch adds

[PATCH v3 02/16] drm/virtio: fix include notation and remove -Iinclude/drm flag

Include instead of relative path from include/drm, then remove the -Iinclude/drm compiler flag. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/virtio/Makefile | 2 -- drivers/gpu/drm/virtio/virtgpu_debugfs.c | 2 +-

[PATCH v3 16/16] drm/via: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/via/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/via/Makefile

[PATCH v3 12/16] drm/stm: remove unneeded -Iinclude/drm compiler flag

With the include directives under include/drm/ fixed, this flag is no longer needed. Signed-off-by: Masahiro Yamada --- Changes in v3: None drivers/gpu/drm/stm/Makefile | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/gpu/drm/stm/Makefile

[PATCH 3/5] ASoC: hdmi-codec: remove multi detection support

From: Kuninori Morimoto DesignWare HDMI driver (= dw-hdmi) is supporting HDMI sound, and its probe function was calling sound binding function multiple times as same HDMI device different port. Because of this behavior, commit 9731f82d601 ("ASoC: hdmi-codec:

Re: (radeon?) WARNING: drivers/gpu/drm/drm_irq.c:1195 drm_vblank_put (v4.11-12441-g56868a4)

2017-05-11 5:51 GMT+03:00 Michel Dänzer : > On 11/05/17 04:33 AM, Tommi Rantala wrote: >> Complete kernel log: >> http://termbin.com/dzy5 >> >> [ 249.952546] [ cut here ] >> [ 249.952593] WARNING: CPU: 5 PID: 0 at >>

Re: [PATCH v3] drm: Add DRM_MODE_ROTATE_ and DRM_MODE_REFLECT_ to UAPI

vmwgfx part: Reviewed-by: Sinclair Yeh On Wed, May 17, 2017 at 09:39:11PM -0400, Robert Foss wrote: > Add DRM_MODE_ROTATE_ and DRM_MODE_REFLECT_ defines to the UAPI > as a convenience. > > Ideally the DRM_ROTATE_ and DRM_REFLECT_ property ids are looked up > through the atomic

[Bug 100437] IO_PAGE_FAULT is spammed in dmesg

https://bugs.freedesktop.org/show_bug.cgi?id=100437 --- Comment #8 from Öyvind Saether --- Motherboard: MSI-A88X-G45-GAMING APU: AMD A8-7600 Graphics card: MSI RX 470 8GB Kernel: 4.11.0-2.fc26.x86_64 Screens: 3 (1080 1440 1080) I can confirm that on cold boot I too get

Re: [PATCH 2/2 -v2] drm: drop drm_[cm]alloc* helpers

On Thu, May 18, 2017 at 10:16:38AM +0200, Christian König wrote: > Am 17.05.2017 um 14:23 schrieb Michal Hocko: > > As it turned out my allyesconfig on x86_64 wasn't sufficient and 0day > > build machinery found a failure on arm architecture. It was clearly a > > typo. Now I have pushed this to my

[GIT PULL v2] drm/hdlcd: fix for calculation of scanout address

Gentle ping on this. Thanks, Liviu Hi Dave, I'm not sure what is the best tree to target this, probably v4.12-rc1 if it is too late to make it into the pull request for this merge window. Just a patch that has been in linux-next for a very long time due to lack of feedback and me going on

Re: [PATCH 3/4] drm/dp: start a DPCD based DP sink/branch device quirk database

On 05/18/2017 04:10 AM, Jani Nikula wrote: Face the fact, there are Display Port sink and branch devices out there in the wild that don't follow the Display Port specifications, or they have bugs, or just otherwise require special treatment. Start a common quirk database the drivers can query

[PULL] drm-misc-fixes for 4.12

Hi Dave, 2 fixes for you, one fixes a link error that seems to have been lurking for a while, but aggrevated by rc1. The second patch fixes a bug introduced in the find_panel_or_bridge cleanup set. drm-misc-fixes-2017-05-18: Driver Changes: - host1x: Fix link error when host1x is built-in and

Re: [PATCH libdrm] xf86drm: fix compile error for declare i in for loop

On 18 May 2017 at 14:46, Emil Velikov wrote: > On 18 May 2017 at 13:47, Eric Engestrom wrote: > >>> > Yes, I think you should change your build command. It's a shame that >>> > autotools has this bug, but we'd like to avoid changing our

Re: [PATCH] gpu: host1x: select IOMMU_IOVA

On Thu, Apr 20, 2017 at 09:47:35AM +0300, Mikko Perttunen wrote: > Ah, had to forget something :) > > Reviewed-by: Mikko Perttunen Applied to -misc-fixes, thank you Sean > > On 19.04.2017 21:24, Arnd Bergmann wrote: > > When IOMMU_IOVA is not built-in but host1x is,

Re: [PATCH] drm/atmel-hlcdc: Fix output initialization

On Thu, May 18, 2017 at 02:43:07PM +0200, Alexandre Belloni wrote: > On 18/05/2017 at 14:35:21 +0200, Boris Brezillon wrote: > > drm_of_find_panel_or_bridge() is expecting np to point to the encoder > > node, not the bridge or panel this encoder is feeding. > > Moreover, the endpoint parameter

Re: [PATCH 2/4] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

Hi Archit, On Thursday 18 May 2017 13:56:19 Archit Taneja wrote: > On 05/17/2017 12:16 AM, Eric Anholt wrote: [snip] > > In terms of physical connections: > >[15-pin "DSI" connector on 2835] > > > > | I2C | DSI > > > >/ \SPI | > > > > [TS]

Re: [PATCH 2/4] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

Hi Eric, On Tuesday 16 May 2017 11:46:36 Eric Anholt wrote: [snip] > In terms of physical connections: > >[15-pin "DSI" connector on 2835] > > | I2C | DSI >/ \SPI | > [TS] [Atmel]--[TC358762] >\| > \PWM|

Re: [PATCH] drm/i915: Check C for null pointer rather than B

On Thu, May 18, 2017 at 02:39:42PM +0100, Colin King wrote: > From: Colin Ian King > > There are two occasions where pointer B is being check for a NULL > when it should be pointer C instead. Fix these. > > Detected by CoverityScan, CID#1436348,1436349 ("Logically Dead

[Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)

https://bugs.freedesktop.org/show_bug.cgi?id=99851 --- Comment #30 from erhar...@mailbox.org --- The same problem on my machine: # dmesg | grep -i drm [ 11.753729] [drm] radeon kernel modesetting enabled. [ 11.760535] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68F9 0x1787:0x2291

Re: [PATCH libdrm] xf86drm: fix compile error for declare i in for loop

On 18 May 2017 at 13:47, Eric Engestrom wrote: >> > Yes, I think you should change your build command. It's a shame that >> > autotools has this bug, but we'd like to avoid changing our codebase to >> > work around these, and in this case, it would mean dropping the

[PATCH] drm/i915: Check C for null pointer rather than B

From: Colin Ian King There are two occasions where pointer B is being check for a NULL when it should be pointer C instead. Fix these. Detected by CoverityScan, CID#1436348,1436349 ("Logically Dead Code") Fixes: 47624cc3301b60 ("drm/i915: Import the kfence selftests

Re: [PATCH] drm/pl111: Add a debugfs node to dump our registers.

On Thu, May 18, 2017 at 2:56 AM, Eric Anholt wrote: > While debugging an X11 display failure, I wanted to see where we were > actually scanning out from. This is probably generally useful to > others that might be working on this device. > > Signed-off-by: Eric Anholt

Re: [PATCH libdrm] xf86drm: fix compile error for declare i in for loop

On Thursday, 2017-05-18 12:10:31 +0100, Emil Velikov wrote: > On 17 May 2017 at 19:16, Eric Engestrom wrote: > > On Wednesday, 2017-05-17 13:58:42 +, Yu, Qiang wrote: > >> Hi Emil, > >> > >> I didn't modify the code. I'm using Ubuntu 14.04 gcc 4.8.4, the configure

  1   2   >