[Bug 98357] [amdgpu] Topaz fails to boot with error in powerplay initialization

attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/7ccf331b/attachment.html>

[Bug 185681] amdgpu: powerplay initialization failed

https://bugzilla.kernel.org/show_bug.cgi?id=185681 --- Comment #10 from Alex Deucher --- Created attachment 244151 --> https://bugzilla.kernel.org/attachment.cgi?id=244151=edit patch 3/3 -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 185681] amdgpu: powerplay initialization failed

https://bugzilla.kernel.org/show_bug.cgi?id=185681 --- Comment #9 from Alex Deucher --- Created attachment 244141 --> https://bugzilla.kernel.org/attachment.cgi?id=244141=edit patch 2/3 -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 185681] amdgpu: powerplay initialization failed

https://bugzilla.kernel.org/show_bug.cgi?id=185681 --- Comment #8 from Alex Deucher --- Created attachment 244131 --> https://bugzilla.kernel.org/attachment.cgi?id=244131=edit patch 1/3 Does the attached patch set fix the issue? -- You are receiving this mail because: You are watching the

[PATCH 04/20] drm/ast: use DRM_FB_HELPER_DEFAULT_OPS for fb_ops

Hi Daniel, On Tue, Nov 08, 2016 at 06:12:31PM +0100, Daniel Vetter wrote: > On Wed, Oct 26, 2016 at 09:15:15PM +0200, Daniel Vetter wrote: > > On Wed, Oct 26, 2016 at 8:47 PM, Stefan Lengfeld > > wrote: > > > > > > On Tue, Oct 25, 2016 at 04:57:37PM +0200, Daniel Vetter wrote: > > >> On Thu, Sep

[PATCH RFC 00/12] tda998x updates

On Wed, Nov 09, 2016 at 11:45:05AM +, Jon Medhurst (Tixy) wrote: > On Tue, 2016-11-08 at 18:24 +, Russell King - ARM Linux wrote: > > On Tue, Nov 08, 2016 at 05:20:36PM +, Jon Medhurst (Tixy) wrote: > > > On Tue, 2016-11-08 at 13:34 +, Russell King - ARM Linux wrote: > > > > On

[PATCH] drm/rockchip: analogix_dp: add supports for regulators in edp IP

On 10/28/2016 05:29 PM, Randy Li wrote: > > > On 10/28/2016 05:11 PM, Shawn Lin wrote: >> On 2016/10/23 3:18, Randy Li wrote: >>> I found if eDP_AVDD_1V0 and eDP_AVDD_1V8 are not been power at >>> RK3288, once trying to enable the pclk clock, the kernel would dead. >>> This patch would try to

[PATCH] drm/rockchip: analogix_dp: add supports for regulators in edp IP

On 10/28/2016 05:29 PM, Randy Li wrote: > > > On 10/28/2016 05:11 PM, Shawn Lin wrote: >> On 2016/10/23 3:18, Randy Li wrote: >>> I found if eDP_AVDD_1V0 and eDP_AVDD_1V8 are not been power at >>> RK3288, once trying to enable the pclk clock, the kernel would dead. >>> This patch would try to

[Bug 98357] [amdgpu] Topaz fails to boot with error in powerplay initialization

||/show_bug.cgi?id=185681 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/9bddb

