Hi Linus,
This is an optional pull request, Alex was waiting for some alsa
bits and some amdgpu bits to land to enable audio support on some
AMD APUs. The number of chips using this is quite low, and it's
just enabling the audio block for those GPUs.
I'm happy enough it shouldn't cause any probl
On 3 February 2016 at 07:20, Alex Deucher wrote:
> On Mon, Jan 25, 2016 at 1:55 PM, Wentland, Harry
> wrote:
>> Hi Dave,
>>
>> I've been running with lockdep with these changes for over a week now. Just
>> ran another test with our daisy-chain displays and the 4k tiled display with
>> no deadl
On 3 February 2016 at 18:39, Robert Bragg wrote:
> index a5524cc..68ca26e 100644
> --- a/include/uapi/drm/i915_drm.h
> +++ b/include/uapi/drm/i915_drm.h
> @@ -1170,4 +1172,71 @@ struct drm_i915_gem_context_param {
> __u64 value;
> };
>
> +#define I915_PERF_FLAG_FD_CLOEXEC (1<<0)
>
On 03.02.2016 21:42, Marek Szyprowski wrote:
> Drivers should use %p for printing pointers instead of hardcoding them
> as hexadecimal integers. This patch fixes compilation warnings on 64bit
> architectures.
>
> Signed-off-by: Marek Szyprowski
> ---
> drivers/gpu/drm/exynos/exynos_drm_fimc.c
2016ë
02ì 04ì¼ 11:17ì Krzysztof Kozlowski ì´(ê°) ì´ ê¸:
> On 03.02.2016 21:42, Marek Szyprowski wrote:
>> Drivers should use %p for printing pointers instead of hardcoding them
>> as hexadecimal integers. This patch fixes compilation warnings on 64bit
>> architectures.
>>
>> Signed-off
On 04.02.2016 11:34, Inki Dae wrote:
>
>
> 2016ë
02ì 04ì¼ 11:17ì Krzysztof Kozlowski ì´(ê°) ì´ ê¸:
>> On 03.02.2016 21:42, Marek Szyprowski wrote:
>>> Drivers should use %p for printing pointers instead of hardcoding them
>>> as hexadecimal integers. This patch fixes compilation warnin
On 02/03/2016 07:55 PM, Luis Henriques wrote:
> This fixes the following build failure:
>
> drivers/gpu/drm/msm/dsi/pll/dsi_pll_28nm.o: In function
> `msm_dsi_pll_28nm_8960_init':
> dsi_pll_28nm.c:(.text+0x1198): multiple definition of
> `msm_dsi_pll_28nm_8960_init'
> drivers/gpu/drm/msm/dsi/pl
Hi Philipp:
On Wed, 2016-02-03 at 12:01 +0100, Philipp Zabel wrote:
> Hi Daniel,
>
> > > +static void mtk_output_dsi_disable(struct mtk_dsi *dsi)
> > > +{
> > > + if (!dsi->enabled)
> > > + return;
> > > +
> > > + if (dsi->panel) {
> > > + if (drm_panel_di
Hi Dave -
Intel fixes for 4.5.
BR,
Jani.
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://anongit.freedesktop.org/drm-intel tags/drm-intel-fixes-2016-02-04
for you to fetc
From: Darren Etheridge
The default behavior of consoles during power management operations is: On
entry to suspend a new console is allocated and switched to. On resume the
original console is restored.
However this isn't the observed behavior and the original console is not
restored. This commi
From: Darren Etheridge
Updating the tilcdc DRM driver code to calculate the LCD controller
pixel clock more accurately. Based on a suggested implementation by
Tomi Valkeinen.
The current code does not work correctly and produces wrong results
with many requested clock rates. It also oddly uses t
From: Darren Etheridge
On BeagleBone Black if no HDMI monitor is connected and suspend
is requested a kernel panic will result:
root at am335x-evm:~# echo mem > /sys/power/state
[ 65.548710] PM: Syncing filesystems ... done.
[ 65.631311] Freezing user space processes ... (elapsed 0.006 seconds)
From: Dave Gerlach
Update tilcdc driver to set the state of the pins to:
- "default on resume
- "sleep" on suspend
By optionally putting the pins into sleep state in the suspend callback
we can accomplish two things.
- minimize current leakage from pins and thus save power,
- prevent the IP from
From: Darren Etheridge
The LCD controller must be deactivated and all DMA transactions stopped
when the suspend power state is entered otherwise the PRCM causes the L3
bus to get stuck in transition state.
This commit forces the lcdc to be shut down and waits for all pending DMA
transactions to
From: Grygorii Strashko
Fix build error when !CONFIG_CPU_FREQ
drivers/gpu/drm/tilcdc/tilcdc_drv.c: In function 'tilcdc_load':
drivers/gpu/drm/tilcdc/tilcdc_drv.c:327:1: error: label 'fail_put_clk' defined
but not used [-Werror=unused-label]
fail_put_clk:
^
Signed-off-by: Grygorii Strashko
Si
From: Tomi Valkeinen
Cleanup runtime PM handling. Before the patch the usage of pm_runtime
calls was inconsistent and hard to follow. After the update the
pm_runtime calls are removed from set_scanout() and called around
major operations that access the HW. After the patch the DPMS code does
not
Allocate suspend/resume register storage based on the actual number
registers the driver is aware of. The static allocation for register
storage had falen behind badly.
Reported-by: Michael Bode
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 20 +++-
drivers
From: Tomi Valkeinen
Split reset to a separate function and use usleep_range(250, 1000)
instead of msleep(1) to to keep the reset bit on long enough.
Signed-off-by: Tomi Valkeinen
[Added description to the patch, changed mdelay(500) to usleep_range(250, 1000)]
Signed-off-by: Jyri Sarha
---
dr
From: Tomi Valkeinen
Remove broken error handling. The condition for handling the
LCDC_SYNC_LOST and LCDC_FIFO_UNDERFLOW could never be satisfied as the
LCDC_SYNC_LOST interrupt is not enabled. Also the requirement to have
both LCDC_SYNC_LOST and LCDC_FIFO_UNDERFLOW fired at once before
handling
From: Tomi Valkeinen
Cleanup irq handling. Clear the irq status unconditionally and
restructure the status bit conditions.
Signed-off-by: Tomi Valkeinen
[Added description to the patch]
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 9 +
1 file changed, 5 inserti
From: Tomi Valkeinen
Do not update the next frame buffer close to vertical blank. This is
to avoid situation when the frame changes between writing of
LCDC_DMA_FB_BASE_ADDR_0_REG and LCDC_DMA_FB_CEILING_ADDR_0_REG.
Signed-off-by: Tomi Valkeinen
[Added description to the patch]
Signed-off-by: Jy
Fix interrupt enable/disable code for version 2 tilcdc. In version 2
tilcdc there is a separate register for disabling interrupts. Writing
0 to enable registers bits does not have any effect. The interrupt
clear register works the same way, writing 1 to specific bit disables
the interrupt and writi
Removes the duplicate LCDC_INT_ENABLE_SET_REG-entry in registers array.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/tilcdc/tilcdc_drv.c
b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
index 8ae19e3
Add ratelimited prints on sync lost and FIFO underrun interrupts.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 8
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 4 ++--
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
Disable the sync lost interrupt if it fires on every frame for 50
consecutive frames in a row. This is relatively sure sign of the sync
lost interrupt being stuck and firing on every frame even if the
display otherwise appears to work OK.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilc
From: Tomi Valkeinen
Disable crtc on unload. Call tilcdc_crtc_dpms() with DRM_MODE_DPMS_OFF
in the beginning of unload function.
Signed-off-by: Tomi Valkeinen
[Added description to the patch]
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 2 ++
1 file changed, 2 insertion
From: Tomi Valkeinen
Get rid of complex ping-pong mechanism and replace it with simpler
single buffer flipping code.
The LCDC HW appears to be designed mainly static framebuffers in
mind. There are two modes of operation, either static single buffer,
or ping pong double buffering with two static
From: Darren Etheridge
The frame_done interrupt was only being enabled when the vsync
interrupts were being enabled by DRM. However the frame_done is
used to determine if the LCD controller has successfully completed
the raster_enable, raster_disable commands and the vsync interrupts
are not alw
We have not been too active in pushing the tilcdc fixes to
mainline. This series tries to bring the mainline tilcdc upto same
level with TI ti-linux tree.
Some patches that touch the same place over and over again have been
squashed into one, leaving author of the last rewrite on top.
Best regard
There is nothing special about tilcdc HW when the video memory is
concerned. Just using the standard drm helpers for implementation is
enough.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drive
From: Tomi Valkeinen
LCDC hardware does not support fb pitch that is different (i.e. larger)
than the screen size. The driver currently does no checks for this, and
the results of too big pitch are are flickering and lower fps.
This issue easily happens when using libdrm's modetest tool with non
forward xorg.conf and Xorg.0.log files from my testing.
--
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/20160204/6b57ed31/attachm
Op 03-02-16 om 21:09 schreef Gustavo Padovan:
> Hi Maarten,
>
> 2016-02-03 Maarten Lankhorst :
>
>> Op 03-02-16 om 14:25 schreef Gustavo Padovan:
>>> From: Gustavo Padovan
>>>
>>> Turn sync_fence_info into __u64 type enable us to extend the struct in the
>>> future without breaking the ABI.
>>>
>>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20160204/7478f79d/attachment.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20160204/4c8c74bf/attachment.html>
On Tue, 2 Feb 2016 15:50:36 -0600
Rob Herring wrote:
> > diff --git a/Documentation/devicetree/bindings/display/sunxi.txt
> > b/Documentation/devicetree/bindings/display/sunxi.txt
> > new file mode 100644
> > index 000..35f9763
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/di
On Thu, Feb 4, 2016 at 2:37 PM, CK Hu wrote:
> Hi Philipp:
>
> On Wed, 2016-02-03 at 12:01 +0100, Philipp Zabel wrote:
>> Hi Daniel,
>>
>
>> > > +static void mtk_output_dsi_disable(struct mtk_dsi *dsi)
>> > > +{
>> > > + if (!dsi->enabled)
>> > > + return;
>> > > +
>> > > +
Am Donnerstag, den 04.02.2016, 14:37 +0800 schrieb CK Hu:
> Hi Philipp:
>
> On Wed, 2016-02-03 at 12:01 +0100, Philipp Zabel wrote:
> > Hi Daniel,
> >
>
> > > > +static void mtk_output_dsi_disable(struct mtk_dsi *dsi)
> > > > +{
> > > > + if (!dsi->enabled)
> > > > + return;
Hi Philipp,
On 3 February 2016 at 19:25, Philipp Zabel wrote:
> diff --git a/drivers/gpu/drm/mediatek/Kconfig
> b/drivers/gpu/drm/mediatek/Kconfig
> index 8dad892..b7e0404 100644
> --- a/drivers/gpu/drm/mediatek/Kconfig
> +++ b/drivers/gpu/drm/mediatek/Kconfig
> @@ -3,6 +3,9 @@ config DRM_MEDIA
ou're wondering about the padding in the header above, note that
this header never gets passed in from userspace, it's a header for data
read by userspace and the driver zeros the padding.
For the hole in the ioctl I'll probably fill that by extending the flags
member and the driver currently returns -EINVAL if any unknown flag bits
are set by userspace.
Thanks for looking through this,
- Robert
>
> -Emil
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20160204/84447ccd/attachment.html>
Op 04-02-16 om 14:05 schreef Gustavo Padovan:
> 2016-02-04 Maarten Lankhorst :
>
>> Op 03-02-16 om 21:09 schreef Gustavo Padovan:
>>> Hi Maarten,
>>>
>>> 2016-02-03 Maarten Lankhorst :
>>>
Op 03-02-16 om 14:25 schreef Gustavo Padovan:
> From: Gustavo Padovan
>
> Turn sync_fence_in
Hi Emil,
Am Donnerstag, den 04.02.2016, 13:09 + schrieb Emil Velikov:
> Hi Philipp,
>
> On 3 February 2016 at 19:25, Philipp Zabel wrote:
>
> > diff --git a/drivers/gpu/drm/mediatek/Kconfig
> > b/drivers/gpu/drm/mediatek/Kconfig
> > index 8dad892..b7e0404 100644
> > --- a/drivers/gpu/drm/m
On 29 January 2016 at 16:00, Rob Herring wrote:
> From: Sumit Semwal
>
> Android needs libdrm built statically for recovery;
> enable that as well.
>
> Signed-off-by: Sumit Semwal
> Signed-off-by: Rob Herring
> Cc: Chih-Wei Huang
> Cc: Emil Velikov
> ---
> I posted this to mesa-dev, but I gue
The warning message in drm_mode_parse_command_line_for_connector miss
the [drm] at beginning.
This patch add it and take the opportunity to convert
printk(KERN_WARNING to pr_warn()
Signed-off-by: LABBE Corentin
---
drivers/gpu/drm/drm_modes.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(
attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20160204/c927f3e9/attachment.html>
instead.
Am also renaming properties to properties_ptr which seems the norm in
i915_drm.h.
- Robert
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20160204/cedc2dbd/attachment.html>
Share with upcoming CP tests.
Reviewed-by: Ken Wang
Signed-off-by: Alex Deucher
---
tests/amdgpu/basic_tests.c | 58 --
1 file changed, 35 insertions(+), 23 deletions(-)
diff --git a/tests/amdgpu/basic_tests.c b/tests/amdgpu/basic_tests.c
index fa0ed
So it can be shared for CP tests.
Reviewed-by: Ken Wang
Signed-off-by: Alex Deucher
---
tests/amdgpu/basic_tests.c | 26 +-
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git a/tests/amdgpu/basic_tests.c b/tests/amdgpu/basic_tests.c
index 1bcc835..5804503 10064
Use the CP to write data to memory.
Reviewed-by: Ken Wang
Signed-off-by: Alex Deucher
---
tests/amdgpu/basic_tests.c | 125 +
1 file changed, 125 insertions(+)
diff --git a/tests/amdgpu/basic_tests.c b/tests/amdgpu/basic_tests.c
index 5804503..5c9deb
So it can be shared for CP tests.
Reviewed-by: Ken Wang
Signed-off-by: Alex Deucher
---
tests/amdgpu/basic_tests.c | 27 +--
1 file changed, 17 insertions(+), 10 deletions(-)
diff --git a/tests/amdgpu/basic_tests.c b/tests/amdgpu/basic_tests.c
index 7806be7..701ccf1 100
Use the CP to copy data between buffers
Reviewed-by: Ken Wang
Signed-off-by: Alex Deucher
---
tests/amdgpu/basic_tests.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/tests/amdgpu/basic_tests.c b/tests/amdgpu/basic_tests.c
index 701ccf1..aac5615 100644
--- a/tests/amdg
So it can be shared for CP tests.
Reviewed-by: Ken Wang
Signed-off-by: Alex Deucher
---
tests/amdgpu/basic_tests.c | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/tests/amdgpu/basic_tests.c b/tests/amdgpu/basic_tests.c
index 5c9debe..4d382e6 100644
Use the CP to fill to memory.
Reviewed-by: Ken Wang
Signed-off-by: Alex Deucher
---
tests/amdgpu/basic_tests.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/tests/amdgpu/basic_tests.c b/tests/amdgpu/basic_tests.c
index 4d382e6..7806be7 100644
--- a/tests/amdgpu/basic_t
Hi,
On Thu, Feb 04, 2016 at 03:03:52PM +0100, LABBE Corentin wrote:
> The warning message in drm_mode_parse_command_line_for_connector miss
> the [drm] at beginning.
> This patch add it and take the opportunity to convert
> printk(KERN_WARNING to pr_warn()
>
> Signed-off-by: LABBE Corentin
> ---
We accidentally point both cfgcr registers for the second shared DPLL to
the same location in i915_reg.h. This results in a lot of hw pipe state
mismatches whenever we try to do a modeset that requires allocating the
DPLL to a CRTC:
[drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_h
On 4 February 2016 at 14:59, Alex Deucher wrote:
> Share with upcoming CP tests.
>
> Reviewed-by: Ken Wang
> Signed-off-by: Alex Deucher
> ---
> tests/amdgpu/basic_tests.c | 58
> --
> 1 file changed, 35 insertions(+), 23 deletions(-)
>
> diff --git
On 4 February 2016 at 14:59, Alex Deucher wrote:
> So it can be shared for CP tests.
>
> Reviewed-by: Ken Wang
> Signed-off-by: Alex Deucher
> ---
> tests/amdgpu/basic_tests.c | 27 +--
> 1 file changed, 17 insertions(+), 10 deletions(-)
>
> diff --git a/tests/amdgpu/bas
On Thu, Feb 4, 2016 at 10:43 AM, Emil Velikov
wrote:
> On 4 February 2016 at 14:59, Alex Deucher wrote:
>> Share with upcoming CP tests.
>>
>> Reviewed-by: Ken Wang
>> Signed-off-by: Alex Deucher
>> ---
>> tests/amdgpu/basic_tests.c | 58
>> --
>>
On Thu, Feb 4, 2016 at 10:47 AM, Emil Velikov
wrote:
> On 4 February 2016 at 14:59, Alex Deucher wrote:
>> So it can be shared for CP tests.
>>
>> Reviewed-by: Ken Wang
>> Signed-off-by: Alex Deucher
>> ---
>> tests/amdgpu/basic_tests.c | 27 +--
>> 1 file changed, 17
On Thu, Feb 04, 2016 at 10:43:21AM -0500, Lyude wrote:
> We accidentally point both cfgcr registers for the second shared DPLL to
> the same location in i915_reg.h. This results in a lot of hw pipe state
> mismatches whenever we try to do a modeset that requires allocating the
> DPLL to a CRTC:
>
Hi guys,
any feedback? patch will be accepted for adv7511 driver?
Regards,
C.Palminha
On 01-02-2016 12:37, Carlos Palminha wrote:
> Hi Laurent
>
> On 29-01-2016 17:48, Laurent Pinchart wrote:
>> Hi Carlos,
>>
>> Thank you for the patch.
>>
>> On Friday 29 January 2016 10:33:47 Carlos Palminha w
Size of kmalloc() in vga_arb_write() is controlled by user.
Too large kmalloc() size triggers WARNING message on console.
Use GFP_USER | __GFP_NOWARN for this kmalloc() to not scare admins.
Signed-off-by: Dmitry Vyukov
---
Example WARNING:
WARNING: CPU: 2 PID: 29322 at mm/page_alloc.c:2999
__al
2016-02-04 Maarten Lankhorst :
> Op 03-02-16 om 21:09 schreef Gustavo Padovan:
> > Hi Maarten,
> >
> > 2016-02-03 Maarten Lankhorst :
> >
> >> Op 03-02-16 om 14:25 schreef Gustavo Padovan:
> >>> From: Gustavo Padovan
> >>>
> >>> Turn sync_fence_info into __u64 type enable us to extend the struct
On Thu, Feb 04, 2016 at 04:49:49PM +0100, Dmitry Vyukov wrote:
> Size of kmalloc() in vga_arb_write() is controlled by user.
> Too large kmalloc() size triggers WARNING message on console.
>
> Use GFP_USER | __GFP_NOWARN for this kmalloc() to not scare admins.
>
> Signed-off-by: Dmitry Vyukov
>
On Thu, Feb 04, 2016 at 05:37:49PM +0100, Dmitry Vyukov wrote:
> On Thu, Feb 4, 2016 at 5:32 PM, Ville Syrjälä
> wrote:
> > On Thu, Feb 04, 2016 at 04:49:49PM +0100, Dmitry Vyukov wrote:
> >> Size of kmalloc() in vga_arb_write() is controlled by user.
> >> Too large kmalloc() size triggers WARNI
On Thu, 04 Feb 2016, Lukas Wunner wrote:
> Hi,
>
> On Thu, Feb 04, 2016 at 03:03:52PM +0100, LABBE Corentin wrote:
>> The warning message in drm_mode_parse_command_line_for_connector miss
>> the [drm] at beginning.
>> This patch add it and take the opportunity to convert
>> printk(KERN_WARNING to
Share with upcoming CP tests.
v2: drop unnecessary forward declaration
Reviewed-by: Ken Wang
Signed-off-by: Alex Deucher
---
tests/amdgpu/basic_tests.c | 51 +-
1 file changed, 28 insertions(+), 23 deletions(-)
diff --git a/tests/amdgpu/basic_tests.
From: Ken Wang
Avoid a crash if no IBs are specified.
Signed-off-by: Ken Wang
Reviewed-by: Alex Deucher
---
amdgpu/amdgpu_cs.c | 8
amdgpu/amdgpu_internal.h | 1 +
2 files changed, 9 insertions(+)
diff --git a/amdgpu/amdgpu_cs.c b/amdgpu/amdgpu_cs.c
index b4f41b0..fb5b3a8 1006
because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20160204/7dcd9042/attachment.html>
scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20160204/fe9e05b4/attachment.html>
On Thu, Feb 4, 2016 at 7:30 AM, Emil Velikov
wrote:
> On 29 January 2016 at 16:00, Rob Herring wrote:
>> From: Sumit Semwal
>>
>> Android needs libdrm built statically for recovery;
>> enable that as well.
>>
>> Signed-off-by: Sumit Semwal
>> Signed-off-by: Rob Herring
>> Cc: Chih-Wei Huang
This is ABI future-proofing if we ever want to extend the pad to mean
something.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_gem.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_gem.c b/drivers/gpu/drm/vc4/vc4_gem.c
index 48ce30a..cc89ffc 100644
--- a/d
Apparently in hardware (as opposed to simulation), the clear colors
need to be uploaded before the render config, otherwise they won't
take effect. Fixes igt's vc4_wait_bo/used-bo-* subtests.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_render_cl.c | 18 +-
1 file chan
Here's a series of fixes for vc4 from writing igt testcases while
debugging X window dragging.
Eric Anholt (5):
drm/vc4: Validate that WAIT_BO padding is cleared.
drm/vc4: Fix the clear color for the first tile rendered.
drm/vc4: Return an ERR_PTR from BO creation instead of NULL.
drm/vc4:
Fixes igt vc4_create_bo/create-bo-0 by returning -EINVAL from the
ioctl instead of -ENOMEM.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_bo.c| 16
drivers/gpu/drm/vc4/vc4_gem.c | 4 ++--
drivers/gpu/drm/vc4/vc4_irq.c | 2 +-
drivers/gpu/drm/vc4/vc
These ioctls end up getting exposed to fairly directly to GL users,
and having normal user operations print DRM errors is obviously wrong.
The message was originally to give us some idea of what happened when
a hang occurred, but we have a DRM_INFO from reset for that.
Signed-off-by: Eric Anholt
This caused the wait ioctls to claim that waiting had completed when
we actually got interrupted by a signal before it was done. Fixes
broken rendering throttling that produced serious lag in X window
dragging.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_gem.c | 6 ++
1 file chan
nt was scrubbed...
Name: 0001-drm-dp-mst-Fix-32-bit-fixed-point-division-calculati.patch
Type: application/octet-stream
Size: 984 bytes
Desc: 0001-drm-dp-mst-Fix-32-bit-fixed-point-division-calculati.patch
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20160204/d5ddea10/
set it in the first place.
--
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/20160204/1519bf0e/attachment.html>
On Wed, Feb 3, 2016 at 4:04 PM, Dave Airlie wrote:
>
> I'm happy enough it shouldn't cause any problems, just wanted to
> check if you'd take it now or not.
Honestly, this feels like "might as well wait for 4.6" to me.
I'm generally ok with taking completely new drivers later in the rc if
there'
Here's the major series I have currently for 4.6: Overlay plane
support. There's definitely more work to be done here, on better
filter kernels at various sizes, choosing our scaling modes better,
and being more aggressive on LBM allocation (right now I think we're
barely allocating for YUV 1:1 at
Previously, on every modeset we would allocate new display list
memory, recompute changed planes, write all of them to the new memory,
and pointed scanout at the new list (which will latch approximately at
the next line of scanout). We let
drm_atomic_helper_wait_for_vblanks() decide whether we nee
As we add actual scaling, this is going to get way more complicated.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_plane.c | 78 +++--
1 file changed, 52 insertions(+), 26 deletions(-)
diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc
Previously we only did the primary and cursor plane, but overlay
planes are useful and just require this setup to add, since all planes
go into the HVS display list in the same way.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_crtc.c | 56 ++
1 f
This implements a simple policy for choosing scaling modes
(trapezoidal for decimation, PPF for magnification), and a single PPF
filter (Mitchell/Netravali's recommendation).
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_drv.h | 4 +
drivers/gpu/drm/vc4/vc4_hvs.c | 85 +++
This supports 420 and 422 subsampling with 2 or 3 planes, tested with
modetest. It doesn't set up chroma subsampling position (which it
appears KMS doesn't deal with yet).
The LBM memory is overallocated in many cases, but apparently the docs
aren't quite correct and I'll probably need to look at
These were all touch-tested with modetest.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_plane.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc4/vc4_plane.c
index 7cedc726..9a390cf 100644
--- a/drivers/gpu/drm/v
So far, we've only ever lit up one CRTC, so this has been fine. To
extend to more displays or more planes, we need to make sure we don't
run our display lists into each other.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_crtc.c | 115 +++--
drivers/
This is the pointer to the HVS device's memory where we stored the
contents of *dlist.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_plane.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc4/vc4_plane.c
index 45e353
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_plane.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc4/vc4_plane.c
index 0addbad..45e353d 100644
--- a/drivers/gpu/drm/vc4/vc4_plane.c
+++ b/drivers/gpu/drm/v
This doesn't matter yet since we only allow 1:1 scaling, but the
comment clearly says we should be using the source size.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_plane.c | 23 ++-
1 file changed, 14 insertions(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/vc
On 2016-02-03 15:18, Stefan Agner wrote:
> On 2016-02-03 06:00, Thierry Reding wrote:
>> On Wed, Jan 27, 2016 at 06:46:50PM -0800, Stefan Agner wrote:
>> [...]
>>> > diff --git a/drivers/gpu/drm/panel/panel-simple.c
>>> > b/drivers/gpu/drm/panel/panel-simple.c
>>> > index f97b73e..fa68b56 100644
>>
next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20160204/e4b43733/attachment.html>
On Tue, Dec 22, 2015 at 1:36 PM, Tiago Vignatti
wrote:
> Hey back,
>
> Thank you Daniel, Chris, Alex and Thomas for reviewing the last series. I
> think I addressed most of the comments now in version 7, including:
> - being even more wording in the doc about sync usage.
> - pass .write = fals
nts/20160204/c15f3787/attachment.html>
On 02/04/2016 04:22 PM, Carlos Palminha wrote:
> Hi guys,
>
> any feedback? patch will be accepted for adv7511 driver?
Hi,
Thanks for the patch, but please try to find and fix the call site that is
trying to invoke the callback even though it does not exist.
This is most likely drm_i2c_encoder_
On 4 February 2016 at 15:51, Alex Deucher wrote:
> On Thu, Feb 4, 2016 at 10:47 AM, Emil Velikov
> wrote:
>> On 4 February 2016 at 14:59, Alex Deucher wrote:
>>> So it can be shared for CP tests.
>>>
>>> Reviewed-by: Ken Wang
>>> Signed-off-by: Alex Deucher
>>> ---
>>> tests/amdgpu/basic_tes
Looking back over my bug history I found this activity:
https://bugzilla.kernel.org/show_bug.cgi?id=60857
--
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/
On Thu, Feb 4, 2016 at 4:38 PM, Emil Velikov
wrote:
> On 4 February 2016 at 15:51, Alex Deucher wrote:
>> On Thu, Feb 4, 2016 at 10:47 AM, Emil Velikov
>> wrote:
>>> On 4 February 2016 at 14:59, Alex Deucher wrote:
So it can be shared for CP tests.
Reviewed-by: Ken Wang
S
|RESOLVED
--
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/20160204/2b6fd49f/attachment.html>
1 - 100 of 105 matches
Mail list logo