Rob Herring writes:
> Need to cc DT list if you want it in my queue.
>
> On Mon, Jan 23, 2017 at 6:38 PM, Eric Anholt wrote:
>> These are part of the vc4 display pipeline.
>>
>> Signed-off-by: Eric Anholt
>> ---
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex Xie (4):
amdgpu: Provide more specific error message if non-privileged user runs
amdgpu_test
amdgpu: verify the tested device
amdgpu: A new option to choose which device to run most tests
amdgpu: A new option to run
Turns out some VBIOSes don't actually set the bit in question in 2240c.
Use the nv50-style detection to try avoiding running the vbios twice.
Fixes: a6a0f67ca7aa ("drm/nouveau/devinit/gf100-: detect if BIOS invoked
devinit")
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97620
Cc:
Need to cc DT list if you want it in my queue.
On Mon, Jan 23, 2017 at 6:38 PM, Eric Anholt wrote:
> These are part of the vc4 display pipeline.
>
> Signed-off-by: Eric Anholt
> ---
> .../devicetree/bindings/display/brcm,bcm-vc4.txt | 35
>
https://bugs.freedesktop.org/show_bug.cgi?id=99553
--- Comment #7 from Vedran Miletić ---
(In reply to darkbasic from comment #6)
> Thanks, I would love to have at least Darktable working. With the CPU it
> takes 30+ seconds to process a single photo, compared to 0.5 seconds
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Vedran Miletić changed:
What|Removed |Added
Depends on||87738
Referenced
https://bugs.freedesktop.org/show_bug.cgi?id=87738
Vedran Miletić changed:
What|Removed |Added
Blocks||99553
Referenced
On 01/23, Eric Anholt wrote:
> +static int
> +vc4_dsi_init_phy_clocks(struct vc4_dsi *dsi)
> +{
> + struct device *dev = >pdev->dev;
> + const char *parent_name = __clk_get_name(dsi->pll_phy_clock);
> + static const struct {
> + const char *dsi0_name, *dsi1_name;
> +
This is an attempt at providing a DRM version of drivers/staging/fbtft.
The tinydrm library provides a very simplified view of DRM in particular
for tiny displays that has onboard video memory and is connected through
a slow bus like SPI/I2C.
Only core patches this time.
Noralf.
Changes
Add common functionality needed by many tinydrm drivers.
Signed-off-by: Noralf Trønnes
---
Changes since version 1:
- Remove some DRM_DEBUG*()
- Write-combined memory has uncached reads, so speed up by copying/buffering
one pixel line before conversion.
tinydrm provides helpers for very simple displays that can use
CMA backed framebuffers and need flushing on changes.
Signed-off-by: Noralf Trønnes
---
Changes since version 1:
- Add tinydrm.rst
- Set tdev->fbdev_cma=NULL on unregister (lastclose is called after that).
-
https://bugs.freedesktop.org/show_bug.cgi?id=99553
--- Comment #6 from darkbasic ---
Thanks, I would love to have at least Darktable working. With the CPU it takes
30+ seconds to process a single photo, compared to 0.5 seconds when using
OpenCL.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=99553
--- Comment #5 from Vedran Miletić ---
(In reply to darkbasic from comment #4)
> Sorry for asking, but the reason behind this bug report is because someone
> is finally willing to put some love into clover or nothing changed
https://bugs.freedesktop.org/show_bug.cgi?id=99553
--- Comment #4 from darkbasic ---
Sorry for asking, but the reason behind this bug report is because someone is
finally willing to put some love into clover or nothing changed in that regard?
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Jan Vesely changed:
What|Removed |Added
Depends on||74140
https://bugs.freedesktop.org/show_bug.cgi?id=74140
Jan Vesely changed:
What|Removed |Added
Blocks||99553
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Jan Vesely changed:
What|Removed |Added
Depends on||73510
https://bugs.freedesktop.org/show_bug.cgi?id=73510
Jan Vesely changed:
What|Removed |Added
Blocks||99553
https://bugs.freedesktop.org/show_bug.cgi?id=68857
Jan Vesely changed:
What|Removed |Added
Blocks||99553
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Jan Vesely changed:
What|Removed |Added
Depends on||68857
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Jan Vesely changed:
What|Removed |Added
Depends on||81896
https://bugs.freedesktop.org/show_bug.cgi?id=81896
Jan Vesely changed:
What|Removed |Added
Blocks||99553
https://bugs.freedesktop.org/show_bug.cgi?id=80876
Jan Vesely changed:
What|Removed |Added
Blocks||99553
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Jan Vesely changed:
What|Removed |Added
Depends on||80876
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Jan Vesely changed:
What|Removed |Added
Depends on||96881
https://bugs.freedesktop.org/show_bug.cgi?id=96881
Jan Vesely changed:
What|Removed |Added
Blocks||99553
https://bugs.freedesktop.org/show_bug.cgi?id=74973
--- Comment #5 from darkbasic ---
Not sure, but I don't think so. AFAIK it' only GEGL-related stuff.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=74973
--- Comment #4 from Jan Vesely ---
does GIMP use OpenGL other than GEGL library?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
On Fri, 27 Jan 2017 11:00:38 +0100
Gerd Hoffmann wrote:
> Hi folks,
>
> Problem at hand: A virtual machine, equipped with two display devices,
> one virtual, one physical (using pci pass-through, or kvmgt-based vgpu).
>
> There is no easy way for the user to configure
On środa, 25 stycznia 2017 12:24:35 CET Alex Deucher wrote:
> On Wed, Jan 25, 2017 at 12:16 PM, Krzysztof Nowicki
>
> wrote:
> > Hi,
> >
> >
> > Is this patch still being considered for pulling in?
> >
> > Recently I've been fighting with a HP UltraSlim docking
Noralf Trønnes writes:
> drm_debugfs_cleanup() now removes all minor->debugfs_list entries
> automatically, so the drm_driver.debugfs_cleanup callback is not
> needed.
Nice!
Reviewed-by: Eric Anholt
signature.asc
Description: PGP signature
From: Gustavo Padovan
As Sync File is highly dependent on dma-fence* tracks it
under SYNC FILE_FRAMEWORK as well.
Signed-off-by: Gustavo Padovan
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS
https://bugs.freedesktop.org/show_bug.cgi?id=99553
--- Comment #3 from Vedran Miletić ---
Thanks for contributing. Very glad to hear about Mandelbulber almost working. I
have added it to [1] as well.
[1] https://en.wikipedia.org/wiki/List_of_OpenCL_applications
--
You are
Hi Chris,
2017-01-24 Chris Wilson :
> Currently this tracepoint is solely used by dma_fence_enable_sw_signaling,
> however I have a need to manually perform the hw enabling of the
> signaling and would like to emit this tracepoint for completeness.
>
> Signed-off-by:
Hi Dave,
This is the main feature pull for radeon and amdgpu for 4.11. Highlights:
- Power and clockgating improvements
- Preliminary SR-IOV support
- ttm buffer priority support
- ttm eviction fixes
- Removal of the ttm lru callbacks
- Remove SI DPM quirks due to MC firmware issues
- Handle
Hi,
We're looking to enable the per-plane color management hardware in
Mali-DP with atomic properties, which has sparked some conversation
around how to handle YCbCr formats.
As it stands today, it's assumed that a driver will implicitly "do the
right thing" to display a YCbCr buffer.
YCbCr
On Sun, Jan 22, 2017 at 02:09:03PM +0800, Shawn Guo wrote:
> From: Shawn Guo
>
> The vblank hooks in struct drm_driver are deprecated and only meant for
> legacy drivers. For modern drivers with DRIVER_MODESET flag, the hooks
> in struct drm_crtc_funcs should be used
fwiw,
On 27 January 2017 at 20:25, Gustavo Padovan wrote:
> Hi Chris,
>
> 2017-01-24 Chris Wilson :
>
>> Currently this tracepoint is solely used by dma_fence_enable_sw_signaling,
>> however I have a need to manually perform the hw enabling of the
On Fri, Jan 27, 2017 at 1:52 AM, Daniel Vetter wrote:
> On Thu, Jan 26, 2017 at 8:48 PM, Eric Anholt wrote:
>>> - Should we require review or at least acks for patches committed by
>>> the author? We have a bunch of drivers with effectively just 1 person
Daniel Vetter writes:
> On Fri, Jan 27, 2017 at 09:20:42AM +0100, Gerd Hoffmann wrote:
>> On Do, 2017-01-26 at 23:05 -0200, Gabriel Krisman Bertazi wrote:
>> > No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
>> > output"). qxl_num_crtc defaults to 4 and
On Fri, Jan 27, 2017 at 1:32 AM, Daniel Vetter wrote:
> On Thu, Jan 26, 2017 at 8:11 PM, Sean Paul wrote:
>> On Thu, Jan 26, 2017 at 06:08:42PM +0100, Daniel Vetter wrote:
>>> - Should it be an entire separate tree for soc drivers? Problem here
>>>
On 27 January 2017 at 07:21, Tomasz Figa wrote:
> -lpthread is not always a valid flag to pull pthread support, especially
> on Android it will fail to link due to a missing libpthread.so. The more
> generic way to build-in pthread support is to use the -pthread CFLAG, so
>
On 27 January 2017 at 07:47, Thierry Reding wrote:
> On Thu, Jan 26, 2017 at 04:14:56PM +, Emil Velikov wrote:
>> On 26 January 2017 at 15:49, Thierry Reding wrote:
>> > On Fri, Jan 20, 2017 at 06:28:39PM +, Emil Velikov wrote:
>> >> On 20 January
The function is not that big, but it's also not used for anything
performance critical. Make it a normal function.
As a side effect, this apparently makes sparse smarter about what it's
doing, and gets rid of the warning:
./include/drm/drm_color_mgmt.h:53:28: warning: shift too big (4294967295)
https://bugs.freedesktop.org/show_bug.cgi?id=99387
--- Comment #8 from Alex Deucher ---
Created attachment 129182
--> https://bugs.freedesktop.org/attachment.cgi?id=129182=edit
possible fix
This patch should fix the crash.
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=193341
Alex Deucher changed:
What|Removed |Added
CC|
On Fri, Jan 27, 2017 at 03:58:08PM +0100, Daniel Vetter wrote:
> On Fri, Jan 27, 2017 at 02:31:55PM +, Chris Wilson wrote:
> > On Fri, Jan 27, 2017 at 03:21:29PM +0100, Daniel Vetter wrote:
> > > On Fri, Jan 27, 2017 at 09:30:50AM +, Chris Wilson wrote:
> > > > On Thu, Jan 26, 2017 at
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Andreas Boll changed:
What|Removed |Added
Depends on||99510
https://bugs.freedesktop.org/show_bug.cgi?id=99510
Andreas Boll changed:
What|Removed |Added
Blocks||99553
On Fri, Jan 27, 2017 at 3:22 AM, Christian König
wrote:
> Am 27.01.2017 um 08:30 schrieb Daniel Vetter:
>>
>> On Fri, Jan 27, 2017 at 07:23:58AM +0100, Thomas Hellstrom wrote:
>>>
>>> On 01/27/2017 03:29 AM, Michel Dänzer wrote:
On 26/01/17 09:46 AM, Sinclair
https://bugs.freedesktop.org/show_bug.cgi?id=96296
Andreas Boll changed:
What|Removed |Added
Blocks||99553
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Andreas Boll changed:
What|Removed |Added
Depends on||96296
On Fri, Jan 27, 2017 at 02:31:55PM +, Chris Wilson wrote:
> On Fri, Jan 27, 2017 at 03:21:29PM +0100, Daniel Vetter wrote:
> > On Fri, Jan 27, 2017 at 09:30:50AM +, Chris Wilson wrote:
> > > On Thu, Jan 26, 2017 at 04:59:21PM +0100, Maarten Lankhorst wrote:
> > > > When writing some
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Christoph Haag changed:
What|Removed |Added
Depends on||82717
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=82717
Christoph Haag changed:
What|Removed |Added
Blocks||99553
Referenced
Hi Chris,
2017-01-24 Chris Wilson :
> Currently this tracepoint is solely used by dma_fence_enable_sw_signaling,
> however I have a need to manually perform the hw enabling of the
> signaling and would like to emit this tracepoint for completeness.
>
> Signed-off-by:
On Fri, Jan 27, 2017 at 03:43:18PM +0100, Christian König wrote:
> Am 27.01.2017 um 15:12 schrieb Daniel Vetter:
> > On Fri, Jan 27, 2017 at 09:22:47AM +0100, Christian König wrote:
> > > Am 27.01.2017 um 08:30 schrieb Daniel Vetter:
> > > > On Fri, Jan 27, 2017 at 07:23:58AM +0100, Thomas
On Tue, Jan 24, 2017 at 11:57:58AM +, Chris Wilson wrote:
> Currently this tracepoint is solely used by dma_fence_enable_sw_signaling,
> however I have a need to manually perform the hw enabling of the
> signaling and would like to emit this tracepoint for completeness.
>
> Signed-off-by:
Am 27.01.2017 um 15:12 schrieb Daniel Vetter:
On Fri, Jan 27, 2017 at 09:22:47AM +0100, Christian König wrote:
Am 27.01.2017 um 08:30 schrieb Daniel Vetter:
On Fri, Jan 27, 2017 at 07:23:58AM +0100, Thomas Hellstrom wrote:
On 01/27/2017 03:29 AM, Michel Dänzer wrote:
On 26/01/17 09:46 AM,
On Fri, Jan 27, 2017 at 03:02:42PM +0100, Daniel Vetter wrote:
> On Fri, Jan 27, 2017 at 11:00:38AM +0100, Gerd Hoffmann wrote:
> > Hi folks,
> >
> > Problem at hand: A virtual machine, equipped with two display devices,
> > one virtual, one physical (using pci pass-through, or kvmgt-based
On Fri, Jan 27, 2017 at 03:31:06PM +0100, Daniel Vetter wrote:
> On Fri, Jan 27, 2017 at 04:13:42PM +0200, Ville Syrjälä wrote:
> > On Fri, Jan 27, 2017 at 01:50:19PM +, Brian Starkey wrote:
> > > On Fri, Jan 27, 2017 at 03:27:09PM +0200, Ville Syrjälä wrote:
> > > >On Fri, Jan 27, 2017 at
On Fri, 27 Jan 2017, Jani Nikula wrote:
> On Fri, 27 Jan 2017, Lionel Landwerlin wrote:
>> Hi Jani,
>>
>> Looks good to me :
>>
>> Reviewed-by: Lionel Landwerlin
>
> Thanks for the reviews, pushed... to
On Fri, Jan 27, 2017 at 03:21:29PM +0100, Daniel Vetter wrote:
> On Fri, Jan 27, 2017 at 09:30:50AM +, Chris Wilson wrote:
> > On Thu, Jan 26, 2017 at 04:59:21PM +0100, Maarten Lankhorst wrote:
> > > When writing some testcases for nonblocking modesets. I found out that the
> > > infinite wait
On Fri, Jan 27, 2017 at 04:13:42PM +0200, Ville Syrjälä wrote:
> On Fri, Jan 27, 2017 at 01:50:19PM +, Brian Starkey wrote:
> > On Fri, Jan 27, 2017 at 03:27:09PM +0200, Ville Syrjälä wrote:
> > >On Fri, Jan 27, 2017 at 10:47:48AM +, Brian Starkey wrote:
> > >> Explicitly state the
On Fri, Jan 27, 2017 at 03:23:43PM +0100, Noralf Trønnes wrote:
>
> Den 27.01.2017 08.49, skrev Daniel Vetter:
> > On Thu, Jan 26, 2017 at 11:56:02PM +0100, Noralf Trønnes wrote:
> > > This patchset removes the need for drivers to clean up their debugfs
> > > files on exit. It is done
On Fri, Jan 27, 2017 at 09:30:50AM +, Chris Wilson wrote:
> On Thu, Jan 26, 2017 at 04:59:21PM +0100, Maarten Lankhorst wrote:
> > When writing some testcases for nonblocking modesets. I found out that the
> > infinite wait on the old fb was causing issues.
>
> The crux of the issue here is
On Fri, Jan 27, 2017 at 10:57:30AM +0100, Lucas Stach wrote:
> Am Donnerstag, den 26.01.2017, 23:56 +0100 schrieb Noralf Trønnes:
> > Make it possible to compile test the driver on other platforms.
> >
> > Cc: l.st...@pengutronix.de
> > Cc: linux+etna...@armlinux.org.uk
> > Cc:
Den 27.01.2017 08.49, skrev Daniel Vetter:
On Thu, Jan 26, 2017 at 11:56:02PM +0100, Noralf Trønnes wrote:
This patchset removes the need for drivers to clean up their debugfs
files on exit. It is done automatically in drm_debugfs_cleanup().
This funtion is also called should the driver error
On Fri, Jan 27, 2017 at 01:50:19PM +, Brian Starkey wrote:
> On Fri, Jan 27, 2017 at 03:27:09PM +0200, Ville Syrjälä wrote:
> >On Fri, Jan 27, 2017 at 10:47:48AM +, Brian Starkey wrote:
> >> Explicitly state the expected CTM equations in the kerneldoc for the CTM
> >> property.
> >>
> >>
On Fri, Jan 27, 2017 at 09:22:47AM +0100, Christian König wrote:
> Am 27.01.2017 um 08:30 schrieb Daniel Vetter:
> > On Fri, Jan 27, 2017 at 07:23:58AM +0100, Thomas Hellstrom wrote:
> > > On 01/27/2017 03:29 AM, Michel Dänzer wrote:
> > > > On 26/01/17 09:46 AM, Sinclair Yeh wrote:
> > > > > On
On Fri, Jan 27, 2017 at 10:36:16AM +0100, Thierry Reding wrote:
> On Fri, Jan 27, 2017 at 08:49:34AM +0100, Daniel Vetter wrote:
> > On Thu, Jan 26, 2017 at 11:56:02PM +0100, Noralf Trønnes wrote:
> > > This patchset removes the need for drivers to clean up their debugfs
> > > files on exit. It is
On Thu, Jan 26, 2017 at 02:46:20PM +, Chris Wilson wrote:
> On Thu, Jan 26, 2017 at 05:32:11PM +0300, Andrey Ryabinin wrote:
> > page_flip_completed() dereferences 'work' variable after executing
> > queue_work(). This is not safe as the 'work' item might be already freed
> > by queued work:
>
On Fri, 27 Jan 2017, Harry Pan wrote:
> When enabling panel backlight, if the current backlight level
> setting matches the panel's minimal, it would apply default policy to
> override the current level by the panel's maximum until next request
> to update brightness, this
On Fri, Jan 27, 2017 at 11:33:04AM +0100, Lucas Stach wrote:
> The fence needs to be cleared out, otherwise the following commit
> might wait on a stale fence from the previous commit. This was fixed
> as a side effect of 9626014258a5 (drm/fence: add in-fences support)
> in kernel 4.10.
>
> As
On Fri, Jan 27, 2017 at 11:00:38AM +0100, Gerd Hoffmann wrote:
> Hi folks,
>
> Problem at hand: A virtual machine, equipped with two display devices,
> one virtual, one physical (using pci pass-through, or kvmgt-based vgpu).
>
> There is no easy way for the user to configure which of the two
On Fri, Jan 27, 2017 at 09:04:25AM +0200, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> From the description of the "DMA-BUF/GEM Object references
> and lifetime overview" it is not clear when exactly
> dma_buf gets destroyed and memory
On Fri, Jan 27, 2017 at 09:20:42AM +0100, Gerd Hoffmann wrote:
> On Do, 2017-01-26 at 23:05 -0200, Gabriel Krisman Bertazi wrote:
> > No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
> > output"). qxl_num_crtc defaults to 4 and is configurable as a module
> > parameter.
>
On Mon, Jan 23, 2017 at 10:09:57PM +0100, Hans de Goede wrote:
> 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
On Mon, Jan 23, 2017 at 10:09:58PM +0100, Hans de Goede wrote:
> Make sure the P-Unit or the PMIC i2c bus is not in use when we send a
> request to the P-Unit by calling iosf_mbi_punit_acquire() / _release()
> around P-Unit write accesses.
Can't we just stuff the calls into the actual punit write
On Fri, Jan 27, 2017 at 03:27:09PM +0200, Ville Syrjälä wrote:
On Fri, Jan 27, 2017 at 10:47:48AM +, Brian Starkey wrote:
Explicitly state the expected CTM equations in the kerneldoc for the CTM
property.
Cc: Ville Syrjälä
Cc: Lionel Landwerlin
On Mon, Jan 23, 2017 at 10:09:56PM +0100, Hans de Goede wrote:
> 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
tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued
head: 920bcd1820a6966b6224f62eadcb4e931bb72e8e
commit: 2eebe4f2d5f4c91edc37801d828ba29edfbc7722 [0/1] drm/color: un-inline
drm_color_lut_extract()
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
make[3]:
On Fri, Jan 27, 2017 at 10:47:48AM +, Brian Starkey wrote:
> Explicitly state the expected CTM equations in the kerneldoc for the CTM
> property.
>
> Cc: Ville Syrjälä
> Cc: Lionel Landwerlin
> Cc: Daniel Vetter
On Fri, Jan 27, 2017 at 04:41:50PM +0530, Shailendra Verma wrote:
> of_match_device could return NULL, and so can cause a NULL
> pointer dereference later.
>
> Signed-off-by: Shailendra Verma
> ---
> drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 13 ++---
> 1 file
On Thu, Jan 26, 2017 at 11:56:10PM +0100, Noralf Trønnes wrote:
> drm_debugfs_cleanup() now removes all minor->debugfs_list entries
> automatically, so the drm_driver.debugfs_cleanup callback is not
> needed.
>
> Cc: liviu.du...@arm.com
> Signed-off-by: Noralf Trønnes
Hi Lucas,
On Fri, Jan 27, 2017 at 8:33 AM, Lucas Stach wrote:
> The fence needs to be cleared out, otherwise the following commit
> might wait on a stale fence from the previous commit. This was fixed
> as a side effect of 9626014258a5 (drm/fence: add in-fences support)
>
On Fri, 27 Jan 2017, Lionel Landwerlin wrote:
> Hi Jani,
>
> Looks good to me :
>
> Reviewed-by: Lionel Landwerlin
Thanks for the reviews, pushed... to drm-intel-next-queued instead of
drm-misc-next. /o\
Dave, Daniel, please advise,
Explicitly state the expected CTM equations in the kerneldoc for the CTM
property.
Cc: Ville Syrjälä
Cc: Lionel Landwerlin
Cc: Daniel Vetter
Signed-off-by: Brian Starkey
---
Hi,
This
Thank for this patch.
It is working fine with sti driver.
Acked-by: Vincent Abriou
Tested-by: Vincent Abriou
Vincent
On 01/26/2017 11:56 PM, Noralf Trønnes wrote:
> drm_debugfs_cleanup() now removes all minor->debugfs_list entries
> automatically,
Am Mittwoch, den 25.01.2017, 09:47 -0200 schrieb Fabio Estevam:
> On Wed, Jan 25, 2017 at 9:30 AM, Lucas Stach wrote:
>
> > Kernel 4.10 just moves the fence attach to the plane state. It has
> > nothing to do with the used commit function. The issue going away if you
> >
The fence needs to be cleared out, otherwise the following commit
might wait on a stale fence from the previous commit. This was fixed
as a side effect of 9626014258a5 (drm/fence: add in-fences support)
in kernel 4.10.
As this commit introduces new functionality and as such can not be
applied to
https://bugs.freedesktop.org/show_bug.cgi?id=99130
Chris Wilson changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.freedesktop.org/show_bug.cgi?id=99130
--- Comment #22 from Dorota Czaplejewicz
---
I haven't seen the underlying slowness causing problems anywhere else yet.
Perhaps we can close this and reopen if it reappears.
--
You are receiving this mail
I hit these two problems while tracking scaling related problems with
omapdrm on DSS5 HW.
Jyri Sarha (2):
Revert "drm: omapdrm: Let the DRM core skip plane commit on inactive
CRTCs"
drm/omapdrm: Move commit_modeset_enables() before commit_planes()
drivers/gpu/drm/omapdrm/omap_crtc.c |
Move drm_atomic_helper_commit_modeset_enables() call to before
drm_atomic_helper_commit_planes() call and have a
omap_atomic_wait_for_completion() call after both.
With the current dss dispc implementation we have to enable the new
modeset before we can commit planes. The dispc ovl configuration
This reverts commit dadf4659d0608e034b6633f30300c2eff2dafb4c.
If planes are not disabled when the they are not on any crtc anymore
they will remain active and may show as "ghosts" when the crtc they
were last on is active again.
Signed-off-by: Jyri Sarha
---
On 01/27/17 00:56, Noralf Trønnes wrote:
> drm_debugfs_cleanup() now removes all minor->debugfs_list entries
> automatically, so the drm_driver.debugfs_cleanup callback is not
> needed. Also remove the unused tilcdc_module_ops.debugfs_cleanup()
> callback. drm_debugfs_cleanup() removes all debugfs
Hi folks,
Problem at hand: A virtual machine, equipped with two display devices,
one virtual, one physical (using pci pass-through, or kvmgt-based vgpu).
There is no easy way for the user to configure which of the two display
devices fbcon should run on. i915 happens to win over bochs-drm or
Am Donnerstag, den 26.01.2017, 23:56 +0100 schrieb Noralf Trønnes:
> Make it possible to compile test the driver on other platforms.
>
> Cc: l.st...@pengutronix.de
> Cc: linux+etna...@armlinux.org.uk
> Cc: christian.gmei...@gmail.com
> Signed-off-by: Noralf Trønnes
I'm not
Am Donnerstag, den 26.01.2017, 23:56 +0100 schrieb Noralf Trønnes:
> drm_debugfs_cleanup() now removes all minor->debugfs_list entries
> automatically, so the drm_driver.debugfs_cleanup callback is not
> needed.
>
> Cc: l.st...@pengutronix.de
> Cc: linux+etna...@armlinux.org.uk
> Cc:
1 - 100 of 118 matches
Mail list logo