On 11/20/2013 03:24 PM, Daniel Vetter wrote:
> On Wed, Nov 20, 2013 at 01:55:49AM -0800, Thomas Hellstrom wrote:
>> Not sure if there are any user-space users of private bo mappings, but
>> if there are, or will be, zapping the COW'd pages when, for example,
>> moving a bo would confuse the user im
attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/40087a52/attachment.html>
edesktop.org/archives/dri-devel/attachments/20131120/5d3fd236/attachment.html>
> clocks = <&tegra_car 34>;
> > resets = <&tegra_car 34>;
> > reset-names = "dma";
> > + #iommu-cells = <1>;
> > };
>
>
> ___
> Mailing list: https://la
On Wednesday 20 November 2013, Stephen Warren wrote:
> > +- #iommu-cells : Must be <1>. This dictates the length of DMA specifiers in
> > + client nodes' dmas properties. The specifier represents the DMA request
> > + select value for the peripheral. For more details, consult the Tegra
> > TRM's
On Wed, Nov 20, 2013 at 08:38:38AM -0800, Ian Romanick wrote:
> From: Ian Romanick
>
> The ioctl expects that certain fields will be zeroed, so we should allow
> the helper function to actually work in non-Valgrind builds.
>
> Signed-off-by: Ian Romanick
> Reported-by: Zhenyu Wang
> Cc: Damien
On Wed, Nov 20, 2013 at 08:38:38AM -0800, Ian Romanick wrote:
> From: Ian Romanick
>
> The ioctl expects that certain fields will be zeroed, so we should allow
> the helper function to actually work in non-Valgrind builds.
>
> Signed-off-by: Ian Romanick
> Reported-by: Zhenyu Wang
> Cc: Damien
On Friday 15 November 2013, Stephen Warren wrote:
> This series implements a common reset framework driver for Tegra, and
> updates all relevant Tegra drivers to use it. It also removes the custom
> DMA bindings and replaced them with the standard DMA DT bindings.
The series is rather long, so I m
https://bugzilla.kernel.org/show_bug.cgi?id=46161
Alan changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=46161
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
ceiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/e8b3782a/attachment.html>
Hi Dave,
Just a small pile of fixes for bugs and a few regressions. I'm still
trying to track down a driver load hang on my g33 (which infuriatingly
doesn't happen when loading the module manually after boot), somehow
bisecting loves to go astray on this one :( And there's a (harmless)
locking WAR
Ugg.. we do actually want to permit FB's in atomic case, since FB will
be looked up like any other object property value.
Currently we do the FB refcnt'ing dance in atomic->commit(), and would
rather not have to special case FB's or collect an FB ref when we look
up the property. Not sure if it i
TODO: probably can split this up into prep patch which splits the
msm_queue_fence_cb out of gem..
---
drivers/gpu/drm/msm/Makefile | 1 +
drivers/gpu/drm/msm/mdp4/mdp4_crtc.c | 48 +---
drivers/gpu/drm/msm/mdp4/mdp4_kms.c | 6 ++
drivers/gpu/drm/msm/mdp4/mdp4_kms.h | 1 +
From: Ville Syrj?l?
The atomic modeset ioctl cna be used to push any number of new values
for object properties. The driver can then check the full device
configuration as single unit, and try to apply the changes atomically.
The ioctl simply takes a list of object IDs and property IDs and their
Break the mutable state of a crtc out into a separate structure
and use atomic properties mechanism to set crtc attributes. This
makes it easier to have some helpers for crtc->set_property()
and for checking for invalid params. The idea is that individual
drivers can wrap the state struct in thei
Break the mutable state of a plane out into a separate structure
and use atomic properties mechanism to set plane attributes. This
makes it easier to have some helpers for plane->set_property()
and for checking for invalid params. The idea is that individual
drivers can wrap the state struct in t
From: Ville Syrj?l?
Refactor the code to check whether an object has a specific property
to a new function.
v1: original
v2: rebase on atomic -- Rob Clark
v3: EINVAL->ENOENT
Signed-off-by: Ville Syrj?l?
---
drivers/gpu/drm/drm_crtc.c | 25 ++---
1 file changed, 14 insertio
From: Ville Syrj?l?
To avoid having to pass object types from userspace for atomic mode
setting ioctl, allow drm_mode_object_find() to look up an object of any
type. This will only work as long as the all object types share the ID
space.
Signed-off-by: Ville Syrj?l?
---
drivers/gpu/drm/drm_crt
Split property values out into a different struct, so we can later
move property values into state structs. This will allow the
property values to stay in sync w/ the state updates which are
either discarded or atomically committed.
And since we are touching all the same code, add support for mut
Add a few more useful helpers to find mode objects.
---
include/drm/drm_crtc.h | 25 +
1 file changed, 25 insertions(+)
diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
index a9b9977..d3abc9c 100644
--- a/include/drm/drm_crtc.h
+++ b/include/drm/drm_crtc.h
@@ -
Flag for range property types indicating that the value is a signed
integer rather than unsigned. For range properties, the signed flag
will trigger use of signed integer comparisions, to handle negative
values properly.
---
drivers/gpu/drm/drm_crtc.c | 15 +++
include/drm/drm_crtc.h
This indicates to userspace that the property is something that can
be set dynamically without requiring a "test" step to check if the
hw is capable. This allows a userspace compositor, such as weston,
to avoid an extra ioctl to check whether it needs to fall-back to
GPU to composite some surface
An object property is an id (idr) for a drm mode object. This
will allow a property to be used set/get a framebuffer, CRTC, etc.
---
drivers/gpu/drm/drm_crtc.c | 34 ++
include/drm/drm_crtc.h | 10 ++
include/uapi/drm/drm_mode.h | 1 +
3 files change
At the moment, this doesn't do anything. But for atomic we will have an
ww_acquire_ctx associated with the state, to simplify the locking and
avoid potential deadlock when we cannot control the locking order.
---
drivers/gpu/drm/drm_crtc.c | 20 +++-
drivers/gpu/drm/i915
The 'atomic' mechanism allows for multiple properties to be updated,
checked, and commited atomically. This will be the basis of atomic-
modeset and nuclear-pageflip.
The basic flow is:
state = dev->atomic_begin();
for (... one or more ...)
obj->set_property(obj, state, prop, value);
Yet another installment of atomic/nuclear modeset/pageflip. Sorry it
took a while since the previous iteration, other tasks came up. But
I hope to not be interrupted so much, because I don't want to spend
the rest of my life rebasing this patchset ;-)
Compared to previous version, I've converted
On Wed, Nov 20, 2013 at 01:55:49AM -0800, Thomas Hellstrom wrote:
> Not sure if there are any user-space users of private bo mappings, but
> if there are, or will be, zapping the COW'd pages when, for example,
> moving a bo would confuse the user immensely since the net effect for the
> user would
https://bugzilla.kernel.org/show_bug.cgi?id=45121
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=50881
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
ou are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/03178b06/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=46161
--- Comment #6 from Brad Jackson ---
It was fixed in one of the releases shortly after I reported it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=46161
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #5 fr
https://bugzilla.kernel.org/show_bug.cgi?id=45121
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 fr
scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/086566d4/attachment-0001.html>
Hi Dave,
More fixes for radeon. This adds new queries for tiling on CIK, and
fixes a crash in handling acpi atif backlight events on CIK.
The following changes since commit 3a118989d58ca9b99f56f16a6fccbe34a9d8047e:
drm/radeon: enable DPM by default in TN asics (2013-11-15 15:57:38 -0500)
are
On Wed, 20 Nov 2013 10:09:59 +
Mark Brown wrote:
> On Wed, Nov 20, 2013 at 10:23:42AM +0100, Jean-Francois Moine wrote:
>
> > But now, I am wondering again about these `empty`codecs:
> > - in a DT context, should we continue to add / modify such codecs?
> > - what do you think about my gener
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/14f218c0/attachment.pgp>
https://bugzilla.kernel.org/show_bug.cgi?id=15850
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=15779
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
e bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/b6d051b5/attachment.html>
Am 13.11.2013 08:45, schrieb Dan Carpenter:
> The "ret = -EIO" is deliberate. It's a very uncommon thing to do and it
> upsets static checkers because they normally would expect "ret == -EIO".
>
> Signed-off-by: Dan Carpenter
>
> diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/dport.c
Hi, Dave!
The set_need_resched() removal fix and yet another fix in
ttm_bo_move_memcpy().
The following changes since commit a3483353ca4e6dbeef2ed62ebed01af109b5b27a:
drm: check for !kdev in drm_unplug_minor() (2013-11-15 20:49:02 +1000)
are available in the git repository at:
git://people
Hi, Dave.
Below is a fix for a false lockep warning,
and the vmwgfx prime implementation.
The following changes since commit a3483353ca4e6dbeef2ed62ebed01af109b5b27a:
drm: check for !kdev in drm_unplug_minor() (2013-11-15 20:49:02 +1000)
are available in the git repository at:
git://people
On 11/20/2013 11:14 AM, David Herrmann wrote:
> Hi
>
> On Wed, Nov 20, 2013 at 10:55 AM, Thomas Hellstrom
> wrote:
>> Not sure if there are any user-space users of private bo mappings, but
>> if there are, or will be, zapping the COW'd pages when, for example,
>> moving a bo would confuse the user
Hi
On Wed, Nov 20, 2013 at 10:55 AM, Thomas Hellstrom
wrote:
> Not sure if there are any user-space users of private bo mappings, but
> if there are, or will be, zapping the COW'd pages when, for example,
> moving a bo would confuse the user immensely since the net effect for the
> user would be
On 11/20/2013 10:03 AM, Arnd Bergmann wrote:
> On Wednesday 20 November 2013, Stephen Warren wrote:
>>> +- #iommu-cells : Must be <1>. This dictates the length of DMA specifiers in
>>> + client nodes' dmas properties. The specifier represents the DMA request
>>> + select value for the peripheral.
On Tue, 19 Nov 2013 14:12:24 +0200
Jyri Sarha wrote:
> Signed-off-by: Jyri Sarha
> ---
> Documentation/devicetree/bindings/sound/hdmi.txt | 17 +
> sound/soc/codecs/hdmi.c | 10 ++
> 2 files changed, 27 insertions(+)
> create mode 100644 Doc
--
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/09c87c68/attachment-0001.pgp>
On 11/20/2013 08:37 AM, Arnd Bergmann wrote:
> On Friday 15 November 2013, Stephen Warren wrote:
>> This series implements a common reset framework driver for Tegra, and
>> updates all relevant Tegra drivers to use it. It also removes the custom
>> DMA bindings and replaced them with the standard D
nce of indirect rendering, which is undesirable anyway.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/8a8de5f3/attachment.html>
From: Ian Romanick
The ioctl expects that certain fields will be zeroed, so we should allow
the helper function to actually work in non-Valgrind builds.
Signed-off-by: Ian Romanick
Reported-by: Zhenyu Wang
Cc: Damien Lespiau
Cc: Daniel Vetter
---
intel/intel_bufmgr_gem.c | 2 +-
1 file chan
assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/31526e70/attachment.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/f04eb1af/attachment.html>
VM_PFNMAP is faster than VM_MIXEDMAP due to reduced page administration so
use it for shared maps where we don't have any Copy-On-Write pages. For
private maps, we continue to use VM_MIXEDMAP.
This might also help a bit for bo mmap dirty tracking, if implemented,
depending on the used interface.
Not sure if there are any user-space users of private bo mappings, but
if there are, or will be, zapping the COW'd pages when, for example,
moving a bo would confuse the user immensely since the net effect for the
user would be that pages written to would lose their contents.
Signed-off-by: Thomas
RD=1]
Even running glxinfo causes this error.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/4a68f84a/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/ba4e7d11/attachment.html>
rted that Worms Reloaded works flawlessly with r600g, so
do I have some strange problem with my 32-bit stack or is this bug peculiar to
radeonsi?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131120/4b3db92e/attachment-0001.html>
59 matches
Mail list logo