This is a more 'flexible' version of g2d_exec allowing to pass
some flags which modify the behaviour of g2d_exec. Currently
only the 'async' operation flag is supported.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 15 +--
exynos/exynos_fimg2d.h | 6 ++
2 files chan
This tests async processing of G2D jobs. A separate thread is spawned
to monitor the DRM fd for events and check whether a G2D job was
completed.
Signed-off-by: Tobias Jakobi
---
tests/exynos/Makefile.am | 7 +-
tests/exynos/exynos_fimg2d_event.c | 248 +++
This event is specific to Exynos G2D DRM driver. Only
process it when Exynos support is enabled.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_drm.h | 12
xf86drm.h | 7 ++-
xf86drmMode.c | 18 ++
3 files changed, 36 insertions(+), 1 deletion(-)
Currently only fast solid color clear performance is measured.
A large buffer is allocated and solid color clear operations
are executed on it with randomly chosen properties (position
and size of the region, clear color). Execution time is
measured and output together with the amount of pixels
pro
This enables us to pass command buffers to the kernel which
trigger an event on the DRM fd upon completion.
The final goal is to enable asynchronous operation of the
G2D engine, similar to async page flips.
Passing the event userdata pointer through the G2D context
was chosen to not change the cur
Hello,
this series exposes async execution of G2D command buffers to userspace. Also
includes is a small performance analysis test, which can also be used to
stress test the engine. The async operation is of course also tested.
Please review and let me know what I can improve.
With best wishes
Changes fixes the misspelled of #interrups-cell.
arch/arm/boot/dts/exynos5420.dtsi:224: WARNING: 'interrups'
may be misspelled - perhaps 'interrupts'?
Tested on OdroidXU3 board.
Signed-off-by: Anand Moon
---
arch/arm/boot/dts/exynos5420.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 d
Hello Abhilash,
On 03/20/2015 06:40 PM, Abhilash Kesavan wrote:
>>
>> I have made some progress on this. This is the current state:
>>
>> If I use next-20141114 (which was when the S2R code first appeared in
>> linux-next), then all is good. next-20141117 is fine too but things
>> are broken in ne
Hi,
On Fri, Mar 20, 2015 at 9:59 PM, Abhilash Kesavan
wrote:
> Hi Javier,
>
> On Fri, Mar 20, 2015 at 9:46 PM, Javier Martinez Canillas
> wrote:
>> Hello Abhilash,
>>
>> On 03/20/2015 03:23 PM, Abhilash Kesavan wrote:
On 03/17/2015 06:35 PM, Kevin Hilman wrote:
>
> Anyone else havin
Hi Javier,
On Fri, Mar 20, 2015 at 9:46 PM, Javier Martinez Canillas
wrote:
> Hello Abhilash,
>
> On 03/20/2015 03:23 PM, Abhilash Kesavan wrote:
>>> On 03/17/2015 06:35 PM, Kevin Hilman wrote:
Anyone else having better luck with suspend/resume on peach-pi?
>>>
>>> # echo +2 > /sys
Hello Abhilash,
On 03/20/2015 03:23 PM, Abhilash Kesavan wrote:
>> On 03/17/2015 06:35 PM, Kevin Hilman wrote:
>>>
>>> Anyone else having better luck with suspend/resume on peach-pi?
>>>
>>
>> # echo +2 > /sys/class/rtc/rtc0/wakealarm && echo mem > /sys/power/state
>>
>> Suspend and CPUs shutdown
Hello Marek,
On 2015-03-20 16:11, Marek Szyprowski wrote:
It was my fault (I left attached JIG cable which prevents power off).
Now it works fine.
Tested on Trats2 (Exynos4412):
Tested-by: Krzysztof Kozlowski
Patch also looks good, so:
Reviewed-by: Krzysztof Kozlowski
Gentle ping for mergi
Hello,
On 2015-02-09 11:58, Krzysztof Kozlowski wrote:
2015-02-09 10:06 GMT+01:00 Krzysztof Kozlowski :
2015-02-09 8:25 GMT+01:00 Marek Szyprowski :
PS_HOLD based power off procedure is common for all Exynos SoCs, so use
it for every Exynos SoC.
Signed-off-by: Marek Szyprowski
---
arch/arm
Hello,
On Wed, Mar 18, 2015 at 4:01 PM, Javier Martinez Canillas
wrote:
> +people involved in Exynos5420 S2R support (Abhilash, Vikas and Pankaj)
>
> Hello Kevin,
>
> On 03/17/2015 06:35 PM, Kevin Hilman wrote:
>> I've tried suspend/resume on peach-pi using v4.0-rc4, next/master and
>> samsung/fo
On 13/03/15 12:38, Javier Martinez Canillas wrote:
> Exynos serial ports operate either in a DMA-based or interrupt-based
> modes. In DMA-based mode, the UART generates a transfer data request
> and a Transmission (Tx) interrupt in interrupt-based mode.
>
> The Tx IRQ is only unmasked in interrupt
Hello,
On 03/13/2015 12:38 PM, Javier Martinez Canillas wrote:
> Exynos serial ports operate either in a DMA-based or interrupt-based
> modes. In DMA-based mode, the UART generates a transfer data request
> and a Transmission (Tx) interrupt in interrupt-based mode.
>
> The Tx IRQ is only unmasked
On Tue, 2015-01-27 at 00:51 +0100, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Hi,
>
> here is patch-set to replace the existing domain_init and
> domain_destroy iommu-ops with the new domain_alloc and
> domain_free callbacks
>
> The new callbacks move the allocation of iommu domains into
> th
Hello,
On 03/20/2015 02:38 AM, Chanwoo Choi wrote:
> On 03/20/2015 10:29 AM, Tobias Jakobi wrote:
>> From: Markus Reichl
>>
>> The Exynos4412 SoC has a s3c6410 RTC where the source clock
>> is now a mandatory property.
>>
>> This patch fixes probe failure of s3c-rtc on Odroid-X2/U2/U3 boards.
>
2015-03-20 2:20 GMT+01:00 Tobias Jakobi :
> Hello!
>
> Tobias Jakobi wrote:
>> Hello Krzysztof,
>>
>> On 2015-02-17 14:24, Krzysztof Kozlowski wrote:
>>> Looking at the backtrace this seems very likely however I have
>>> troubles reproducing this. Any special tree or config is required
>>> (except
Hi Chanwoo,
> This patch adds the support for Exynos5433's TMU (Thermal Management
> Unit). Exynos5433 has a little different register bit fields as
> following description:
> - Support the eight trip points for rising/falling interrupt by using
> two registers
> - Read the calibration type (1-poi
20 matches
Mail list logo
