On 27 April 2016 at 22:57, Dave Airlie wrote:
> On 28 April 2016 at 07:45, Emil Velikov wrote:
>> On 27 April 2016 at 10:47, Russell King - ARM Linux
>> wrote:
>>> On Thu, Apr 21, 2016 at 09:17:13PM +0100, Emil Velikov wrote:
Dave Airlie pointed out that "polluting" the headers in a manner
Dear all,
I have noticed several warnings in dmesg like below. I wonder if I can
provide more information. I have looked into the sources
https://kernel.googlesource.com/pub/scm/linux/kernel/git/stable/linux-stable/+/v4.4.6/drivers/gpu/drm/i915/intel_display.c#12157
https://kernel.googlesource.co
Hi Ville,
On Wednesday 27 Apr 2016 20:29:24 Ville Syrjälä wrote:
> On Wed, Apr 27, 2016 at 06:30:19PM +0300, Laurent Pinchart wrote:
> > Hi Tomi,
> >
> > (CC'ing Daniel)
> >
> > Thank you for the patch.
> >
> > On Tuesday 26 Apr 2016 13:16:42 Tomi Valkeinen wrote:
> > > At the moment we don't
On 27 April 2016 at 10:47, Russell King - ARM Linux
wrote:
> On Thu, Apr 21, 2016 at 09:17:13PM +0100, Emil Velikov wrote:
>> Dave Airlie pointed out that "polluting" the headers in a manner as seen
>> with this series might not be too wise. David H, can we hear your view
>> on the topic ?
>
> For
From: Ville Syrjälä
Let's be nice and interrupt the dpcd aux-dev reads/writes when there's
a signal pending. Much nicer if the user can hit ^C instead of having to
sit around waiting for the read/write to finish.
time dd if=/dev/drm_dp_aux0 bs=$((1024*1024))
^C
before:
real 0m34.681s
user
On 27 April 2016 at 00:37, Dave Airlie wrote:
> On 22 April 2016 at 18:37, Daniel Vetter wrote:
>> On Thu, Apr 21, 2016 at 09:17:32PM +0100, Emil Velikov wrote:
>>> Signed-off-by: Emil Velikov
>>
>> If the extern C stuff falls through, maybe we want to pull this one out
>> ahead?
>
> I've pulled
On 27 April 2016 at 07:43, Dave Airlie wrote:
> On 19 April 2016 at 19:03, Xinliang Liu wrote:
>> Hi Dave,
>>
>> This is the first pull request from drm-hisilicon and for 4.7.
>>
>> The patches add new hisilicon drm driver.
>>
>> The patches were reviewed here:
>> http://www.spinics.net/lists/dri
Den 27.04.2016 21:24, skrev Daniel Vetter:
> On Wed, Apr 27, 2016 at 08:16:29PM +0200, Noralf Trønnes wrote:
>> This patchset adds fbdev deferred io support to drm_fb_helper and
>> drm_fb_cma_helper.
>>
>> It channels fbdev mmap and fb_{write,fillrect,copyarea,imageblit} damage
>> through the (st
On Mon, Apr 25, 2016 at 03:19:22PM +0100, Liviu Dudau wrote:
> Add DT bindings documentation for the Mali Display Processor. The bindings
> describe the Mali DP500, DP550 and DP650 processors from ARM Ltd.
>
> Cc: Rob Herring
> Cc: Pawel Moll
> Cc: Mark Rutland
> Cc: Ian Campbell
> Cc: Kumar G
On Mon, Apr 25, 2016 at 03:22:45PM +0200, Maxime Ripard wrote:
> The display pipeline of the Allwinner A10 is involving several loosely
> coupled components.
>
> Add a documentation for the bindings.
>
> Signed-off-by: Maxime Ripard
> ---
> .../bindings/display/sunxi/sun4i-drm.txt | 2
On Wed, Apr 27, 2016 at 02:39:21PM +0200, Lucas Stach wrote:
> +static int etnaviv_gem_userptr_mmap_obj(struct etnaviv_gem_object
> *etnaviv_obj,
> + struct vm_area_struct *vma)
> +{
> + return -EPERM;
> +}
EPERM The prot argument asks for PROT_EXEC but the mapped area bel
Den 27.04.2016 21:20, skrev Daniel Vetter:
> On Wed, Apr 27, 2016 at 08:16:32PM +0200, Noralf Trønnes wrote:
>> This adds deferred io support to drm_fb_helper.
>> The fbdev framebuffer changes are flushed using the callback
>> (struct drm_framebuffer *)->funcs->dirty() by a dedicated worker
>> en
On Wed, Apr 27, 2016 at 08:16:29PM +0200, Noralf Trønnes wrote:
> This patchset adds fbdev deferred io support to drm_fb_helper and
> drm_fb_cma_helper.
>
> It channels fbdev mmap and fb_{write,fillrect,copyarea,imageblit} damage
> through the (struct drm_framebuffer_funcs)->dirty callback on the
On Wed, Apr 27, 2016 at 08:16:35PM +0200, Noralf Trønnes wrote:
> Use the fbdev deferred io support in drm_fb_helper which mirrors the
> one qxl has had.
> This patch has only been compile tested.
>
> Signed-off-by: Noralf Trønnes
> ---
>
> Changes since v2:
> - The drm_clip_rect_{width/height
On Wed, Apr 27, 2016 at 08:16:32PM +0200, Noralf Trønnes wrote:
> This adds deferred io support to drm_fb_helper.
> The fbdev framebuffer changes are flushed using the callback
> (struct drm_framebuffer *)->funcs->dirty() by a dedicated worker
> ensuring that it always runs in process context.
>
On Wed, Apr 27, 2016 at 01:27:07PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Hi,
>
> This patchset sits on top of Sync ABI Rework v13:
>
> https://www.spinics.net/lists/dri-devel/msg105667.html
>
> The first eight clean up and prepare sync_file for de-staging. The last four
> p
On Wed, Apr 27, 2016 at 01:27:19PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Add sync_file documentation on dma-buf-sync_file.txt
> ---
> Documentation/dma-buf-sync_file.txt | 65
> +
> 1 file changed, 65 insertions(+)
> create mode 100644 Do
On Wed, 27 Apr 2016 20:36:13 +0300 Mihai DonÈu wrote:
> On Wed, 27 Apr 2016 08:28:20 -0700 Rodrigo Vivi wrote:
> > Hi Mihai,
> >
> > What platform do you have? HSW or BDW?
>
> I have an i7, Haswell CPU.
>
> > If you don't know please provide lspci -nn
>
> I have attached the output of lspc
DonÈu
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: lspci.txt
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/e594bf28/attachment.txt>
On Wed, Apr 27, 2016 at 06:30:19PM +0300, Laurent Pinchart wrote:
> Hi Tomi,
>
> (CC'ing Daniel)
>
> Thank you for the patch.
>
> On Tuesday 26 Apr 2016 13:16:42 Tomi Valkeinen wrote:
> > At the moment we don't check the plane input/output sizes, which can
> > lead to DSS HW errors when invalid
Use the fbdev deferred io support in drm_fb_helper.
The (struct fb_ops *)->fb_{fillrect,copyarea,imageblit} functions will
now schedule a worker instead of being flushed directly like it was
previously (recorded when in atomic).
This patch has only been compile tested.
Signed-off-by: Noralf Trøn
Use the fbdev deferred io support in drm_fb_helper which mirrors the
one qxl has had.
This patch has only been compile tested.
Signed-off-by: Noralf Trønnes
---
Changes since v2:
- The drm_clip_rect_{width/height} functions are dropped, so open code it
Changes since v1:
- Add FIXME about speci
This adds fbdev deferred io support if CONFIG_FB_DEFERRED_IO is enabled.
The driver has to provide a (struct drm_framebuffer_funcs *)->dirty()
callback to get notification of fbdev framebuffer changes.
If the dirty() hook is set, then fb_deferred_io is set up automatically
by the helper.
Two funct
Export fb_deferred_io_mmap so drivers can change vma->vm_page_prot.
When the framebuffer memory is allocated using dma_alloc_writecombine()
instead of vmalloc(), I get cache syncing problems on ARM.
This solves it:
static int drm_fbdev_cma_deferred_io_mmap(struct fb_info *info,
This adds deferred io support to drm_fb_helper.
The fbdev framebuffer changes are flushed using the callback
(struct drm_framebuffer *)->funcs->dirty() by a dedicated worker
ensuring that it always runs in process context.
Signed-off-by: Noralf Trønnes
---
Changes since v2:
- FB_DEFERRED_IO is
Now that drm_fb_helper gets deferred io support, the
drm_fb_helper_sys_{fillrect,copyarea,imageblit} functions will schedule
a worker that will call the (struct drm_framebuffer *)->funcs->dirty()
function. This will break this driver so use the
sys_{fillrect,copyarea,imageblit} functions directly.
Now that drm_fb_helper gets deferred io support, the
drm_fb_helper_sys_{fillrect,copyarea,imageblit} functions will schedule
a worker that will call the (struct drm_framebuffer *)->funcs->dirty()
function. This will break this driver so use the
sys_{fillrect,copyarea,imageblit} functions directly.
This patchset adds fbdev deferred io support to drm_fb_helper and
drm_fb_cma_helper.
It channels fbdev mmap and fb_{write,fillrect,copyarea,imageblit} damage
through the (struct drm_framebuffer_funcs)->dirty callback on the
fb_helper framebuffer which will always run in process context.
I have al
On 27/04/16 17:05, Philipp Zabel wrote:
> To allow building mediatek-drm.ko as a module, the
> mtk_smi_larb_get and mtk_smi_larb_put symbols have
> to be exported.
>
> Signed-off-by: Philipp Zabel
Signed-off-by: Matthias Brugger
> ---
> drivers/memory/mtk-smi.c | 2 ++
> 1 file changed, 2
When tracking down a customer issue, it is useful to know exactly
which version of the vmwgfx they are using. Since vmware.log is
often the only available debug log, report vmwgfx version in there.
Signed-off-by: Sinclair Yeh
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/.gitignore
This patch adds capabilities for a VMWare guest to send and
receive messages from the host, and adds functions to sending log
messages to vmware.log and to request device settings that aren't
available through the virtual hardware, e.g. certain settings in
the VMX file.
Signed-off-by: Sinclair Yeh
https://bugzilla.kernel.org/show_bug.cgi?id=86351
haakobja at gmail.com changed:
What|Removed |Added
CC||haakobja at gmail.com
--- Comment
Hi Maarten,
Thank you for the patch.
On Tuesday 26 Apr 2016 16:11:40 Maarten Lankhorst wrote:
> The async name is deprecated and should be changed to nonblocking.
>
> Cc: Laurent Pinchart
> Signed-off-by: Maarten Lankhorst
Acked-by: Laurent Pinchart
> ---
> drivers/gpu/drm/rcar-du/rcar_du_
Hi Tomi,
(CC'ing Daniel)
Thank you for the patch.
On Tuesday 26 Apr 2016 13:16:42 Tomi Valkeinen wrote:
> At the moment we don't check the plane input/output sizes, which can
> lead to DSS HW errors when invalid values are given from the userspace.
>
> Add a check so that the sizes are > 0.
>
vel/attachments/20160427/6d62ecf1/attachment.sig>
the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/d89f60c4/attachment-0001.html>
or the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/8860601c/attachment-0001.html>
racks. Roland just mentioned this on
IRC...I've reviewed and pushed the patch to master. I'm also making a
release.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digital
Allocation of a frame buffer memory in a special memory region
allows bypassing of so-called IO Coherency aperture
which is typically set as a range 0x8z-0xAz.
I.e. all data traffic to PGU bypasses IO Coherency block
and saves its bandwidth for other peripherals.
Even though for AXS101 (which sor
Now when ARC supports reserved memory areas and
per-device coherent DMA allocations we may switch ARC PGU
to use of those dedicated areas.
One of the benefits we may move frame-buffer area out
from IO Coherency aperture and so significantly
reduce IOC utilization allowing less demanding
peripheral
This mini-series allows to allocate frame buffer memory in desired
location. Allocation of a frame buffer memory in a special memory region
allows bypassing of so-called IO Coherency aperture which is typically set
as a range 0x8z-0xAz.
I.e. all data traffic to PGU bypasses IO Coherency block
and
LGTM
Reviewed-by: Thomas Hellstrom
On 04/26/2016 06:50 AM, Alex Deucher wrote:
> Ping. Any objections?
>
>
> On Wed, Apr 20, 2016 at 1:52 PM, Alex Deucher
> wrote:
>> From: Flora Cui
>>
>> Fixes the following scenario:
>>
>> 1. Page table bo allocated in vram and linked to man->lru.
>>t
2016-04-21 14:51 GMT+02:00 Lucas Stach :
> On cores with MC1.0 the memory window offset is not properly respected
> by all engines in the core, leading to different views of the memory
> if the offset in non-zero. This causes relocs for those engines to be
> wrong and might lead to other subtile pr
Am Mittwoch, den 27.04.2016, 08:59 +1000 schrieb Dave Airlie:
> > I reverted the 4 patches in that series
> >
> > 407c9eba drm/imx: Remove of_node assignment from ipuv3-crtc driver probe
> > 304e6be6 gpu: ipu-v3: Assign of_node of child platform devices to
> > corresponding ports
> > 99ae78c3 gpu:
2016-04-21 22:17 GMT+02:00 Emil Velikov :
> Cc: Christian Gmeiner
> Cc: Russell King
> Cc: Lucas Stach
> Signed-off-by: Emil Velikov
Acked-by: Christian Gmeiner
> ---
> include/uapi/drm/etnaviv_drm.h | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/include/uapi/drm/etnaviv_d
>> Hm, I thought the referenced commit explained this, but now that I recheck
>> it doesn't. I'm not too sure again myself why I thought nouveau needs
>> this. The legacy ctx stuff is required because of some old kms nouveau ddx
>> that still used that stuff. I thought it also used legacy maps ...
To allow building mediatek-drm.ko as a module, the
mtk_smi_larb_get and mtk_smi_larb_put symbols have
to be exported.
Signed-off-by: Philipp Zabel
---
drivers/memory/mtk-smi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/memory/mtk-smi.c b/drivers/memory/mtk-smi.c
index 089091f.
The hdmitx_dig_cts clock signal is not a child of tvdpll_445p5m,
but is routed out of the HDMI PHY module.
Signed-off-by: Philipp Zabel
Acked-by: Stephen Boyd
---
drivers/clk/mediatek/clk-mt8173.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/clk/mediatek/clk-mt8173.c
b/drivers/cl
The configurable hdmi_ref output of the PLL block is derived from
the tvdpll_594m clock signal via a configurable PLL post-divider.
It is used as the PLL reference input to the HDMI PHY module.
Signed-off-by: Philipp Zabel
Acked-by: James Liao
Acked-by: Stephen Boyd
---
drivers/clk/mediatek/cl
This mux is supposed to select a fitting divider after the PLL
is already set to the correct rate.
Signed-off-by: Philipp Zabel
Acked-by: James Liao
Acked-by: Stephen Boyd
---
drivers/clk/mediatek/clk-mt8173.c | 6 +-
drivers/clk/mediatek/clk-mtk.h| 15 +--
2 files changed
From: Jie Qiu
Add DPI connector/encoder to support HDMI output via the
attached HDMI bridge.
Signed-off-by: Jie Qiu
Signed-off-by: Philipp Zabel
---
drivers/gpu/drm/mediatek/Makefile | 3 +-
drivers/gpu/drm/mediatek/mtk_dpi.c | 769
drivers/gpu/dr
From: CK Hu
This patch add a drm encoder/connector driver for the MIPI DSI function
block of the Mediatek display subsystem and a phy driver for the MIPI TX
D-PHY control module.
Signed-off-by: Jitao Shi
Signed-off-by: Philipp Zabel
---
Changes since v15:
- use div_u64 to avoid "__aeabi_uldiv
From: CK Hu
This patch adds an initial DRM driver for the Mediatek MT8173 DISP
subsystem. It currently supports two fixed output streams from the
OVL0/OVL1 sources to the DSI0/DPI0 sinks, respectively.
Signed-off-by: CK Hu
Signed-off-by: YT Shen
Signed-off-by: Daniel Kurtz
Signed-off-by: Bibb
From: CK Hu
Add device tree binding documentation for the display subsystem in
Mediatek MT8173 SoCs.
Signed-off-by: CK Hu
Signed-off-by: Philipp Zabel
Acked-by: Rob Herring
---
.../bindings/display/mediatek/mediatek,disp.txt| 203 +
.../bindings/display/mediatek/media
Rebased onto drm-next, fixed building as a module, removed the
driver unload hook, custom vm_ops, and the dts patch.
Changes since v14:
- Fixed module build
- Select DRM_GEM_CMA_HELPER and use drm_gem_cma_vm_ops
- Select MEMORY so that select MTK_SMI works properly
- Rebase onto drm-next so we
me is loading at the end of the qualifications.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/50f682c6/attachment-0001.html>
1315b) / Debian Sid.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/92d019ff/attachment.html>
Here, a location is reset to NULL before being passed to PTR_ERR.
So, PTR_ERR should be called before its argument is reassigned
to NULL. Further to simplify things use PTR_ERR_OR_ZERO instead
of PTR_ERR and IS_ERR.
Problem found using Coccinelle.
Signed-off-by: Vaishali Thakkar
---
drivers/gpu
We have allowed migration for only LRU pages until now and it was
enough to make high-order pages. But recently, embedded system(e.g.,
webOS, android) uses lots of non-movable pages(e.g., zram, GPU memory)
so we have seen several reports about troubles of small high-order
allocation. For fixing the
Recently, I got many reports about perfermance degradation in embedded
system(Android mobile phone, webOS TV and so on) and easy fork fail.
The problem was fragmentation caused by zram and GPU driver mainly.
With memory pressure, their pages were spread out all of pageblock and
it cannot be migrat
On Wed, 27 Apr 2016, Florian Zumbiehl wrote:
>> Florian, if you're using drm-intel-nigthly submit a bug at
>> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI, with DRM/intel
>> as component. This way we can track some kind of progress/regress. The FIFO
>
> Gee ... is there any way without "
Document the ddc-i2c-bus property used by imx-ldb driver to read EDID
information via I2C interface.
Signed-off-by: Akshay Bhat
---
v3:
Newly added.
Documentation/devicetree/bindings/display/imx/ldb.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/displ
From: Steve Longerbeam
Add support for reading EDID over Display Data Channel. If no DDC
adapter is available, falls back to hardcoded EDID or display-timings
node as before.
Signed-off-by: Steve Longerbeam
Signed-off-by: Akshay Bhat
Acked-by: Philipp Zabel
---
Hi Philipp,
I have addressed
scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/8cf7fd6b/attachment.html>
Am Mittwoch, den 27.04.2016, 08:54 -0500 schrieb Dennis Gilmore:
> Thanks Philipp,
>
> I tested and module loading worked correctly
>
> Dennis
>
> On 2016-04-27 03:29, Philipp Zabel wrote:
> > If of_node is set before calling platform_device_add, the driver core
> > will try to use of: modalias
On Wed, 27 Apr 2016, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Purpose is to enable drivers to print out just the mode
> string with their own formatting.
Some alternatives that preserve the use of a single printk(), avoiding
garbled console output due to races (as discussed on intel-gfx
lt;https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/b4bd19d1/attachment.html>
Hi,
> Florian, if you're using drm-intel-nigthly submit a bug at
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI, with DRM/intel
> as component. This way we can track some kind of progress/regress. The FIFO
Gee ... is there any way without "creating an account"? Having to create
accounts
Add an indirect object operations call to allow distinct implementations
of the mmap operation based on the type of the object.
This ensures that the exporter is called to set up the mmap for imported
dma-bufs and disallows mapping of userptr objects through the DRM file,
as this might lead to ser
This function will be changed to be called indirectly and this
prototype change brings it in line with all the other indirect
object calls.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/etnaviv_gem.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/gp
If the MMU map fails caused by an unaligned SG entry, the unmap path
is called to undo all already setup SG mappings. When encountering the
unaligned SG the unmap path hangs the kernel with a BUG(), while the
error is recoverable by just failing the submit that references the
faulty object.
Signed
On Wed, Apr 27, 2016 at 12:58:51PM +0100, Chris Wilson wrote:
> On Wed, Apr 27, 2016 at 01:50:00PM +0200, Daniel Vetter wrote:
> > Finally all the core gem and a lot of drivers are entirely free of
> > dev->struct_mutex depencies, and we can start to have an entirely
> > lockless unref path.
> >
>
Am Mittwoch, den 27.04.2016, 13:21 +0200 schrieb Daniel Vetter:
> On Wed, Apr 27, 2016 at 12:29:34PM +0200, Philipp Zabel wrote:
> > Am Dienstag, den 26.04.2016, 19:29 +0200 schrieb Daniel Vetter:
> > > No dev->struct_mutex anywhere to be seen.
> > >
> > > Cc: Sascha Hauer
> > > Cc: Philipp Zabel
Hi Dave,
A few fixes for 4.6.
- revert amdgpu PX commit that was previously reverted on the radeon side
- cleaned up version of the NI+ MC update display fix for radeon
- TTM kref fix
The following changes since commit 18cdfe751f26ffa610f2a7b59775c5cc4c1c9619:
Merge branch 'drm-fixes-4.6' of g
On 27/04/16 13:35, Jani Nikula wrote:
> On Wed, 27 Apr 2016, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin
>>
>> Purpose is to enable drivers to print out just the mode
>> string with their own formatting.
>
> Some alternatives that preserve the use of a single printk(), avoiding
> garbled conso
Finally all the core gem and a lot of drivers are entirely free of
dev->struct_mutex depencies, and we can start to have an entirely
lockless unref path.
To make sure that no one who touches the core code accidentally breaks
existing drivers which still require dev->struct_mutex I've made the
migh
It's an optional hook.
Cc: Rob Clark
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/msm/msm_fb.c | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/gpu/drm/msm/msm_fb.c b/drivers/gpu/drm/msm/msm_fb.c
index 17e0c9eb1900..672d8b1c2d09 100644
--- a/drivers/gpu/drm/msm/msm_fb.c
++
It's an optional hook. Might be needed for frontbuffer rendering on
manual upload displays, but a simple TODO doesn't explain at all what
needs to be done or why.
Cc: Inki Dae
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/exynos/exynos_drm_fb.c | 11 ---
1 file changed, 11 deletions(
No need to reinvent this little wheel.
v2: Like, try to make it compile even.
Cc: Mark Yao
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
b/dri
On Wed, 27 Apr 2016, Mihai DonÈu wrote:
> On Wed, 27 Apr 2016 10:09:32 +0300 Jani Nikula wrote:
>> On Wed, 27 Apr 2016, Mihai DonÈu wrote:
>> > I noticed that since I started using 4.6.0-rcX, my screen flickers once
>> > or twice after I stop using my laptop for ~1min or so. Given the
>> > behav
For MST encoders, the encoder struct is stored in the intel_dp_mst
struct, not a intel_digital_port struct.
This fixes issues with hotplugging MST displays that support MST audio,
where hotplugging had a surprisingly good chance of accidentally
overwriting other parts of the kernel leading to seem
From: Gustavo Padovan
Add sync_file documentation on dma-buf-sync_file.txt
---
Documentation/dma-buf-sync_file.txt | 65 +
1 file changed, 65 insertions(+)
create mode 100644 Documentation/dma-buf-sync_file.txt
diff --git a/Documentation/dma-buf-sync_file.tx
From: Gustavo Padovan
Add entry in device-drivers.tmpl for sync_file documentation.
Signed-off-by: Gustavo Padovan
---
Documentation/DocBook/device-drivers.tmpl | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/DocBook/device-drivers.tmpl
b/Documentation/DocBook/device-drive
From: Gustavo Padovan
sync_file is useful to connect one or more fences to the file. The file is
used by userspace to track fences between drivers that share DMA bufs.
Signed-off-by: Gustavo Padovan
---
drivers/Kconfig | 2 ++
drivers/dma-buf/Kconfig
From: Gustavo Padovan
Move sync_file headers file to include/ dir.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.h | 4 ++--
drivers/staging/android/sync_debug.c | 2 +-
drivers/staging/android/sync_file.c
From: Gustavo Padovan
Fix checks reported by checkpatch.pl.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync_file.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/android/sync_file.c
b/drivers/staging/android/sync_file.c
index 5d77c0
From: Gustavo Padovan
num_fences was missing a colon mark and sync_file_create() now have
better description.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync_file.c | 3 ++-
drivers/staging/android/sync_file.h | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git
From: Gustavo Padovan
Move its functions and structs to their own file. Also moves function's
docs to the .c file.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Makefile | 2 +-
drivers/staging/android/sync.c | 373 ---
drive
From: Gustavo Padovan
There is no plan in the near future to use this function outside of this
file so keep it as static.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 3 +--
drivers/staging/android/sync.h | 1 -
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git
From: Gustavo Padovan
There is no plan in the near future to use this function outside of this
file so keep it as static.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 4 ++--
drivers/staging/android/sync.h | 2 --
2 files changed, 2 insertions(+), 4 deletions(-)
diff --
From: Gustavo Padovan
To keep comments in line with drivers/dma-buf/ move all sync_file comments
to sync.c.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 26 +-
drivers/staging/android/sync.h | 31 ---
2 files changed, 2
From: Gustavo Padovan
These two functions are just wrappers for one line functions, they
call fd_install() and fput() respectively, so just get rid of them
and use fd_install() and fput() directly for more simplicity.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 20
From: Gustavo Padovan
struct sync_merge_data already have documentation on top of the
struct definition. No need to duplicate it.
Signed-off-by: Gustavo Padovan
Reviewed-by: Maarten Lankhorst
---
drivers/staging/android/uapi/sync.h | 10 +-
1 file changed, 5 insertions(+), 5 deletions
From: Gustavo Padovan
Hi,
This patchset sits on top of Sync ABI Rework v13:
https://www.spinics.net/lists/dri-devel/msg105667.html
The first eight clean up and prepare sync_file for de-staging. The last four
patches do the de-staging, moving files to drivers/dma-buf/ and include/linux/
plus ad
On Wed, Apr 27, 2016 at 12:29:34PM +0200, Philipp Zabel wrote:
> Am Dienstag, den 26.04.2016, 19:29 +0200 schrieb Daniel Vetter:
> > No dev->struct_mutex anywhere to be seen.
> >
> > Cc: Sascha Hauer
> > Cc: Philipp Zabel
> > Signed-off-by: Daniel Vetter
> > ---
> > drivers/gpu/drm/imx/imx-drm
On Wed, Apr 27, 2016 at 11:31:00AM +0200, Lucas Stach wrote:
> Am Dienstag, den 26.04.2016, 19:29 +0200 schrieb Daniel Vetter:
> > Finally all the core gem and a lot of drivers are entirely free of
> > dev->struct_mutex depencies, and we can start to have an entirely
> > lockless unref path.
> >
>
On Wed, 27 Apr 2016 16:48:13 +0900 Minchan Kim wrote:
> Recently, I got many reports about perfermance degradation in embedded
> system(Android mobile phone, webOS TV and so on) and easy fork fail.
>
> The problem was fragmentation caused by zram and GPU driver mainly.
> With memory pressure, th
On Wed, Apr 27, 2016 at 02:12:46PM +0200, Daniel Vetter wrote:
> On Wed, Apr 27, 2016 at 12:58:51PM +0100, Chris Wilson wrote:
> > On Wed, Apr 27, 2016 at 01:50:00PM +0200, Daniel Vetter wrote:
> > > Finally all the core gem and a lot of drivers are entirely free of
> > > dev->struct_mutex depencie
On Wed, Apr 27, 2016 at 11:45:31AM +0200, Noralf Trønnes wrote:
>
> Den 26.04.2016 19:19, skrev Daniel Vetter:
> >On Tue, Apr 26, 2016 at 06:24:54PM +0200, Noralf Trønnes wrote:
> >>Den 25.04.2016 11:09, skrev Daniel Vetter:
> >>>On Sun, Apr 24, 2016 at 10:48:58PM +0200, Noralf Trønnes wrote:
>
On Wed, 27 Apr 2016 10:09:32 +0300 Jani Nikula wrote:
> On Wed, 27 Apr 2016, Mihai DonÈu wrote:
> > I noticed that since I started using 4.6.0-rcX, my screen flickers once
> > or twice after I stop using my laptop for ~1min or so. Given the
> > behavior, my prime suspect is the PSR feature that yo
1 - 100 of 174 matches
Mail list logo