[drm-intel:topic/drm-misc 1/2] backtracetest.c:undefined reference to `save_stack_trace'

Intel Corporation -- next part -- A non-text attachment was scrubbed... Name: .config.gz Type: application/gzip Size: 38611 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/da109d62/attachment-0001.gz>

[radeon-alex:drm-next-4.10-wip 26/45] drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c:1613:24-48: duplicated argument to & or |

The constants on lines 1613 and 1615 are the same. julia On Wed, 9 Nov 2016, kbuild test robot wrote: > > tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.10-wip > head: a5178d59d93d8b04fed1de3602cd448de9f1f995 > commit: 94f2d9bf6f3c0c192bc864ba1530d0f40afe9984 [26/45]

[Bug 98238] witcher 2: objects are black when changing lod

not being able to change the grass settings. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/6de822fc/attachment.html>

[Bug 98667] [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta 0.8.4)

dri-devel/attachments/20161109/3b72b613/attachment.html>

[Bug 98667] [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta 0.8.4)

bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/9e051173/attachment.html>

[Bug 98667] [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta 0.8.4)

vel/attachments/20161109/a7e72681/attachment.html>

[Bug 98667] [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta 0.8.4)

art -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/57bf6a41/attachment.html>

[Bug 98667] [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta 0.8.4)

4.0-47-generic). -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/a1cd2553/attachment.html>

[PATCH 5/5] drm/i915: Implement Link Rate fallback on Link training failure

If link training at a link rate optimal for a particular mode fails during modeset's atomic commit phase, then we let the modeset complete and then retry. We save the link rate value at which link training failed, update the link status property to "BAD" and use a lower link rate to prune the

[PATCH 4/5] drm/i915: Find fallback link rate/lane count

If link training fails, then we need to fallback to lower link rate first and if link training fails at RBR, then fallback to lower lane count. This function finds the next lower link rate/lane count value after link training failure. v2: Squash the patch that returns the link rate index (Jani

[PATCH 3/5] drm/i915: Update CRTC state if connector link status property changed

CRTC state connector_changed needs to be set to true if connector link status property has changed. This will tell the driver to do a complete modeset due to change in connector property. Cc: dri-devel at lists.freedesktop.org Cc: Jani Nikula Cc: Daniel Vetter Cc: Ville Syrjala Signed-off-by:

[PATCH 2/5] drm/i915: Set link status property for DP connector

This defines a helper function to set the property value. This will be used to set the link status to Bad in case of link training failures. v3: * Set connector->link_status in this function (Jani Nikula) v2: * Simplify the return value (Jani Nikula) Cc: dri-devel at lists.freedesktop.org Cc:

[PATCH 1/5] drm: Add a new connector property for link status

A new default connector property is added for keeping track of whether the link is good (link training passed) or link is bad (link training failed). If the link status property is not good, then userspace should fire off a new modeset at the current mode even if there have not been any changes

[PATCH 0/5] Handle Link Training Failure during modeset

Link training failure is handled by lowering the link rate first until it reaches the minimum and keeping the lane count maximum and then lowering the lane count until it reaches minimim. These fallback values are saved and hotplug uevent is sent to the userspace after setting the connector link

[PATCH v9 01/11] drm/i915: Add i915 perf infrastructure

On 7 November 2016 at 19:49, Robert Bragg wrote: > Adds base i915 perf infrastructure for Gen performance metrics. > > This adds a DRM_IOCTL_I915_PERF_OPEN ioctl that takes an array of uint64 > properties to configure a stream of metrics and returns a new fd usable > with standard VFS system

[PATCH v9 09/11] drm/i915: add dev.i915.oa_max_sample_rate sysctl

On 7 November 2016 at 19:49, Robert Bragg wrote: > The maximum OA sampling frequency is now configurable via a > dev.i915.oa_max_sample_rate sysctl parameter. > > Following the precedent set by perf's similar > kernel.perf_event_max_sample_rate the default maximum rate is 10Hz > >

[Bug 39832] HDA ATI HDMI: no sound with 3.0 - 2.6.39.3 works

https://bugzilla.kernel.org/show_bug.cgi?id=39832 Szőgyényi Gábor changed: What|Removed |Added CC||szg at freemail.hu --- Comment

[Bug 60568] nv49_ram_create kernel panic

https://bugzilla.kernel.org/show_bug.cgi?id=60568 Szőgyényi Gábor changed: What|Removed |Added CC||szg at freemail.hu --- Comment

4.9-rc1 lockdep warning suggesting a deadlock between nouveau and i915 with prime video outputs active

Hi, On 09-11-16 18:26, Chris Wilson wrote: > On Wed, Nov 09, 2016 at 06:02:40PM +0100, Hans de Goede wrote: >> Hi, >> >> I noticed this while testing the displayport output attached >> to the nvidia GPU on a Thinkpad P50 while the intel GPU >> was driving the LCD panel (and was the primary GPU

[Bug 98664] Fragment shader while loop causes geometry corruption

You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/6c0b5239/attachment.html>

[Bug 98664] Fragment shader while loop causes geometry corruption

ext part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/44f7434c/attachment.html>

[Bug 98664] Fragment shader while loop causes geometry corruption

ext part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/8949223b/attachment.html>

[Bug 98664] Fragment shader while loop causes geometry corruption

ent was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/e0149154/attachment.html>

[PATCH 3/3] drm/tilcdc: Add drm bridge support for attaching drm bridge drivers

On Wed, Nov 02, 2016 at 06:32:17PM +0200, Jyri Sarha wrote: > Adds drm bride support for attaching drm bridge drivers to tilcdc. The > decision whether a video port leads to an external encoder or bridge > is made simply based on remote device's compatible string. The code > has been tested with

[PATCH] drm/nouveau: Intercept ACPI_VIDEO_NOTIFY_PROBE

Various notebooks with nvidia GPUs generate an ACPI_VIDEO_NOTIFY_PROBE acpi-video event when an external device gets plugged in (and again on modesets on that connector), the default behavior in the acpi-video driver for this is to send a KEY_SWITCHVIDEOMODE evdev event, which causes e.g.

[PATCH] acpi: video: Move ACPI_VIDEO_NOTIFY_* defines to acpi/video.h

acpi_video.c passed the ACPI_VIDEO_NOTIFY_* defines as type code to acpi_notifier_call_chain(). Move these defines to acpi/video.h so that acpi_notifier listeners can check the type code using these defines. Signed-off-by: Hans de Goede --- drivers/acpi/acpi_video.c | 11 ---

[PATCH libdrm v2] xf86drm: Parse the separate files to retrieve the vendor, ... info

From: Emil Velikov Parsing config sysfs file wakes up the device. The latter of which may be slow and isn't required to begin with. Reading through config is/was required since the revision is not available by other means, although with a kernel patch in the way that

4.9-rc1 lockdep warning suggesting a deadlock between nouveau and i915 with prime video outputs active

://lists.freedesktop.org/archives/dri-devel/attachments/20161109/f1bc6535/attachment-0001.bin>

4.9-rc1 lockdep warning suggesting a deadlock between nouveau and i915 with prime video outputs active

On Wed, Nov 09, 2016 at 06:02:40PM +0100, Hans de Goede wrote: > Hi, > > I noticed this while testing the displayport output attached > to the nvidia GPU on a Thinkpad P50 while the intel GPU > was driving the LCD panel (and was the primary GPU according > to Xorg). This was while logging into

[Intel-gfx] [PATCH v3] drm: move allocation out of drm_get_format_name()

On Wednesday, 2016-11-09 14:13:40 +0100, Daniel Vetter wrote: > On Wed, Nov 9, 2016 at 12:42 PM, Eric Engestrom > wrote: > >> Well, had to drop it again since it didn't compile: > >> > >> > >> CC [M] drivers/gpu/drm/drm_blend.o > >> drivers/gpu/drm/drm_atomic.c: In function > >>

[PATCH v2] PCI: create revision file in sysfs

From: Emil Velikov Currently the revision isn't available via sysfs/libudev thus if one wants to know the value they need to read through the config file. This in itself wakes/powers up the device, causing unwanted delays. There are at least two userspace components

[pull] amdgpu drm-fixes-4.9

Hi Dave, Just a few small bug fixes for 4.9. The following changes since commit 020a0bbc0d89c15693e69ed2063584ef7ec2d811: Merge branch 'msm-fixes-4.9' of git://people.freedesktop.org/~robclark/linux into drm-fixes (2016-11-07 09:41:10 +1000) are available in the git repository at:

[PATCH v3 1/4] drm: Add a new connector property for link status

On Mon, 31 Oct 2016, Manasi Navare wrote: > A new default connector property is added for keeping > track of whether the link is good (link training passed) or > link is bad (link training failed). If the link status property > is not good, then userspace should fire off a new modeset at the

[Bug 98638] Panic on shutdown with AMDGPU and Ubuntu Plymouth

You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/8ef50196/attachment.html>

[PATCH] drm: Make DRM_DEBUG_MM depend on STACKTRACE_SUPPORT

0day continues to complain about trying to save a stacktrace for the users of the drm_mm range allocator. This time, it is that m68k has no save_stack_trace(), which is apparently guarded by STACKTRACE_SUPPORT. Make it depend so! Reported-by: kbuild test robot Signed-off-by: Chris Wilson Cc:

[Intel-gfx] [drm-intel:topic/drm-misc 1/2] backtracetest.c:undefined reference to `save_stack_trace'

