On Tue, Mar 26, 2019 at 10:32:03AM +, Liviu Dudau wrote:
> The Device Tree bindings documentation file is in a simplified path
> that doesn't match the MAINTAINERS entry.
>
> Reported-by: Joe Perches
> Signed-off-by: Liviu Dudau
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+),
Remove checkpatch error, "foo* bar" should be "foo *bar".
Signed-off-by: Seung-Woo Kim
---
drivers/gpu/drm/exynos/exynos_drm_g2d.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_g2d.c
b/drivers/gpu/drm/exynos/exynos_drm_g2d.c
index 24
https://bugs.freedesktop.org/show_bug.cgi?id=110143
Timothy Arceri changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #4 from Timothy A
To all X.Org Foundation Members:
The X.Org Foundation's annual election is now open and will remain open until
02:00 UTC on 11 April 2019.
Four of the eight director seats are open during this election, with the four
nominees receiving the highest vote totals serving as directors for two year
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #13 from Diego Viola ---
I can also reproduce the issue with Xephyr -glamor.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@
Hi all,
After merging the drm-intel tree, today's linux-next build (i386
defconfig) failed like this:
In file included from drivers/gpu/drm/i915/intel_guc.h:28:0,
from drivers/gpu/drm/i915/intel_uc.h:27,
from drivers/gpu/drm/i915/intel_uc.c:25:
drivers/gpu/drm/i9
https://bugs.freedesktop.org/show_bug.cgi?id=106571
--- Comment #4 from ukbeas...@protonmail.com ---
Linux 5.0-rc2 had changes to amdgpu that mentioned resume changes.
"drm/amdgpu: Don't ignore rc from drm_dp_mst_topology_mgr_resume()
drm/amdgpu: Don't fail resume process if resuming atomic state
19. 3. 26. 오후 10:51에 Andrzej Hajda 이(가) 쓴 글:
> On 26.03.2019 09:45, Inki Dae wrote:
>> Hi Andrzej,
>>
>> 19. 3. 25. 오후 4:13에 Andrzej Hajda 이(가) 쓴 글:
>>> Hi Inki,
>>>
>>> GSCALERs in Exynos SoCs support conversion between wide range of image
>>> formats,
>>> plus scaling and rotation.
>>> Driver
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #12 from Diego Viola ---
I also tried recompiling xorg-server (git and 1.20.0) and the problem still
persists with those, I can't compile older releases anymore due to compile time
errors.
--
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=202043
--- Comment #7 from mista...@gmail.com ---
Best results performance wise had with following setup:
echo 27500 >> /sys/class/drm/card0/device/hwmon/hwmon0/power1_cap
echo "m 3 1100 1000" > /sys/class/drm/card0/device/pp_od_clk_voltage
GPU clo
https://bugzilla.kernel.org/show_bug.cgi?id=202043
mista...@gmail.com changed:
What|Removed |Added
CC||mista...@gmail.com
--- Comment #6 fr
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #7 from Laurent ---
Ha! I think I've found why the shader output is not good if my guessing about
how the CPU and the GPU works together is good.
I'll try to change it and recompile it to see if it works.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #11 from Diego Viola ---
Tried mesa git (19.1.0-devel) with LLVM 9.0.0 (SVN) and the issue still
persists.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri
Otherwise gcc will complain about unknown types, and declarations
inside parameter lists, if "drm_internal.h" is used in C files with
less headers than what's now typically done under drivers/gpu/drm/.
Signed-off-by: Ahmed S. Darwish
---
Notes:
This was triggered by the in-development drm-pa
https://bugs.freedesktop.org/show_bug.cgi?id=110251
Yuxuan Shui changed:
What|Removed |Added
Hardware|Other |x86-64 (AMD64)
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=110251
Bug ID: 110251
Summary: Buffer age seems incorrect
Product: Mesa
Version: 19.0
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: m
https://bugs.freedesktop.org/show_bug.cgi?id=110251
Yuxuan Shui changed:
What|Removed |Added
Summary|Buffer age seems incorrect |Buffer age seems to be
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #6 from Laurent ---
Mmm... ok it's when I'm using a shader that the bug appears (without shaders,
it works), I'll try to run gallium in Debug mode to see if the shaders outputs
are correct, and if so, this is probably the attached fr
https://bugs.freedesktop.org/show_bug.cgi?id=110250
Bug ID: 110250
Summary: [Regression linux 5.1-rc1] Displayport 1.2 tty second
monitor corruption
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
Hi Ville.
On Tue, Mar 26, 2019 at 07:34:00PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> drm_display_info.name is only ever set by a few panel drveirs but
drivers
Nice clean-up!
Sam
__
On Tue, Mar 26, 2019 at 06:55:33PM +0100, Noralf Trønnes wrote:
> Prepare for moving drm_fb_helper modesetting code to drm_client.
> drm_client will be linked to drm.ko, so move
> __drm_atomic_helper_disable_plane() and __drm_atomic_helper_set_config()
> out of drm_kms_helper.ko.
>
> While at it,
From: Sean Paul
Now that we use the drm psr helpers, we no longer need to hand-roll our
atomic_commit_tail implementation. So use the helper
Changes in v2:
- None
Link to v1:
https://patchwork.freedesktop.org/patch/msgid/20190228210939.83386-6-s...@poorly.run
Cc: Zain Wang
Cc: Tomasz Figa
S
From: Sean Paul
Once we start shutting off the link during PSR, we're going to want fast
training to work. If the display doesn't support fast training, don't
enable psr.
Changes in v2:
- None
Link to v1:
https://patchwork.freedesktop.org/patch/msgid/20190228210939.83386-3-s...@poorly.run
Cc:
From: Sean Paul
Instead of fully disabling and re-enabling the vop on self refresh
transitions, only disable the active windows. This will speed up
self refresh exits substantially and is still a power-savings win.
This patch integrates portions of Zain's patch from here:
https://patchwork.kerne
From: Sean Paul
Instead of rolling our own implementation for tracking when PSR should
be [in]active, use the new self refresh helpers to do the heavy lifting.
Changes in v2:
- updated to reflect changes made in the helpers
Link to v1:
https://patchwork.freedesktop.org/patch/msgid/201902282109
From: Sean Paul
This patch adds a new drm helper library to help drivers implement
self refresh. Drivers choosing to use it will register crtcs and
will receive callbacks when it's time to enter or exit self refresh
mode.
In its current form, it has a timer which will trigger after a
driver-spec
On Tue, Mar 26, 2019 at 06:55:46PM +0100, Noralf Trønnes wrote:
> drm_dev_register() initializes internal clients like bootsplash as the
> last thing it does, so all setup needs to be done at this point.
>
> Fix by calling vc4_kms_load() before registering.
> Also check the error code returned fro
Hi,
So what's the status of it?
Has it been merged? I don't see it in drm-misc-next.
Regards,
Vasily
On Tue, Mar 12, 2019 at 1:12 AM Heiko Stuebner wrote:
>
> Hi,
>
> Am Dienstag, 12. März 2019, 02:54:57 CET schrieb Qiang Yu:
> > On Mon, Mar 11, 2019 at 11:37 PM Rob Herring wrote:
> > >
> > >
On Thu, Mar 21, 2019 at 06:00:45PM +, Måns Rullgård wrote:
> Maxime Ripard writes:
>
> > On Tue, Mar 19, 2019 at 12:48:19PM +, Måns Rullgård wrote:
> >> Maxime Ripard writes:
> >>
> >> > On Mon, Mar 18, 2019 at 04:23:56PM +, Måns Rullgård wrote:
> >> >> Maxime Ripard writes:
> >> >>
https://bugs.freedesktop.org/show_bug.cgi?id=110143
--- Comment #3 from h...@inbox.lv ---
(In reply to andrew.m.mcmahon from comment #2)
> Just out of interest RBDoom3-BFG works perfectly.
> Consider compiling the latest master rather than running Doom 3 through
> Wine/Proton. Your RX580 shouldn't
-Original Message-
From: Taylor, Clinton A
Sent: Thursday, March 21, 2019 3:42 PM
To: dri-devel@lists.freedesktop.org
Cc: Taylor, Clinton A
Subject: [PATCH] drm/dp: Add DP phy test pattern DPCD bit definitions
From: Clinton Taylor
Added PHY_TEST_PATTERN_SEL bit definitions for DPCD 0
On Tue, Mar 26, 2019 at 06:55:32PM +0100, Noralf Trønnes wrote:
> For each enabled crtc the functions sets dpms on all registered connectors.
> Limit this to only doing it once and on the connectors actually in use.
>
> Signed-off-by: Noralf Trønnes
Fixes: 023eb571a1d0 ("drm: correctly update con
On Tue, Mar 26, 2019 at 06:55:31PM +0100, Noralf Trønnes wrote:
> The gamma_size variable has not been used since
> commit 4abe35204af8 ("drm/kms/fb: use slow work mechanism for normal hotplug
> also.")
>
> While in the area move a comment back to its code block.
> They got separated by
> commit
On Tue, Mar 26, 2019 at 06:47:41PM +0200, Ville Syrjälä wrote:
> On Tue, Mar 26, 2019 at 10:17:44AM +0100, Thomas Zimmermann wrote:
> > Mode detection currently reports the modes listed in fb_info::modelist.
> > The list is either build from EDID information or, more often, a list of
> > previously
On Tue, Mar 26, 2019 at 07:38:10PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Just use a pointer to the display_info rather than make a copy
> on stack.
>
> Cc: Maxime Ripard
> Signed-off-by: Ville Syrjälä
Reviewed-by: Daniel Vetter
> ---
> drivers/gpu/drm/sun4i/sun4i_tcon.c | 8
On Tue, Mar 26, 2019 at 07:34:01PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Remove the unused DRM_DISPLAY_INFO_LEN from the uapi headers.
> I presume the original plan was to expose the display name
> via getconnector, but looks like that never happened. So we have
> the define for t
On Tue, Mar 26, 2019 at 07:34:00PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> drm_display_info.name is only ever set by a few panel drveirs but
> never actually used anywhere except in i915 debugfs code. Trash it.
>
> Signed-off-by: Ville Syrjälä
Huh, nice find.
Reviewed-by: Daniel
On Tue, Mar 26, 2019 at 07:33:59PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> A set of 8 spaces has snuck in. Replace with a tab, and
> toss in an extra newline while at it.
>
> Signed-off-by: Ville Syrjälä
> ---
> include/drm/drm_connector.h | 3 ++-
> 1 file changed, 2 insertions(
On Tue, Mar 26, 2019 at 07:33:58PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> drm_display_info.pixel_clock is unused. Let's get rid of it.
>
> Signed-off-by: Ville Syrjälä
> ---
> include/drm/drm_connector.h | 6 --
> 1 file changed, 6 deletions(-)
>
> diff --git a/include/drm/
On Tue, Mar 26, 2019 at 07:38:10PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Just use a pointer to the display_info rather than make a copy
> on stack.
>
> Cc: Maxime Ripard
> Signed-off-by: Ville Syrjälä
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and
Add display abstraction and helpers to probe for displays and commit
modesets.
TODO:
If the bootsplash client doesn't need to subclass drm_client_display,
the callbacks can be removed.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c | 415 +++
incl
An example to showcase the client API.
TODO:
A bootsplash client needs a way to tell drm_fb_helper to stay away,
otherwise it will chime in on setup and hotplug.
Most DRM drivers register fbdev before calling drm_dev_register() (the
generic emulation is an exception). This have to be reversed for
drm_dev_register() initializes internal clients like bootsplash as the
last thing it does, so all setup needs to be done at this point.
Fix by calling vc4_kms_load() before registering.
Also check the error code returned from that function.
Cc: Eric Anholt
Signed-off-by: Noralf Trønnes
---
dri
drm_fb_helper_is_bound() is used to check if DRM userspace is in control.
This is done by looking at the fb on the primary plane. By the time
fb-helper gets around to committing, it's possible that the facts have
changed.
Avoid this race by holding the drm_device->master_mutex lock while
committin
No functional changes, just moving code as-is and fixing includes.
There is one addition and that is exporting drm_client_modesets_probe().
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c| 698
drivers/gpu/drm/drm_fb_helper.c | 697
This prepares the modeset code so it can be moved out as-is in the next
patch.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 75 +
include/drm/drm_fb_helper.h | 4 --
2 files changed, 57 insertions(+), 22 deletions(-)
diff --git a/drive
All drivers add all their connectors so there's no need to keep around an
array of available connectors.
Rename functions which signature is changed since they will be moved to
drm_client in a later patch.
Signed-off-by: Noralf Trønnes
---
checkpatch complains, but I'm unable to satisfy it:
ER
It is generic code and having it in the helper will let other drivers
benefit from it.
One change was necessary assuming this to be true:
INTEL_INFO(dev_priv)->num_pipes == dev->mode_config.num_crtc
Suggested-by: Daniel Vetter
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Cc: intel-...
Move the modeset commit code to drm_client.
No changes except exporting API.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c| 236
drivers/gpu/drm/drm_fb_helper.c | 232 ---
include/drm/drm_client.h| 3 +
3
The values are already present in the modeset.
This is done in preparation for the removal of struct drm_fb_helper_crtc.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 12
include/drm/drm_fb_helper.h | 2 --
2 files changed, 4 insertions(+), 10 deletions(-
This moves the modesetting code from drm_fb_helper to drm_client so it
can be shared by all internal clients.
I have also added a client display abstraction and a bootsplash example
client to show where this might be heading. Hopefully Max Staudt will be
able to pick up his bootsplash work now.
N
This makes the necessary changes so the commit code can be moved out to
drm_client as-is in the next patch. It's split up to ease review.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 93 +
1 file changed, 59 insertions(+), 34 deletions(-)
d
It now only contains the modeset so use that directly instead. The modeset
code will be moved to drm_client, so add code there.
The modeset connector array size is hardcoded for the cloned case to avoid
having to pass in a value from the driver. A value of 8 is chosen to err
on the safe side. This
Prepare for moving drm_fb_helper modesetting code to drm_client.
drm_client will be linked to drm.ko, so move
__drm_atomic_helper_disable_plane() and __drm_atomic_helper_set_config()
out of drm_kms_helper.ko.
While at it, fix two checkpatch complaints:
- WARNING: Block comments use a trailing */ o
The gamma_size variable has not been used since
commit 4abe35204af8 ("drm/kms/fb: use slow work mechanism for normal hotplug
also.")
While in the area move a comment back to its code block.
They got separated by
commit d50ba256b5f1 ("drm/kms: start adding command line interface using fb.").
Sign
Getting rotation info is cheap so we can do it on demand.
This is done in preparation for the removal of struct drm_fb_helper_crtc.
Cc: Hans de Goede
Signed-off-by: Noralf Trønnes
---
Hans,
You had this comment inline in restore_fbdev_mode_atomic() the last time
I sent this out:
We want p
For each enabled crtc the functions sets dpms on all registered connectors.
Limit this to only doing it once and on the connectors actually in use.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/dr
On 3/22/19 4:04 PM, Mario Kleiner wrote:
> In VRR mode, proper vblank/pageflip timestamps can only be computed
> after the display scanout position has left front-porch. Therefore
> delay calls to drm_crtc_handle_vblank(), and thereby calls to
> drm_update_vblank_count() and pageflip event delivery
From: Ville Syrjälä
Just use a pointer to the display_info rather than make a copy
on stack.
Cc: Maxime Ripard
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/sun4i/sun4i_tcon.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/sun4i/sun4i_tcon.c
b/
From: Ville Syrjälä
A set of 8 spaces has snuck in. Replace with a tab, and
toss in an extra newline while at it.
Signed-off-by: Ville Syrjälä
---
include/drm/drm_connector.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/drm/drm_connector.h b/include/drm/drm_con
From: Ville Syrjälä
Remove the unused DRM_DISPLAY_INFO_LEN from the uapi headers.
I presume the original plan was to expose the display name
via getconnector, but looks like that never happened. So we have
the define for the length of the string but no string anywhere.
A quick scan didn't seem t
From: Ville Syrjälä
drm_display_info.name is only ever set by a few panel drveirs but
never actually used anywhere except in i915 debugfs code. Trash it.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_debugfs.c| 1 -
drivers/gpu/drm/panel/panel-arm-versatile.c
From: Ville Syrjälä
drm_display_info.pixel_clock is unused. Let's get rid of it.
Signed-off-by: Ville Syrjälä
---
include/drm/drm_connector.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
index bb3bd8e1633a..fcdca46e0c24 1006
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #5 from Laurent ---
The code is too large, there are a lot of folders and they are a lot of
pointers to functions so it's very difficult to find where a specific function
is called, and anyway, when I tried to compile the driver to s
From: Jérôme Glisse
This update each existing invalidation to use the correct mmu notifier
event that represent what is happening to the CPU page table. See the
patch which introduced the events to see the rational behind this.
Signed-off-by: Jérôme Glisse
Cc: Andrew Morton
Cc: linux...@kvack.
From: Jérôme Glisse
CPU page table update can happens for many reasons, not only as a result
of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) but also
as a result of kernel activities (memory compression, reclaim, migration,
...).
Users of mmu notifier API track changes to the CPU p
From: Jérôme Glisse
Helper to test if a range is updated to read only (it is still valid
to read from the range). This is useful for device driver or anyone
who wish to optimize out update when they know that they already have
the range map read only.
Signed-off-by: Jérôme Glisse
Cc: Andrew Mor
From: Jérôme Glisse
Use the mmu_notifier_range_blockable() helper function instead of
directly dereferencing the range->blockable field. This is done to
make it easier to change the mmu_notifier range field.
This patch is the outcome of the following coccinelle patch:
%<
From: Jérôme Glisse
CPU page table update can happens for many reasons, not only as a result
of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) but also
as a result of kernel activities (memory compression, reclaim, migration,
...).
Users of mmu notifier API track changes to the CPU p
From: Jérôme Glisse
CPU page table update can happens for many reasons, not only as a result
of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) but also
as a result of kernel activities (memory compression, reclaim, migration,
...).
This patch introduce a set of enums that can be asso
On Tue, Mar 26, 2019 at 10:17:44AM +0100, Thomas Zimmermann wrote:
> Mode detection currently reports the modes listed in fb_info::modelist.
> The list is either build from EDID information or, more often, a list of
> previously set modes. A later update to the mode detection could also
> take into
From: Jérôme Glisse
Use an unsigned field for flags other than blockable and convert
the blockable field to be one of those flags.
Signed-off-by: Jérôme Glisse
Cc: Andrew Morton
Cc: linux...@kvack.org
Cc: Christian König
Cc: Joonas Lahtinen
Cc: Jani Nikula
Cc: Rodrigo Vivi
Cc: Jan Kara
Cc
From: Jérôme Glisse
(Andrew this apply on top of my HMM patchset as otherwise you will have
conflict with changes to mm/hmm.c)
Changes since v5:
- drop KVM bits waiting for KVM people to express interest if they
do not then i will post patchset to remove change_pte_notify as
wit
From: Jérôme Glisse
Simple helpers to test if range invalidation is blockable. Latter
patches use cocinnelle to convert all direct dereference of range->
blockable to use this function instead so that we can convert the
blockable field to an unsigned for more flags.
Signed-off-by: Jérôme Glisse
https://bugs.freedesktop.org/show_bug.cgi?id=110199
--- Comment #5 from Daniel Stone ---
> Please don't post outside your own bug reports if you're not contributing
> with anything useful. This is not Phoronix or a discussion forum.
Sigh. This person constantly spams every bug report with usele
On Tue, Mar 26, 2019 at 10:17:40AM +0100, Thomas Zimmermann wrote:
> Signed-off-by: Thomas Zimmermann
> ---
> drivers/gpu/drm/fbdevdrm/Makefile | 1 +
> drivers/gpu/drm/fbdevdrm/fbdevdrm_format.c | 441 +
> drivers/gpu/drm/fbdevdrm/fbdevdrm_format.h | 26 ++
> 3 fi
https://bugs.freedesktop.org/show_bug.cgi?id=110249
--- Comment #6 from Eero Tamminen ---
intel_gpu_top works fine now. Large difference in ldd output, and it's still
small:
$ size intel_gpu_top
textdata bss dec hex filename
211021204 304 226105852 /opt/instal
https://bugs.freedesktop.org/show_bug.cgi?id=110199
--- Comment #4 from bmil...@gmail.com ---
(In reply to fin4478 from comment #3)
> You both have cheap low quality Sapphire cards with 2 year warranty here
> when Asus has 3 years. Custom bios in those cards are famous to cause
> problems with Lin
https://bugs.freedesktop.org/show_bug.cgi?id=110249
--- Comment #5 from Chris Wilson ---
One down, the rest left to an adventurous sole.
commit a350b9f9f606296b1599c3617c8530a8985709e2 (HEAD, upstream/master)
Author: Chris Wilson
Date: Tue Mar 26 13:26:26 2019 +
tools/intel-gpu-top:
On Tue, 2019-03-26 at 10:17 +0100, Thomas Zimmermann wrote:
> +static bool is_generic_driver(const struct fb_info *fb_info)
> +{
> + /* DRM porting note: We don't want to bind to vga16fb, vesafb, or any
> + * other generic fbdev driver. Usually, these drivers have limited
> + * capab
On Tue, Mar 26, 2019 at 02:53:49PM +, Chris Wilson wrote:
> Quoting Mika Kuoppala (2019-03-26 09:30:57)
> > Dan Carpenter writes:
> >
> > > The live_context() function returns error pointers. It never returns
> > > NULL.
> > >
> > > Fixes: 9c1477e83e62 ("drm/i915/selftests: Exercise adding r
On Wed, Nov 28, 2018 at 8:17 AM Maarten Lankhorst
wrote:
>
> Op 27-11-18 om 18:34 schreef Daniel Vetter:
> > KMS drivers really should all be able to restore their display state
> > on resume without fbcon helping out. So make this the default.
> >
> > Since I'm not entirely foolish, make it only
Den 26.03.2019 14.20, skrev Daniel Vetter:
> Not used by drivers anymore.
>
> v2: Rebase
>
> Signed-off-by: Daniel Vetter
> ---
Reviewed-by: Noralf Trønnes
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mai
Den 26.03.2019 14.20, skrev Daniel Vetter:
> This should not result in any changes.
>
> v2: Rebase over vbox changes - vbox gained it's own line to fill
> fix.id.
>
> v3: Rebase
>
> Reviewed-by: Greg Kroah-Hartman (v2)
> Signed-off-by: Daniel Vetter
> Cc: Greg Kroah-Hartman
> Cc: Hans de Go
Den 26.03.2019 14.20, skrev Daniel Vetter:
> This should not result in any changes.
>
> v2: Rebase
>
> Signed-off-by: Daniel Vetter
> Cc: Dave Airlie
> Cc: Sean Paul
> Cc: Mikulas Patocka
> Cc: Daniel Vetter
> Cc: Greg Kroah-Hartman
> Cc: Emil Lundmark
> ---
> drivers/gpu/drm/udl/udl_fb
On Tue, Mar 26, 2019 at 02:20:05PM +0100, Daniel Vetter wrote:
> Another driver that didn't set fbinfo->fix.id before.
>
> v2: Fix subject and rebase
>
> Acked-by: Thierry Reding
> Signed-off-by: Daniel Vetter
> Cc: Thierry Reding
> Cc: Jonathan Hunter
> Cc: linux-te...@vger.kernel.org
> ---
Quoting Mika Kuoppala (2019-03-26 09:30:57)
> Dan Carpenter writes:
>
> > The live_context() function returns error pointers. It never returns
> > NULL.
> >
> > Fixes: 9c1477e83e62 ("drm/i915/selftests: Exercise adding requests to a
> > full GGTT")
> > Signed-off-by: Dan Carpenter
>
> Reviewe
Den 26.03.2019 14.20, skrev Daniel Vetter:
> Another driver that didn't set fbinfo->fix.id before.
>
> v2: Fix subject and rebase
>
> Acked-by: Thierry Reding
> Signed-off-by: Daniel Vetter
> Cc: Thierry Reding
> Cc: Jonathan Hunter
> Cc: linux-te...@vger.kernel.org
> ---
Reviewed-by: Nora
On Tue, Mar 26, 2019 at 10:17:33AM +0100, Thomas Zimmermann wrote:
> Hi,
>
> this RFC patch set implements fbdevdrm, a DRM driver on top of fbdev
> drivers. I'd appreciate feedback on the code and the idea in general.
>
> The fbdev subsystem is considered legacy and will probably be removed at
>
Den 26.03.2019 14.20, skrev Daniel Vetter:
> This will set an fb name for the first time!
>
> v2: Rebase
>
> Reviewed-by: Heiko Stuebner
> Signed-off-by: Daniel Vetter
> Cc: Sandy Huang
> Cc: "Heiko Stübner"
> Cc: linux-arm-ker...@lists.infradead.org
> Cc: linux-rockc...@lists.infradead.org
Den 26.03.2019 14.20, skrev Daniel Vetter:
> This should not result in any changes.
>
> v2: Rebase
>
> Signed-off-by: Daniel Vetter
> Cc: Alex Deucher
> Cc: "Christian König"
> Cc: "David (ChunMing) Zhou"
> Cc: amd-...@lists.freedesktop.org
> ---
Acked-by: Noralf Trønnes
_
Den 26.03.2019 14.20, skrev Daniel Vetter:
> This changes the fb name from "omapdrm" to "omapdrmfb".
>
> v2: Rebase
>
> Signed-off-by: Daniel Vetter
> Cc: Tomi Valkeinen
> ---
Reviewed-by: Noralf Trønnes
___
dri-devel mailing list
dri-devel@lists.
Den 26.03.2019 14.20, skrev Daniel Vetter:
> This changes the fb name from "nouveaufb" to "nouveaudrmfb".
>
> Aside: I wonder whether the in_interrupt() check is good enough for
> the nouveau acceleration. Cargo-cult says drm_can_sleep() is needed,
> which isn't actually working if you pick a .c
Den 26.03.2019 15.42, skrev Noralf Trønnes:
>
>
> Den 26.03.2019 14.20, skrev Daniel Vetter:
>> This will change the fb name from "msm" to "msmdrmfb".
>>
>> v2: Rebase
>>
>> Signed-off-by: Daniel Vetter
>> Cc: Rob Clark
>> Cc: linux-arm-...@vger.kernel.org
>> Cc: freedr...@lists.freedesktop.o
https://bugs.freedesktop.org/show_bug.cgi?id=110249
--- Comment #4 from Eero Tamminen ---
(In reply to Chris Wilson from comment #3)
> The autotools build doesn't have this problem because in there intel-gpu-top
> is not linked against libigt.la, as nothing outside of tests/ should be. It
> looks
Den 26.03.2019 14.20, skrev Daniel Vetter:
> This will change the fb name from "msm" to "msmdrmfb".
>
> v2: Rebase
>
> Signed-off-by: Daniel Vetter
> Cc: Rob Clark
> Cc: linux-arm-...@vger.kernel.org
> Cc: freedr...@lists.freedesktop.org
> ---
Reviewed-by: Noralf Trønnes
___
Den 26.03.2019 14.19, skrev Daniel Vetter:
> Should not result in any changes.
It changes the name, so:
Only changes the name of the fb from "mgadrmfb" to "mga200drmfb".
Acked-by: Noralf Trønnes
>
> v2: Rebase
>
> Signed-off-by: Daniel Vetter
> Cc: Dave Airlie
> Cc: Alex Deucher
> Cc: "
https://bugs.freedesktop.org/show_bug.cgi?id=110249
--- Comment #3 from Chris Wilson ---
The autotools build doesn't have this problem because in there intel-gpu-top is
not linked against libigt.la, as nothing outside of tests/ should be. It looks
like a bit of carelessness introduced the extra d
On Tue, Mar 26, 2019 at 9:21 AM Daniel Vetter wrote:
>
> Not used by drivers anymore.
>
> v2: Rebase
>
> Signed-off-by: Daniel Vetter
Other than the spelling typos noted by Noralf, the series is:
Reviewed-by: Alex Deucher
> ---
> drivers/gpu/drm/drm_fb_helper.c | 38 +
Den 26.03.2019 14.19, skrev Daniel Vetter:
> This changes the fb name from "inteldrmfb" to "i915drmfb".
>
> v2: Rebase
>
> Signed-off-by: Daniel Vetter
> Cc: Jani Nikula
> Cc: Joonas Lahtinen
> Cc: Rodrigo Vivi
> Cc: intel-...@lists.freedesktop.org
> ---
Reviewed-by: Noralf Trønnes
__
1 - 100 of 214 matches
Mail list logo
