attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/5d3fbd39/attachment-0001.html>
On Tue, May 31, 2016 at 05:24:30PM +0800, Liu Ying wrote:
> To support generic atomic page flip, this patch customizes ->atomic_commit
> for nonblock commits.
>
> Signed-off-by: Liu Ying
> ---
> v1->v2:
> * s/async/nonblock/ on this patch to address Daniel Vetter's comment.
> * Wait for pending c
On Tue, May 31, 2016 at 12:02:23PM +0100, Liviu Dudau wrote:
> On Sun, May 29, 2016 at 08:35:13PM +0200, Daniel Vetter wrote:
> > Again, just doing them as blocking commits isn't cool.
> >
> > From a cursory check hdlcd does seem to at least try to handle
> > drm_pending_vblank_event, so hopefully
On Tue, May 31, 2016 at 11:13:27AM +0200, Lukas Wunner wrote:
> Daniel Vetter pointed out that vga_switcheroo_client_probe_defer() could
> be needed by audio clients as well. To avoid mistakes when someone adds
> conditions for these in the future, constrain the single existing
> condition to VGA c
On Tue, May 31, 2016 at 12:03:04PM +0100, Liviu Dudau wrote:
> The HDLCD atomic_commit code was mis-using the drm_atomic_helper_commit()
> function to implement the non-blocking code. Replace that with the correct
> implementation that does the async queue-ing of commits.
>
> Signed-off-by: Liviu
On Mon, May 30, 2016 at 07:03:46PM +0200, Peter Wu wrote:
> On Sun, May 29, 2016 at 05:50:06PM +0200, Lukas Wunner wrote:
> > How exactly did you reach the situation where the root port didn't wake
> > up when you tried to load nouveau again? (IRC conversation this week.)
>
> Ensure that the pci/p
These fix two atomic modesetting issues on v4.7-rc1. The last one is a bit of
an RFC.
Changes to v1:
- drop unnecessary cleanups from "drm: make drm_atomic_set_mode_prop_for_crtc()
more reliable".
- Cc stable where appropriate
- Add "Fixes:" to "drm: fix fb refcount issue with atomic modesettin
When setting mode via MODE_ID property,
drm_atomic_set_mode_prop_for_crtc() does not call
drm_mode_set_crtcinfo() which possibly causes:
"[drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 32: Can't
calculate constants, dotclock = 0!"
Whether the error is seen depends on the previous data i
Commit 652353e6e561c2aeeac62df183f721f6f9b5b45f ("drm/sti: set CRTC
modesetting parameters") added a hack to avoid warnings related to
setting mode with atomic API. With the previous patch, the hack should
no longer be necessary.
Signed-off-by: Tomi Valkeinen
Cc: Benjamin Gaignard
Cc: Vincent Ab
drm_atomic_set_mode_prop_for_crtc() does not clear the state->mode, so
old data may be left there when a new mode is set, possibly causing odd
issues.
This patch improves the situation by always clearing the state->mode
first.
Signed-off-by: Tomi Valkeinen
Cc: stable at vger.kernel.org
---
driv
After commit 027b3f8ba9277410c3191d72d1ed2c6146d8a668 ("drm/modes: stop
handling framebuffer special") extra fb refs are left around when doing
atomic modesetting.
The problem is that the new drm_property_change_valid_get() does not
return anything in the '**ref' parameter, which causes
drm_proper
On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote:
> Do you have any suggestions for the case where the pcieport driver
> refuses to put the bridge in D3 (because the BIOS is too old)? In that
> case the nouveau driver needs to fallback to the DSM method (but not
> when runtime PM is deliber
2016-05-30 3:35 GMT+09:00 Daniel Vetter :
> We want to hide drm_atomic_state internals better.
>
Acked-by: Inki Dae
> Cc: Inki Dae
> Signed-off-by: Daniel Vetter
> ---
> drivers/gpu/drm/exynos/exynos_drm_drv.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/dr
Op 31-05-16 om 12:46 schreef Daniel Vetter:
> On Tue, May 31, 2016 at 10:43:56AM +0200, Maarten Lankhorst wrote:
>> Op 30-05-16 om 17:09 schreef Daniel Vetter:
>>> On Mon, May 30, 2016 at 03:08:39PM +0200, Maarten Lankhorst wrote:
Op 29-05-16 om 20:35 schreef Daniel Vetter:
> - dev is redu
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/3cc648f7/attachment.sig>
On Tue, May 31, 2016 at 12:53:12PM +0200, Gerd Hoffmann wrote:
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/drm_crtc.c | 2 ++
> include/drm/drm_crtc.h | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> index d2a6d9
Pick up the correct source rectangle from framebuffer.
Without this multihead setups are not working correctly.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_plane.c | 31 ++-
1 file changed, 18 insertions(+), 13 deletions(-)
diff --git a/drivers/gp
On Mon, May 30, 2016 at 5:59 PM, Ulrich Hecht
wrote:
> Hi!
>
> This is a prototype of HDMI output support for the Renesas r8a7795 SoC and
> Salvator-X board. It is based on the renesas-devel-20160516-v4.6 tree and
Actually, it is based on renesas-drivers-2016-05-17-
v4.6, sorry for the confusion
On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote:
> Do you have any suggestions for the case where the pcieport driver
> refuses to put the bridge in D3 (because the BIOS is too old)? In that
> case the nouveau driver needs to fallback to the DSM method (but not
> when runtime PM is deliber
On Tue, May 31, 2016 at 01:34:43PM +0200, Lukas Wunner wrote:
> On Mon, May 30, 2016 at 07:03:46PM +0200, Peter Wu wrote:
> > On Sun, May 29, 2016 at 05:50:06PM +0200, Lukas Wunner wrote:
> > > How exactly did you reach the situation where the root port didn't wake
> > > up when you tried to load n
On Tue, May 31, 2016 at 11:43:56AM +0300, Mika Westerberg wrote:
> On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote:
> > Do you have any suggestions for the case where the pcieport driver
> > refuses to put the bridge in D3 (because the BIOS is too old)? In that
> > case the nouveau driver
CCing danvet
Thorsten Leemhuis wrote on 28.04.2016 10:37:
> Kenneth Graunke wrote on 28.04.2016 03:05:
>> On Wednesday, April 27, 2016 9:37:07 AM PDT Thorsten Leemhuis wrote:
>>> Thorsten Leemhuis wrote on 26.04.2016 13:41:
>>> Forget that patch -- a way better one was submitted weeks ago my Micha
On Tue, May 31, 2016 at 03:03:17PM +0300, Tomi Valkeinen wrote:
> drm_atomic_set_mode_prop_for_crtc() does not clear the state->mode, so
> old data may be left there when a new mode is set, possibly causing odd
> issues.
>
> This patch improves the situation by always clearing the state->mode
> fi
Op 30-03-16 om 11:51 schreef Daniel Vetter:
> Code stolen from gma500.
It would be useful to mention why this is done. :)
But even with this patch it seems the legacy gamma in gamma_get is not very
reliable.
A failed call to gamma_set could leave wrong values in crtc->gamma_store either
by calli
On Di, 2016-05-31 at 15:36 +0300, Ville Syrjälä wrote:
> Why store it in the fb and not eg. the plane state?
Well, drm_plane_state is allocated by drm_atomic_helper_update_plane.
When sticking the hotspot into the the plane state we have to add hot_x
and hot_y parameters to drm_plane_funcs->up
Op 30-03-16 om 11:51 schreef Daniel Vetter:
> DRM fbdev emulation only supports pallete_color with depth == 8, and
> truecolor with depth > 8. Handling depth == 16 for palettes is hence
> dead code, let's remove it.
Hooray, less chance for failure!
Reviewed-by: Maarten Lankhorst
Op 30-03-16 om 11:51 schreef Daniel Vetter:
> The core does this for us already.
Unfortunately some other drivers do the same. :(
various variations of
end = min_t(start + size, 256);
I'll kill the rest off when killing start parameter and returning int.
Reviewed-by: Maarten Lankhorst
On Tue, May 31, 2016 at 01:07:15PM +0200, Daniel Vetter wrote:
> On Tue, May 31, 2016 at 12:02:23PM +0100, Liviu Dudau wrote:
> > On Sun, May 29, 2016 at 08:35:13PM +0200, Daniel Vetter wrote:
> > > Again, just doing them as blocking commits isn't cool.
> > >
> > > From a cursory check hdlcd does
Op 30-03-16 om 11:51 schreef Daniel Vetter:
> Again the fbdev emulation gamma_set/get functions are only needed for
> drivers that try to also use 8bpp paletted mode. Which msm doesn't, so
> this is dead code. Let's rip it out.
>
> Cc: Rob Clark
> Signed-off-by: Daniel Vetter
Reviewed-by: Maarten
Op 30-03-16 om 11:51 schreef Daniel Vetter:
> qxl doesn't have any functions for setting the gamma table, so this is
> completely defunct.
>
> Not nice to lie to userspace, so let's stop!
Reviewed-by: Maarten Lankhorst
On Mon, May 30, 2016 at 1:53 PM, Daniel Vetter
wrote:
> No dev->struct_mutex anywhere to be seen.
>
> Cc: seanpaul at chromium.org
> Signed-off-by: Daniel Vetter
Reviewed-by: Sean Paul
> ---
> drivers/gpu/drm/vgem/vgem_drv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --
On Tue, May 31, 2016 at 03:05:32PM +0200, Maarten Lankhorst wrote:
> Op 30-03-16 om 11:51 schreef Daniel Vetter:
> > Code stolen from gma500.
> It would be useful to mention why this is done. :)
>
> But even with this patch it seems the legacy gamma in gamma_get is not very
> reliable.
> A failed
On Tue, May 31, 2016 at 03:09:42PM +0200, Maarten Lankhorst wrote:
> Op 30-03-16 om 11:51 schreef Daniel Vetter:
> > DRM fbdev emulation only supports pallete_color with depth == 8, and
> > truecolor with depth > 8. Handling depth == 16 for palettes is hence
> > dead code, let's remove it.
> Hooray
On Tue, May 31, 2016 at 03:17:57PM +0200, Maarten Lankhorst wrote:
> Op 30-03-16 om 11:51 schreef Daniel Vetter:
> > qxl doesn't have any functions for setting the gamma table, so this is
> > completely defunct.
> >
> > Not nice to lie to userspace, so let's stop!
> Reviewed-by: Maarten Lankhorst
On Tue, May 31, 2016 at 09:20:07AM -0400, Sean Paul wrote:
> On Mon, May 30, 2016 at 1:53 PM, Daniel Vetter
> wrote:
> > No dev->struct_mutex anywhere to be seen.
> >
> > Cc: seanpaul at chromium.org
> > Signed-off-by: Daniel Vetter
>
> Reviewed-by: Sean Paul
Applied to drm-misc, thanks for t
Op 31-05-16 om 15:24 schreef Daniel Vetter:
> On Tue, May 31, 2016 at 03:05:32PM +0200, Maarten Lankhorst wrote:
>> Op 30-03-16 om 11:51 schreef Daniel Vetter:
>>> Code stolen from gma500.
>> It would be useful to mention why this is done. :)
>>
>> But even with this patch it seems the legacy gamma
Hi Daniel!
On 30 May 2016 at 23:22, Daniel Vetter wrote:
> HI all,
>
> Here's the pile of lockless gem BO free conversion patches. Assuming I didn't
> botch it these are all the ones that didn't yet get an ack. Since this is all
> pretty boring stuff I'll just send a pull request to Dave later th
On Tue, 2016-05-31 at 10:51 +0300, Jani Nikula wrote:
> On Mon, 30 May 2016, James Bottomley <
> James.Bottomley at HansenPartnership.com> wrote:
> > I've tested a pristine 4.6.0 system, so it's definitely something
> > that
> > went in during the merge window. The flicker isn't continuous,
> > it
omapdrm is using much too generic Kconfig names for its panels and
encoders. Rename them to have "DRM_OMAP" in the name.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/displays/Kconfig | 28 ++--
drivers/gpu/drm/omapdrm/displays/Makefile | 28 ++---
The full name of PSR is Panel Self Refresh, panel device could refresh
itself with the hardware framebuffer in panel, this would make a lots
of sense to save the power consumption.
For example, when desktop haven't change the context for a long time,
then we could refresh the data to the hardware
EDP PSR function is interesting in vblank enable or disable event,
so it would be great introduce a way to notify encoder about this
event.
Signed-off-by: Yakir Yang
---
drivers/gpu/drm/rockchip/Makefile | 2 +-
drivers/gpu/drm/rockchip/rockchip_drm_notify.c | 66 ++
The full name of PSR is Panel Self Refresh, panel device could refresh
itself with the hardware framebuffer in panel, this would make a lots
of sense to save the power consumption.
For example, when desktop haven't change the context for a long time,
then we could refresh the data to the hardware
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/0feccc41/attachment.html>
On Tue, May 31, 2016 at 03:09:13PM +0200, Gerd Hoffmann wrote:
> On Di, 2016-05-31 at 15:36 +0300, Ville Syrjälä wrote:
>
> > Why store it in the fb and not eg. the plane state?
>
> Well, drm_plane_state is allocated by drm_atomic_helper_update_plane.
>
> When sticking the hotspot into the the
Op 30-05-16 om 10:01 schreef Daniel Vetter:
> Design ideas:
>
> - split up the actual commit into different phases, and have
> completions for each of them. This will be useful for the future
> when we want to interleave phases much more aggressively, for e.g.
> queue depth > 1. For not it's
From: Gustavo Padovan
Add Gustavo as maintainer for the Sync File Framework. Sumit is
co-maintainer as he maintains drivers/dma-buf/. It also uses Sumit's
tree as base.
Signed-off-by: Gustavo Padovan
Acked-by: Sumit Semwal
Acked-by: Maarten Lankhorst
---
MAINTAINERS | 11 +++
1 file
From: Gustavo Padovan
We've got a complaint saying that the description was quite obtuse and
indeed it was. This patch tries to improve it.
Cc: Dave Jones
Signed-off-by: Gustavo Padovan
---
drivers/dma-buf/Kconfig | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --
On Tue, May 31, 2016 at 04:22:57PM +0200, Maarten Lankhorst wrote:
> Op 30-05-16 om 10:01 schreef Daniel Vetter:
> > Design ideas:
> >
> > - split up the actual commit into different phases, and have
> > completions for each of them. This will be useful for the future
> > when we want to interl
On Tue, May 31, 2016 at 09:39:19PM +0800, Yakir Yang wrote:
> EDP PSR function is interesting in vblank enable or disable event,
> so it would be great introduce a way to notify encoder about this
> event.
>
> Signed-off-by: Yakir Yang
notifiers considered evil, especially if you add a global no
On Tue, May 31, 2016 at 09:37:36PM +0800, Yakir Yang wrote:
> The full name of PSR is Panel Self Refresh, panel device could refresh
> itself with the hardware framebuffer in panel, this would make a lots
> of sense to save the power consumption.
>
> For example, when desktop haven't change the co
Dispatch DRM pending events from crtc_atomic_flush() and not from
the IRQ handler.
Don't disable the vsync interrupt, as the hardware lacks hardware
counters for vsync time stamping.
Signed-off-by: Liviu Dudau
---
This replaces the previous patch "drm: hdlcd: Replace the mode config's
atomic_c
ail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/ea213ff5/attachment-0001.html>
From: Ville Syrjälä
Here's a repost of my PSR fixes, and one straggler from Daniel.
One interesting thing I noticed is that my SKL actually hits the PSR setup
time vs. vblank length check, so after these patches that machine won't
actually use PSR. The panel does support a lower refresh rate t
From: Ville Syrjälä
Add a small helper to parse the PSR setup time from the DPCD PSR
capabilities and return the value in microseconds.
v2: Don't waste so many bytes on the psr_setup_time_us[] table
Cc: Daniel Vetter
Reviewed-by: Daniel Vetter
Signed-off-by: Ville Syrjälä
---
drivers/gp
From: Ville Syrjälä
Add a small helper to parse from the DPCD whether link training
is required when exiting PSR main-link off mode.
v2: Rebased
Cc: Daniel Vetter
Reviewed-by: Daniel Vetter
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/drm_dp_helper.c | 14 ++
include/drm
From: Ville Syrjälä
Bspec says:
"Restriction : SRD must not be enabled when the PSR Setup time from DPCD
00071h is greater than the time for vertical blank minus one line."
Let's check for that and disallow PSR if we exceed the limit.
Cc: Daniel Vetter
Reviewed-by: Daniel Vetter
Signed-off-
From: Daniel Vetter
Not sure we can trust VBT on this one, but let's try.
Cc: Rodrigo Vivi
Cc: Sonika Jindal
Cc: Durgadoss R
Signed-off-by: Daniel Vetter
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_psr.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm
From: Ville Syrjälä
The sink can tell us if link training needs to be performed when
exiting PSR main-link off mode. Currently we get that information
from the VBT, but at least on my HSW the VBT says one thing, the sink
another. And in practice the sink doesn't seem to notice any screen
update
From: Ville Syrjälä
Determine the value of psr.link_standby at runtime rather than at init
time. This helps in testing since you can change between link-off and
link-standby at runtime.
Reviewed-by: Daniel Vetter
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_psr.c | 41 +
scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/943c9c1a/attachment-0001.html>
HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/91ce6f0c/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/19e4e1a8/attachment.html>
commit 255f0e7c418ad95a4baeda017ae6182ba9b3c423 upstream.
During boot, MST hotplugs are generally expected (even if no physical
hotplugging occurs) and result in DRM's connector topology changing.
This means that using num_connector from the current mode configuration
can lead to the number of con
Unfortunately since we don't have Dave's connector refcounting patch
here yet, it's very possible that drm_atomic_state_default_clear() could
get called by intel_display_resume() when
intel_dp_mst_destroy_connector() isn't completely finished destroying an
mst connector, but has already finished se
On Mon, May 30, 2016 at 01:54:06PM +0200, Krzysztof Kozlowski wrote:
> The dma-mapping core and the implementations do not change the
> DMA attributes passed by pointer. Thus the pointer can point to const
> data. However the attributes do not have to be a bitfield. Instead
> unsigned long will d
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/9d569ec0/attachment.sig>
On Tue, May 31, 2016 at 8:15 PM, Luis R. Rodriguez wrote:
> On Sun, May 29, 2016 at 05:49:17PM +0300, Oded Gabbay wrote:
>> On Fri, May 27, 2016 at 4:18 AM, Luis R. Rodriguez
>> wrote:
>> > diff --git a/drivers/gpu/drm/radeon/radeon_drv.c
>> > b/drivers/gpu/drm/radeon/radeon_drv.c
>> > index b5
On Mon, May 30, 2016 at 01:54:06PM +0200, Krzysztof Kozlowski wrote:
> The dma-mapping core and the implementations do not change the
> DMA attributes passed by pointer. Thus the pointer can point to const
> data. However the attributes do not have to be a bitfield. Instead
> unsigned long will d
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160531/a6bb9a80/attachment.html>
org/archives/dri-devel/attachments/20160531/54493392/attachment.html>
On Tue, May 31, 2016 at 06:58:34PM +0200, Luis R. Rodriguez wrote:
> On Sun, May 29, 2016 at 08:27:07PM +0200, Daniel Vetter wrote:
> > On Fri, May 27, 2016 at 3:18 AM, Luis R. Rodriguez
> > wrote:
> > > To get KFD support in radeon we need the following
> > > initialization to happen in this ord
On Tue, May 31, 2016 at 06:50:24PM +0300, ville.syrjala at linux.intel.com
wrote:
> From: Ville Syrjälä
>
> Here's a repost of my PSR fixes, and one straggler from Daniel.
>
> One interesting thing I noticed is that my SKL actually hits the PSR setup
> time vs. vblank length check, so after t
On Tue, May 31, 2016 at 10:23:32AM -0700, Eric Anholt wrote:
> Daniel Vetter writes:
>
> > No dev->struct_mutex anywhere to be seen.
>
> The vc4 patches are:
>
> Reviewed-by: Eric Anholt
Thanks for the review, both applied to drm-misc.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corpor
On Tue, May 31, 2016 at 09:07:49PM +0200, Daniel Vetter wrote:
> On Tue, May 31, 2016 at 06:50:24PM +0300, ville.syrjala at linux.intel.com
> wrote:
> > From: Ville Syrjälä
> >
> > Here's a repost of my PSR fixes, and one straggler from Daniel.
> >
> > One interesting thing I noticed is that
From: Gustavo Padovan
Hi,
The following patches do a clean up on the sw_sync inteface. It starts by
removing struct sync_timeline_ops, which was creating unecessary wrappers
in the code and the start to organize the sync_timeline and sw_sync code
better.
sw_sync interface was moved to sw_sync.c
From: Gustavo Padovan
Now fence timeline is aware of the last signaled fence, as it
receives the increment to the current value in sync_timeline_signal().
That allow us to remove .has_signaled() from timeline_ops as we can
directly compare using timeline->value and fence->seqno in sync.c
Signed
From: Gustavo Padovan
Now that the value of fence and the timeline are not stored by sw_sync
anymore we can remove this extra abstraction to retrieve this data.
This patch changes both fence_ops (.fence_value_str and
.timeline_value_str) to return the str directly.
It also clean up struct sync_
From: Gustavo Padovan
As we moved value storage to sync_timeline and fence those two structs
became useless and can be removed now.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c| 24 +++-
drivers/staging/android/sw_sync.h| 24 ++---
From: Gustavo Padovan
Move drv_name, the last field of sync_timeline_ops, to sync_timeline
and remove sync_timeline_ops.
struct sync_timeline_ops was just an extra abstraction on top of
fence_ops, and in the last few commits we removed all it ops in favor
of cleaner fence_ops.
Signed-off-by: Gu
From: Gustavo Padovan
We can glue the sw_sync file operations directly on the sync framework
without the need to pass through sw_sync wrappers.
It only builds sw_sync debugfs file support if CONFIG_SW_SYNC is enabled.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Makefile |
From: Gustavo Padovan
We are moving out of staging/android so rename it to a name that is not
related to android anymore.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a
From: Gustavo Padovan
When we call sync_print_fence() fence is always valid.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync_debug.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/android/sync_debug.c
b/drivers/staging/android/sync_deb
From: Gustavo Padovan
After we removed sw_sync_timeline this arg has not been really used by
anyone, all its users pass the size of struct sync_timeline there.
So simplify this function but not requiring the size anymore.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c
From: Gustavo Padovan
Move the list_head members from sync_pt to struct fence was a mistake,
they will not be used by struct fence as planned before, so here we create
sync_pt again to bring the list heads back.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 40 +
Hello Yakir,
On 05/27/2016 02:16 AM, Yakir Yang wrote:
> Hi Javier,
>
> On 05/26/2016 08:48 PM, Javier Martinez Canillas wrote:
>> Hello Yakir,
>>
>> On 05/26/2016 05:34 AM, Yakir Yang wrote:
>>> Hi Javier,
>>>
>>> On 05/24/2016 01:01 PM, Yakir Yang wrote:
Hi all,
This series have
From: Gustavo Padovan
'destroyed' was set but not used ny anyone.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c | 5 -
drivers/staging/android/sync.h| 5 +
2 files changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/staging/android/sw_sync.c
b/driv
From: Gustavo Padovan
Most of the includes there are not necessary anymore.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 6 --
drivers/staging/android/sync.h | 3 ---
drivers/staging/android/sync_debug.c | 16
3 files changed, 25 deleti
From: Gustavo Padovan
SW_SYNC only works with DEBUG_FS so state it in the Kconfig file.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Kconfig | 1 +
drivers/staging/android/sync_debug.c | 4
drivers/staging/android/sync_debug.h | 4 +---
3 files changed, 2 insertions(+),
From: Gustavo Padovan
Split sync_debug and sw_sync in two different files.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Makefile | 1 +
drivers/staging/android/sw_sync.c| 136 +++
drivers/staging/android/sync.h | 2 +
drivers/stag
From: Gustavo Padovan
The only use sync_timeline will have in upstream kernel is for debugging
through the SW_SYNC interface. So make it internal to SW_SYNC to avoid
people use it in the future.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Kconfig | 16 +--
drivers/staging/
From: Gustavo Padovan
We don't want to export this from the kernel. This is interface is only
for testing and debug. So testers shall copy the ioctl info in their own
projects.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c | 13 -
drivers/staging/android
From: Gustavo Padovan
This function was just used by the file release function, so we just fold
its content there and remove sync_timeline_destroy().
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c | 19 +++
1 file changed, 3 insertions(+), 16 deletions(-)
From: Gustavo Padovan
This header file only contains information for debugging and SW_SYNC, so
rename it to sync_debug.h instead of having a more generic name.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c| 2 +-
drivers/staging/android/sync_debug.c
From: Gustavo Padovan
As it is internal to sw_sync now this value will always be "sw_sync".
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c| 11 +++
drivers/staging/android/sync.h | 2 --
drivers/staging/android/sync_debug.c | 2 +-
3 files changed, 4 i
e the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/0e310200/attachment.html>
Apparently not everyone has been super dutiful with updating this
stuff.
I still decided to leave out the documentation for all the *_property
pointers we have in drm_mode_config.
Signed-off-by: Daniel Vetter
---
include/drm/drm_crtc.h | 80 ++
1
kernel-doc is unhappy, appease it.
Cc: Lionel Landwerlin
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/drm_atomic_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_atomic_helper.c
b/drivers/gpu/drm/drm_atomic_helper.c
index 290318d6f5b5..68627b
kernel-doc was unhappy, appease it.
Cc: Noralf Trønnes
Cc: laurent.pinchart at ideasonboard.com
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/drm_fb_cma_helper.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/drm_fb_cma_helper.c
b/dr
We need to get folks to run
$ make htmldocs
more often and actually check the output. With the fancy new sphinx
stuff there's hopefully no more excuses.
Fixes: 286dbb8d5d80 ("drm/atomic: Rename async parameter to nonblocking.")
Cc: Maarten Lankhorst
Signed-off-by: Daniel Vetter
---
Documentat
At least in drm core we only document the driver interfaces using
kerneldoc. For internals an unstructured comment is good enough.
Fixes a warning from kernel-doc, too.
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/drm_irq.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
1 - 100 of 175 matches
Mail list logo
