[PATCH 12/13] exynos/fimg2d: add g2d_reset() to public API

After the rewrite of the command buffer submission handling g2d_reset() is no longer called internally. Still the user might want to reset the G2D context so expose this call. Signed-off-by: Tobias Jakobi --- exynos/exynos-symbol-check | 1 +

Re: [PATCH v2] clk: samsung: fix cpu clock's flags checking

On 08/28, Bartlomiej Zolnierkiewicz wrote: > CLK_CPU_HAS_DIV1 and CLK_CPU_NEEDS_DEBUG_ALT_DIV masks were > incorrectly used as a bit numbers. Fix it. > > Tested on Exynos4210 based Origen board and on Exynos5250 based > Arndale board. > > Cc: Tomasz Figa > Cc: Michael

Re: [PATCH v3 2/4] Documentation: bindings: mfd: cros ec: document vbc EC property

On Mon, 21 Sep 2015, Emilio López wrote: > Some EC implementations include a small nvram space used to store > verified boot context data. This boolean property lets us indicate > whether this space is available or not on a specific EC implementation. > > Signed-off-by: Emilio López

[PATCH 04/13] exynos/fimg2d: add g2d_config_event

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

[PATCH 01/13] drm: Implement drmHandleEvent2()

Basically this is an extended version of drmHandleEvent(). drmHandleEvent() only handles core events (like e.g. page flips), but since kernel DRM drivers might use vendor-specific events to signal userspace the completion of pending jobs, etc., its desirable to provide a way to handle these

[PATCH 05/13] exynos: fimg2d: add g2d_exec2

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. v2: Add g2d_exec2() to Exynos symbol test. Signed-off-by: Tobias Jakobi ---

[PATCH 03/13] tests/exynos: add fimg2d performance analysis

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

[PATCH 00/13] drm/exynos: async G2D and g2d_move()

Hello, this series mostly touches G2D code. It introduces the following: (1) drmHandleEvent2() is added to enable processing of vendor-specific events. This will be used to expose asynchronous operation of the G2D. The necessary kernel infrastructure is already there since a lot of

[PATCH 02/13] exynos: Introduce exynos_handle_event()

Used to handle kernel events specific to the Exynos platform. Currently only G2D events are handled. v2: Adapt to container approach. v3: Add exynos_handle_event() to Exynos symbol test. Signed-off-by: Tobias Jakobi --- exynos/exynos-symbol-check | 1 +

[PATCH 06/13] tests/exynos: add fimg2d event test

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. v2: Add GPLv2 header, argument handling and documentation. Test is only installed when requested. v3: Allocate G2D jobs with calloc which fixes

[PATCH 09/13] exynos/fimg2d: add g2d_move

We already have g2d_copy() which implements G2D copy operations from one buffer to another. However we can't do a overlapping copy operation in one buffer. Add g2d_move() which acts like the standard memmove() and properly handles overlapping copies. Signed-off-by: Tobias Jakobi

[PATCH 07/13] tests/exynos: use XRGB8888 for framebuffer

This matches the G2D color mode that is used in the entire code. The previous (incorrect) RGBA would only work since the Exynos mixer did its configuration based on the bpp, and not based on the actual pixelformat. Signed-off-by: Tobias Jakobi ---

[PATCH 10/13] tests/exynos: add test for g2d_move

To check if g2d_move() works properly we create a small checkerboard pattern in the center of the screen and then shift this pattern around with g2d_move(). The pattern should be properly preserved by the operation. Signed-off-by: Tobias Jakobi ---

[PATCH 11/13] exynos/fimg2d: add exynos_bo_unmap()

This unmaps a previously mapped (via exynos_bo_map()) buffer object. Signed-off-by: Tobias Jakobi --- exynos/exynos-symbol-check | 1 + exynos/exynos_drm.c| 20 exynos/exynos_drmif.h | 1 + 3 files changed, 22 insertions(+)

[PATCH v5 15/17] drm: bridge: analogix/dp: try force hpd after plug in lookup failed

Some edp screen do not have hpd signal, so we can't just return failed when hpd plug in detect failed. This is an hardware property, so we need add a devicetree property "analogix,need-force-hpd" to indicate this sutiation. Signed-off-by: Yakir Yang --- Changes in v5: None

[PATCH v5 14/17] drm: bridge: analogix/dp: add max link rate and lane count limit for RK3288

There are some IP limit on rk3288 that only support 4 physical lanes of 2.7/1.6 Gbps/lane, so seprate them out by device_type flag. Signed-off-by: Yakir Yang --- Changes in v5: None Changes in v4: - Seprate the link-rate and lane-count limit out with the device_type flag.