On 9 November 2016 at 14:12, Chris Wilson wrote: > On Wed, Nov 09, 2016 at 10:01:37PM +0800, kbuild test robot wrote: >> tree: git://anongit.freedesktop.org/drm-intel topic/drm-misc >> head: 77d150b90d58ae6a43bf67af28feb26384d06cd6 >> commit: cd456f8d06d2036e1e013136c3fbf5721d04f6d7 [1/2]

[Intel-gfx] [PATCH v3] drm: move allocation out of drm_get_format_name()

On Wed, Nov 9, 2016 at 12:42 PM, Eric Engestrom wrote: >> Well, had to drop it again since it didn't compile: >> >> >> CC [M] drivers/gpu/drm/drm_blend.o >> drivers/gpu/drm/drm_atomic.c: In function ‘drm_atomic_plane_print_state’: >> drivers/gpu/drm/drm_atomic.c:920:5: error: too few

[drm-intel:topic/drm-misc 1/2] backtracetest.c:undefined reference to `save_stack_trace'

On Wed, Nov 09, 2016 at 10:01:37PM +0800, kbuild test robot wrote: > tree: git://anongit.freedesktop.org/drm-intel topic/drm-misc > head: 77d150b90d58ae6a43bf67af28feb26384d06cd6 > commit: cd456f8d06d2036e1e013136c3fbf5721d04f6d7 [1/2] drm: Restrict > stackdepot usage to builtin drm.ko >

[PATCH] drm_fourcc: Document linear modifier

Not setting the fb modifiers flag is something different from setting the fb modifiers to 0 (which means explicitly linear). We kinda failed to document that properly. Spotted by Kristian. Cc: hoegsberg at google.com Signed-off-by: Daniel Vetter --- include/uapi/drm/drm_fourcc.h | 10 ++

[PULL] drm-intel-fixes

Hi Dave - Fixes for i915, in particular includes the fix for [1]. BR, Jani. [1] http://lkml.kernel.org/r/2656903.keIazZlQoI at merkaba The following changes since commit bc33b0ca11e3df46a4fa7639ba488c9d4911: Linux 4.9-rc4 (2016-11-05 16:23:36 -0700) are available in the git

[PATCH v2 2/5] ARM: bus: da8xx-mstpri: new driver

On Mon, Oct 31, 2016 at 03:45:35PM +0100, Bartosz Golaszewski wrote: > Create the driver for the da8xx master peripheral priority > configuration and implement support for writing to the three > Master Priority registers on da850 SoCs. > > Signed-off-by: Bartosz Golaszewski > --- >

[PATCH v2 1/5] ARM: memory: da8xx-ddrctl: new driver

On Mon, Oct 31, 2016 at 03:45:34PM +0100, Bartosz Golaszewski wrote: > Create a new driver for the da8xx DDR2/mDDR controller and implement > support for writing to the Peripheral Bus Burst Priority Register. > > Signed-off-by: Bartosz Golaszewski > --- >

drm/bridge: analogix_dp: clear psr_support when disable_bridge

From: zain wang Don't run psr work during enabling bridge when you restart ui, it may make link training fail since there is a race between them in AUX CH resource. Signed-off-by: zain wang Signed-off-by: Caesar Wang Cc: Tomeu Vizoso Cc: dri-devel at

[PATCH RFC 00/12] tda998x updates

On Tue, 2016-11-08 at 18:24 +, Russell King - ARM Linux wrote: > On Tue, Nov 08, 2016 at 05:20:36PM +, Jon Medhurst (Tixy) wrote: > > On Tue, 2016-11-08 at 13:34 +, Russell King - ARM Linux wrote: > > > On Tue, Nov 08, 2016 at 01:32:15PM +, Russell King - ARM Linux wrote: > > > >

[Intel-gfx] [PATCH v3] drm: move allocation out of drm_get_format_name()

On Wednesday, 2016-11-09 02:13:25 +0100, Daniel Vetter wrote: > On Wed, Nov 09, 2016 at 02:09:16AM +0100, Daniel Vetter wrote: > > On Wed, Nov 09, 2016 at 12:17:52AM +, Eric Engestrom wrote: > > > The function's behaviour was changed in 90844f00049e, without changing > > > its signature,

[PATCH v7 3/3] drm/fence: add out-fences support

2016-11-08 Daniel Vetter : > On Tue, Nov 08, 2016 at 03:54:50PM +0900, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Support DRM out-fences by creating a sync_file with a fence for each CRTC > > that sets the OUT_FENCE_PTR property. > > > > We use the out_fence pointer received in

[PATCH v7 3/3] drm/fence: add out-fences support

On Wed, Nov 09, 2016 at 11:39:11AM +0900, Gustavo Padovan wrote: > > On Tue, Nov 08, 2016 at 03:54:50PM +0900, Gustavo Padovan wrote: > > > + if (!access_ok(VERIFY_WRITE, fence_ptr, sizeof(*fence_ptr))) > > > + return -EFAULT; > > > > Same comment about igt coverage I made

linux-next: build failure after merge of the drm-misc tree

Hi all, After merging the drm-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "depot_save_stack" [drivers/gpu/drm/drm.ko] undefined! ERROR: "depot_fetch_stack" [drivers/gpu/drm/drm.ko] undefined! Caused by commit 5705670d0463 ("drm: Track drm_mm allocators

[PATCH] gpu: ipu-di: silence videomode logspam

Am Dienstag, den 08.11.2016, 16:57 +0100 schrieb Lucas Stach: > Adapting the videomode to the hardware constraints is something that > can and must happen during normal operation and isn't something that > the user can avoid. So printing a warning each time it happens isn't > helpful. > > Demote

[PATCH] drm_fourcc: Document linear modifier

er. > + */ > +#define DRM_FORMAT_MOD_LINEAR fourcc_mod_code(NONE, 0) > + > /* Intel framebuffer modifiers */ > > /* > -- > 2.7.4 > > -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/3bbbd944/attachment-0001.html>

BUG: 'list_empty(>free_vbufs)' is true!

On Di, 2016-11-08 at 22:37 +0200, Michael S. Tsirkin wrote: > On Mon, Nov 07, 2016 at 09:43:24AM +0100, Jiri Slaby wrote: > > Hi, > > > > I can relatively easily reproduce this bug: How? > > BUG: 'list_empty(>free_vbufs)' is true! > The following might be helpful for debugging - if kernel

[Bug 98638] Panic on shutdown with AMDGPU and Ubuntu Plymouth

are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/c6e87ce6/attachment.html>

[Bug 98638] Panic on shutdown with AMDGPU and Ubuntu Plymouth

. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/85cb3926/attachment.html>

[Bug 98638] Panic on shutdown with AMDGPU and Ubuntu Plymouth

. The computer responds to sysrq but V and G have no effect. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/76737

[Bug 98627] mesa doesn't build since llvm r286062

vel/attachments/20161109/c9161b3e/attachment.html>

[PATCH] drm/amdgpu: Attach exclusive fence to prime exported bo's. (v5)

External clients which import our bo's wait only for exclusive dmabuf-fences, not on shared ones, ditto for bo's which we import from external providers and write to. Therefore attach exclusive fences on prime shared buffers if our exported buffer gets imported by an external client, or if we

[Intel-gfx] [PATCH v3] drm: move allocation out of drm_get_format_name()

On Wed, Nov 09, 2016 at 02:09:16AM +0100, Daniel Vetter wrote: > On Wed, Nov 09, 2016 at 12:17:52AM +, Eric Engestrom wrote: > > The function's behaviour was changed in 90844f00049e, without changing > > its signature, causing people to keep using it the old way without > > realising they were

[Intel-gfx] [PATCH v3] drm: move allocation out of drm_get_format_name()

On Wed, Nov 09, 2016 at 12:17:52AM +, Eric Engestrom wrote: > The function's behaviour was changed in 90844f00049e, without changing > its signature, causing people to keep using it the old way without > realising they were now leaking memory. > Rob Clark also noticed it was also allocating

[Bug 98638] Panic on shutdown with AMDGPU and Ubuntu Plymouth

are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161109/53f24d7b/attachment.html>

[PATCH 1/4] dma-buf/fence: make timeout handling in fence_default_wait consistent (v2)

Hi Alex, Christian, On 8 November 2016 at 02:46, Alex Deucher wrote: > Kernel functions taking a timeout usually return 1 on success even > when they get a zero timeout. > > v2: agd: rebase on drm-next > > Reviewed-by: Alex Deucher > Signen-off-by: Christian König > Reviewed-by: Chunming Zhou

[PATCH 1/2] dma-buf: return index of the first signaled fence (v2)

Hi Alex, Christian, On 8 November 2016 at 04:12, Sumit Semwal wrote: > Hi Alex, > > On 07-Nov-2016 11:14 PM, "Alex Deucher" wrote: >> >> On Fri, Nov 4, 2016 at 6:03 PM, Sumit Semwal >> wrote: >> > Hi Alex, >> > >> > Thanks for the patches. >> > >> > On 4 November 2016 at 14:16, Alex Deucher

[PATCH] MAINTAINERS: update Sync File Framework files

On 27 October 2016 at 02:34, Gustavo Padovan wrote: > From: Gustavo Padovan > > Signed-off-by: Gustavo Padovan > --- Applied to drm-misc; Thanks! > MAINTAINERS | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index e60e0a1..10f1bc0 100644

[PATCH] dma-buf/sw_sync: put fence reference from the fence creation

On 27 October 2016 at 03:24, Chris Wilson wrote: > On Wed, Oct 26, 2016 at 06:59:59PM -0200, Gustavo Padovan wrote: >> From: Gustavo Padovan >> >> Once sw_sync_ioctl_create_fence() returns we no longer have the >> *pt pointer to the fence base object thus we need to put the reference >> we have

[PATCH v4] drm: bridge: add DesignWare HDMI I2S audio support

Hi Russell > > @@ -11,4 +11,11 @@ struct dw_hdmi_audio_data { > > u8 *eld; > > }; > > > > +struct dw_hdmi_i2s_audio_data { > > + struct dw_hdmi *hdmi; > > + > > + void (*write)(struct dw_hdmi *hdmi, u8 val, int offset); > > + u8 (*read)(struct dw_hdmi *hdmi, int offset); > > +}; >

[PATCH v3] drm: move allocation out of drm_get_format_name()

The function's behaviour was changed in 90844f00049e, without changing its signature, causing people to keep using it the old way without realising they were now leaking memory. Rob Clark also noticed it was also allocating GFP_KERNEL memory in atomic contexts, breaking them. Instead of having to