Re: [PATCH 2/4] drm/i915: use drm DP helper to read DPCD desc

On Wed, May 17, 2017 at 05:25:14PM +0300, Jani Nikula wrote: > Switch to using the common DP helpers instead of using our own. > > Signed-off-by: Jani Nikula Forgot to remove struct intel_dp_desc, otherwise lgtm. Reviewed-by: Daniel Vetter > ---

Re: [PATCH 4/4] drm/i915: Detect USB-C specific dongles before reducing M and N

On Wed, May 17, 2017 at 05:25:16PM +0300, Jani Nikula wrote: > The Analogix 7737 DP to HDMI converter requires reduced M and N values > when to operate correctly at HBR2. Detect this IC by its OUI value of > 0x0022B9 via the DPCD quirk list. Commit message is a bit confusing since this sounds

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

Am 18.05.2017 um 06:43 schrieb Masahiro Yamada: 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 Reviewed-by: Christian König

Re: [PATCH v5 3/3] drm/i915: Add format modifiers for Intel

On 18 May 2017 at 02:14, Ben Widawsky wrote: > On 17-05-17 01:20:50, Emil Velikov wrote: >> >> Hi Ben, >> >> A couple of small questions/suggestions that I hope you find useful. >> Please don't block any of this work based on my comments. >> >> On 16 May 2017 at 22:31, Ben

Re: [PATCH v3 14/21] drm/sun4i: tcon: multiply the vtotal when not in interlace

On Wed, May 17, 2017 at 05:50:45PM +0800, Chen-Yu Tsai wrote: > On Wed, May 17, 2017 at 3:40 PM, Maxime Ripard > wrote: > > It appears that the total vertical resolution needs to be doubled when > > we're not in interlaced. Make sure that is the case. > > > >

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

Hi Rob, On 18 May 2017 at 02:39, 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 API, but realizing that userspace is

Re: [Intel-gfx] [PATCH v2 2/3] drm: Create a format/modifier blob

On 18 May 2017 at 01:46, Ben Widawsky wrote: >>> + blob_size += modifiers_size; >>> + >>> + blob = drm_property_create_blob(dev, blob_size, NULL); >>> + if (IS_ERR(blob)) >>> + return -1; >>> + >> >> Maybe propagate the exact error... Hmm we

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

On Wed, May 17, 2017 at 09:39:11PM -0400, Robert Foss wrote: > +/* > + * DRM_MODE_REFLECT_ > + * > + * Signals that the contents of a drm plane has been reflected in > + * the axis. Still vague. Also you didn't respond to my comment about the use of past tense. > + * > + * This define is

Re: [PATCH] drm/amd/powerplay: ensure loop does not wraparound on decrement

Am 17.05.2017 20:13, schrieb Colin King: > From: Colin Ian King > > The current for loop decrements i when it is zero and this causes > a wrap-around back to ~0 because i is unsigned. In the unlikely event > that mask is 0, the loop will run forever. Fix this so we

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

Hi, On 05/17/2017 12:16 AM, Eric Anholt wrote: Laurent Pinchart writes: Hi Eric, On Tuesday 16 May 2017 09:47:49 Eric Anholt wrote: Rob Herring writes: On Mon, May 15, 2017 at 7:03 PM, Eric Anholt wrote: Laurent

Re: [Intel-gfx] [PATCH v2 2/3] drm: Create a format/modifier blob

On Wed, May 17, 2017 at 05:46:18PM -0700, Ben Widawsky wrote: > On 17-05-17 01:06:16, Emil Velikov wrote: > >Hi Ben, > > > >On 16 May 2017 at 22:31, Ben Widawsky wrote: > >> Updated blob layout (Rob, Daniel, Kristian, xerpi) > >> > >> v2: > >> * Removed __packed, and alignment

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

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 build battery with cross arch compilers and it passes so there shouldn't

Re: [REGRESSION] drm/radeon: Don't register Thunderbolt eGPU with vga_switcheroo

On Wed, May 17, 2017 at 11:08:23PM +0200, Nicolai Stange wrote: > I'm experiencing a boot failure on next-20170515: > > BUG: unable to handle kernel NULL pointer dereference at 07cb > IP: radeon_driver_load_kms+0xeb/0x230 [radeon] [snip] > Bisection lead to commit 7ffb0ce31cf9

Re: [PATCH v3 1/3] drm: Plumb modifiers through plane init

On Wed, May 17, 2017 at 05:26:14PM -0700, Ben Widawsky wrote: > On 17-05-17 11:17:57, Liviu Dudau wrote: > > On Tue, May 16, 2017 at 02:31:24PM -0700, Ben Widawsky wrote: > > > This is the plumbing for supporting fb modifiers on planes. Modifiers > > > have already been introduced to some extent,

Re: [PATCH] drm/omap: fix tiled buffer stride calculations

Hi Tomi, On Thursday 18 May 2017 14:14:35 Tomi Valkeinen wrote: > On 18/05/17 13:59, Laurent Pinchart wrote: > > On Thursday 18 May 2017 13:28:26 Tomi Valkeinen wrote: > >> omap_gem uses page alignment for buffer stride. The related calculations > >> are a bit off, though, as byte stride of 4096

Re: [PATCH] drm/omap: fix tiled buffer stride calculations

On Thu, May 18, 2017 at 02:14:35PM +0300, Tomi Valkeinen wrote: > On 18/05/17 13:59, Laurent Pinchart wrote: > > Hi Tomi, > > > > Thank you for the patch. > > > > On Thursday 18 May 2017 13:28:26 Tomi Valkeinen wrote: > >> omap_gem uses page alignment for buffer stride. The related calculations

Re: [PATCH] drm/omap: fix tiled buffer stride calculations

On 18/05/17 14:25, Laurent Pinchart wrote: > Hi Tomi, > > On Thursday 18 May 2017 14:14:35 Tomi Valkeinen wrote: >> On 18/05/17 13:59, Laurent Pinchart wrote: >>> On Thursday 18 May 2017 13:28:26 Tomi Valkeinen wrote: omap_gem uses page alignment for buffer stride. The related calculations

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

On Wednesday, 2017-05-17 17:56:40 -0700, 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 3/4] drm/dp: start a DPCD based DP sink/branch device quirk database

On Wed, 17 May 2017, Clint Taylor wrote: > On 05/17/2017 07:25 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

Re: [PATCH] drm/omap: fix tiled buffer stride calculations

Hi Tomi, Thank you for the patch. On Thursday 18 May 2017 13:28:26 Tomi Valkeinen wrote: > omap_gem uses page alignment for buffer stride. The related calculations > are a bit off, though, as byte stride of 4096 gets aligned to 8192, > instead of 4096. This patch fixes those calculations. > >

[PATCH 0/4] drm/dp: device identification and quirks ~v3

Update on [1]. BR, Jani. [1] cover.1495030890.git.jani.nikula@intel.com">http://mid.mail-archive.com/cover.1495030890.git.jani.nikula@intel.com Jani Nikula (4): drm/dp: add helper for reading DP sink/branch device desc from DPCD drm/i915: use drm DP helper to read DPCD desc drm/dp:

[PATCH 4/4] drm/i915: Detect USB-C specific dongles before reducing M and N

The Analogix 7737 DP to HDMI converter requires reduced M and N values when to operate correctly at HBR2. We tried to reduce the M/N values for all devices in commit 9a86cda07af2 ("drm/i915/dp: reduce link M/N parameters"), but that regressed some other sinks. Detect this IC by its OUI value of

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

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 based on the DP device identification. At least

[PATCH 2/4] drm/i915: use drm DP helper to read DPCD desc

Switch to using the common DP helpers instead of using our own. v2: also remove leftover struct intel_dp_desc (Daniel) Reviewed-by: Daniel Vetter Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/intel_dp.c | 37

[PATCH 1/4] drm/dp: add helper for reading DP sink/branch device desc from DPCD

Reviewed-by: Daniel Vetter Signed-off-by: Jani Nikula --- drivers/gpu/drm/drm_dp_helper.c | 35 +++ include/drm/drm_dp_helper.h | 19 +++ 2 files changed, 54 insertions(+) diff --git

Re: [PATCH] drm/omap: fix tiled buffer stride calculations

On 18/05/17 13:59, Laurent Pinchart wrote: > Hi Tomi, > > Thank you for the patch. > > On Thursday 18 May 2017 13:28:26 Tomi Valkeinen wrote: >> omap_gem uses page alignment for buffer stride. The related calculations >> are a bit off, though, as byte stride of 4096 gets aligned to 8192, >>

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

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 API, but realizing that userspace is likely to take >

[PULL] drm-intel-fixes

Hi Dave, drm/i915 fixes for v4.12-rc2. BR, Jani. The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6: Linux 4.12-rc1 (2017-05-13 13:19:49 -0700) are available in the git repository at: git://anongit.freedesktop.org/git/drm-intel tags/drm-intel-fixes-2017-05-18-1

[PATCH] drm/omap: fix tiled buffer stride calculations

omap_gem uses page alignment for buffer stride. The related calculations are a bit off, though, as byte stride of 4096 gets aligned to 8192, instead of 4096. This patch fixes those calculations. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/omap_gem.c | 4 ++--

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

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 >> pass but >> fail when compile. >> >> I think my gcc support c99 but

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

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 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 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

[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 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] 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 ++--

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); >>> +

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;

[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 ++-

[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: (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] 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

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 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 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] 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 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 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

[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

[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 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

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 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 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 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 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:

[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 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

[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/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 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 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 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

[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

[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

[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] 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

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

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] 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 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

[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. --

[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(+)

[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 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] 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

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 =

[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 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 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 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

[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: [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),

[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

[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

  1   2   >