[PATCH v5 0/17] Add Analogix Core Display Port Driver

Hi all, The Samsung Exynos eDP controller and Rockchip RK3288 eDP controller share the same IP, so a lot of parts can be re-used. I split the common code into bridge directory, then rk3288 and exynos only need to keep some platform code. Cause I can't find the exact IP name of exynos dp

[PATCH v5 06/17] Documentation: drm/bridge: add document for analogix_dp

Analogix dp driver is split from exynos dp driver, so we just make an copy of exynos_dp.txt, and then simplify exynos_dp.txt Beside update some exynos dtsi file with the latest change according to the devicetree binding documents. Signed-off-by: Yakir Yang --- Changes in

[PATCH v5 13/17] drm: bridge: analogix/dp: add some rk3288 special registers setting

RK3288 need some special registers setting, we can separate them out by the dev_type of plat_data. Signed-off-by: Yakir Yang --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: - Fix compile failed dut to phy_pd_addr variable misspell error

[PATCH v5 11/17] Documentation: phy: add document for rockchip dp phy

This phy driver is binded with the Rockchip DisplayPort driver, here are the brief properties: edp_phy: edp-phy@ff770274 { compatible = "rockchip,rk3288-dp-phy"; rockchip,grf = <>; clocks = < SCLK_EDP_24M>; clock-names =

[PATCH v5 17/17] drm: bridge: analogix/dp: add edid modes parse in get_modes method

Display Port monitor could support kinds of mode which indicate in monitor edid, not just one single display resolution which defined in panel or devivetree property display timing. Signed-off-by: Yakir Yang --- Changes in v5: None Changes in v4: - Call drm_panel_prepare()

[PATCH v5 07/17] ARM: dts: exynos/dp: remove some properties that deprecated by analogix_dp driver

After exynos_dp have been split the common IP code into analogix_dp driver, the analogix_dp driver have deprecated some Samsung platform properties which could be dynamically parsed from EDID/MODE/DPCD message, so this is an update for Exynos DTS file for dp-controller. Beside the backward

[PATCH v5 08/17] drm: rockchip: dp: add rockchip platform dp driver

Rockchip have three clocks for dp controller, we leave pclk_edp to analogix_dp driver control, and keep the sclk_edp_24m and sclk_edp in platform driver. Signed-off-by: Yakir Yang --- Changes in v5: - Remove the empty line at the end of document, and correct the endpoint

[PATCH v5 16/17] drm: bridge: analogix/dp: move hpd detect to connector detect function

This change just make a little clean to make code more like drm core expect, move hdp detect code from bridge->enable(), and place them into connector->detect(). Signed-off-by: Yakir Yang --- Changes in v5: None Changes in v4: - Take Jingoo suggest, add commit messages.

[PATCH v5 03/17] drm: bridge: analogix/dp: fix some obvious code style

Fix some obvious alignment problems, like alignment and line over 80 characters problems, make this easy to be maintained later. Signed-off-by: Yakir Yang --- Changes in v5: - Resequence this patch after analogix_dp driver have been split from exynos_dp code, and rephrase

[PATCH v5 09/17] Documentation: drm/bridge: add document for analogix_dp

Rockchip DP driver is a helper driver of analogix_dp coder driver, so most of the DT property should be descriped in analogix_dp document. Signed-off-by: Yakir Yang --- Changes in v5: - Split binding doc's from driver changes. (Rob) - Add eDP hotplug pinctrl property.

[PATCH v5 10/17] phy: Add driver for rockchip Display Port PHY

This phy driver would control the Rockchip DisplayPort module phy clock and phy power, it is relate to analogix_dp-rockchip dp driver. If you want DP works rightly on rockchip platform, then you should select both of them. Signed-off-by: Yakir Yang --- Changes in v5: -

[PATCH v5 04/17] drm: bridge: analogix/dp: remove duplicate configuration of link rate and link count

link_rate and lane_count already configured in analogix_dp_set_link_train(), so we don't need to config those repeatly after training finished, just remove them out. Beside Display Port 1.2 already support 5.4Gbps link rate, the maximum sets would change from {1.62Gbps, 2.7Gbps} to {1.62Gbps,

[PATCH v5 01/17] drm: exynos: dp: convert to drm bridge mode

In order to move exynos dp code to bridge directory, we need to convert driver drm bridge mode first. As dp driver already have a ptn3460 bridge, so we need to move ptn bridge to the next bridge of dp bridge. Signed-off-by: Yakir Yang --- Changes in v5: None Changes in v4: