[PATCH v2 3/3] ARM: dts: add Panel device support for exynos3250-rinato

2014-12-09 Thread Hyungwon Hwang
From: Inki Dae inki@samsung.com This patch adds MIPI-DSI and MIPI-DSI based S6E63J0X03 AMOLED panel device nodes for Exynos3250 Rinato board. Signed-off-by: Inki Dae inki@samsung.com Signed-off-by: Hyungwon Hwang human.hw...@samsung.com Acked-by: Kyungmin Park kyungmin.p...@samsung.com

[PATCH v2 0/3] add display support for exynos3250 rinato board

2014-12-09 Thread Hyungwon Hwang
This is v2 of the patchset adding support for s6e63j0x03 lcd panel. Inki Dae sent this patchset before. Because of his busy work at company, I modifies some point according to the review by Thierry Reding on behalf of him. This patch series adds Display support for exynos3250 Rinato board. For

[PATCH v2 1/3] ARM: dts: add fimd device support for exynos3250-rinato

2014-12-09 Thread Hyungwon Hwang
From: Inki Dae inki@samsung.com This patch adds fimd device node which is a display controller for Exynos3250 Rinato board. Signed-off-by: Inki Dae inki@samsung.com Signed-off-by: Hyungwon Hwang human.hw...@samsung.com Acked-by: Kyungmin Park kyungmin.p...@samsung.com --- Changes for v2:

[PATCH v2 2/3] drm/panel: add s6e63j0x03 LCD panel driver

2014-12-09 Thread Hyungwon Hwang
From: Inki Dae inki@samsung.com This patch adds MIPI-DSI based S6E63J0X03 AMOLED LCD panel driver which uses mipi_dsi bus to communicate with panel. The panel has 320×320 resolution in 1.63-inch physical panel. This panel is used in Samsung Galaxy Gear 2. Signed-off-by: Inki Dae

Re: drm/exynos: some small forgotten patch

2014-12-09 Thread Inki Dae
Hi, On 2014년 11월 30일 09:35, tjak...@math.uni-bielefeld.de wrote: Hello, while looking through my local kernel tree, I noticed that this patch for the mixer component of drm/exynos, posted some time ago, was That might be a patch I missed. Can you tell me the Subject? Thanks, Inki Dae

Re: [PATCH] drm/exynos/fimd: only finish pageflip if START == START_S

2014-12-09 Thread Inki Dae
On 2014년 11월 26일 03:12, Gustavo Padovan wrote: From: Daniel Kurtz djku...@chromium.org A framebuffer gets committed to FIMD's default window like this: exynos_drm_crtc_update() exynos_plane_commit() fimd_win_commit() fimd_win_commit() programs BUF_START[0]. At each vblank, FIMD

Re: [PATCH] clk: samsung: Fix Exynos 5420 pinctrl setup and clock disable failure due to domain being gated

2014-12-09 Thread Krzysztof Kozlowski
On pią, 2014-12-05 at 15:15 +0100, Krzysztof Kozlowski wrote: Audio subsystem clocks are located in separate block. On Exynos 5420 if clock for this block (from main clock domain) 'mau_epll' is gated then any read or write to audss registers will block. This kind of boot hang was observed on

Re: [PATCH] clk: samsung: Fix Exynos 5420 pinctrl setup and clock disable failure due to domain being gated

2014-12-09 Thread Sylwester Nawrocki
On 09/12/14 13:59, Krzysztof Kozlowski wrote: On pią, 2014-12-05 at 15:15 +0100, Krzysztof Kozlowski wrote: Audio subsystem clocks are located in separate block. On Exynos 5420 if clock for this block (from main clock domain) 'mau_epll' is gated then any read or write to audss registers

Re: [PATCH] clk: samsung: Fix Exynos 5420 pinctrl setup and clock disable failure due to domain being gated

2014-12-09 Thread Javier Martinez Canillas
Hello, On 12/09/2014 02:18 PM, Sylwester Nawrocki wrote: This is a non-intrusive workaround for that issue, as wanted by Sylwester: https://lkml.org/lkml/2014/12/5/223 Any comments on this? The patch looks OK to me, it would be good though if someone else has confirmed it fixes the

[RFC PATCHv2 3/7] devfreq: event: Add the exclusive flag for devfreq-event device

2014-12-09 Thread Chanwoo Choi
This patch adds the exclusive flag for devfreq-event device. If the specific devfreq-event device should be used in only one devfreq device driver, devfreq driver have to use 'devfreq_enable_event_dev_exclusive()' function to consist integrity of event data. Cc: MyungJoo Ham

[RFC PATCHv2 6/7] ARM: dts: Add PPMU dt node for Exynos4 SoC

2014-12-09 Thread Chanwoo Choi
This patch add PPMU (Performance Profiling Monitoring Unit) dt node for Exynos4 (Exynos4210/4212/4412) SoC. PPMU dt node is used to monitor the utilization of each IP. The Exynos4210/Exynos4212/Exynos4412 SoC includes following PPMUs: - PPMU_DMC0 0x106A_ - PPMU_DMC1 0x106B_ -

[RFC PATCHv2 2/7] devfreq: event: Add the list of supported devfreq-event type

2014-12-09 Thread Chanwoo Choi
This patch adds the list of supported devfreq-event type as following. Each devfreq-event device driver would support the various devfreq-event type for devfreq governor at the same time. - DEVFREQ_EVENT_TYPE_RAW_DATA - DEVFREQ_EVENT_TYPE_UTILIZATION - DEVFREQ_EVENT_TYPE_BANDWIDTH -

[RFC PATCHv2 5/7] ARM: dts: Add PPMU dt node for Exynos3250

2014-12-09 Thread Chanwoo Choi
This patch add PPMU (Performance Profiling Monitoring Units) dt node to estimate the utilization of each IP in Exynos SoC throught DEVFREQ Event subsystem. This patch adds following PPMU dt nodes: - PPMU_DMC0 0x106a - PPMU_DMC1 0x106b - PPMU_RIGHTBUS 0x112A - PPMU_LEFTBUS

[RFC PATCHv2 0/7] devfreq: Add devfreq-event class to provide raw data for devfreq device

2014-12-09 Thread Chanwoo Choi
This patchset add new devfreq_event class to provide raw data to determine current utilization of device which is used for devfreq governor. [Description of devfreq-event class] This patchset add new devfreq_event class for devfreq_event device which provide raw data (e.g., memory bus

[RFC PATCHv2 1/7] devfreq: event: Add new devfreq_event class to provide basic data for devfreq governor

2014-12-09 Thread Chanwoo Choi
This patch add new devfreq_event class for devfreq_event device which provide raw data (e.g., memory bus utilization/GPU utilization). This raw data from devfreq_event data would be used for the governor of devfreq subsystem. - devfreq_event device : Provide raw data for governor of existing

[RFC PATCHv2 7/7] ARM: dts: exynos: Add PPMU dt node to Exynos3250-based Rinato board

2014-12-09 Thread Chanwoo Choi
This patch add PPMU dt node to Exynos3250-base Rinato board. The PPMU dt node is used to get the utilization of DMC0/DMC1/CPU Block. Cc: Kukjin Kim kgene@samsung.com Signed-off-by: Chanwoo Choi cw00.c...@samsung.com Acked-by: Kyungmin Park kyungmin.p...@samsung.com ---

[RFC PATCHv2 4/7] devfreq: event: Add exynos-ppmu devfreq event driver

2014-12-09 Thread Chanwoo Choi
This patch add exynos-ppmu devfreq event driver to provider raw data about the utilization of each IP in Exynos SoC series. Cc: MyungJoo Ham myungjoo@samsung.com Cc: Kyungmin Park kyungmin.p...@samsung.com Signed-off-by: Chanwoo Choi cw00.c...@samsung.com --- drivers/devfreq/Kconfig

Re: [PATCH] dmaengine: pl330: Set residue in tx_status callback

2014-12-09 Thread Jassi Brar
On 8 December 2014 at 18:37, Vinod Koul vinod.k...@intel.com wrote: On Sat, Dec 06, 2014 at 12:31:01PM +0530, Jassi Brar wrote: It does, though, create an awkward situation when a channel is active while new requests are submitted - why would the channel want to stop after current transfer and

Re: drm/exynos: some small forgotten patch

2014-12-09 Thread Tobias Jakobi
On 2014-12-09 13:09, Inki Dae wrote: That might be a patch I missed. Can you tell me the Subject? Uhm, I think that is obvious from the mail? http://www.spinics.net/lists/linux-samsung-soc/msg39811.html Anyway, I'm still waiting for Thierry's reply on that matter. With best wishes, Tobias --

Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)

2014-12-09 Thread Nishanth Menon
On 10:13-20141205, Nishanth Menon wrote: On 12/05/2014 10:10 AM, Nishanth Menon wrote: next-20141204 fails to boot, but next-20141203 boots fine with omap2plus_defconfig. Panda-ES(4460): https://github.com/nmenon/kernel-test-logs/blob/next-20141204/omap2plus_defconfig/pandaboard-es.txt

Re: [PATCH 0/20] fix misspelling of current function in string

2014-12-09 Thread Julian Calaby
Hi Julia, On Mon, Dec 8, 2014 at 5:43 PM, Julia Lawall julia.law...@lip6.fr wrote: On Mon, 8 Dec 2014, Julian Calaby wrote: Hi Julia, On Mon, Dec 8, 2014 at 6:20 AM, Julia Lawall julia.law...@lip6.fr wrote: These patches replace what appears to be a reference to the name of the current

Re: [PATCH RFT 1/2] drivers: bus: check cci device tree node status

2014-12-09 Thread Abhilash Kesavan
Hi, On Fri, Nov 28, 2014 at 8:20 PM, Abhilash Kesavan a.kesa...@samsung.com wrote: The arm-cci driver completes the probe sequence even if the cci node is marked as disabled. Add a check in the driver to honour the cci status in the device tree. Signed-off-by: Abhilash Kesavan

Re: [PATCH RFT 1/2] drivers: bus: check cci device tree node status

2014-12-09 Thread Sudeep Holla
Hi Abhilash, On Wednesday 10 December 2014 09:31 AM, Abhilash Kesavan wrote: Hi, On Fri, Nov 28, 2014 at 8:20 PM, Abhilash Kesavan a.kesa...@samsung.com wrote: The arm-cci driver completes the probe sequence even if the cci node is marked as disabled. Add a check in the driver to honour the

Re: [PATCH RFT 1/2] drivers: bus: check cci device tree node status

2014-12-09 Thread Abhilash Kesavan
Hi Sudeep, On Wed, Dec 10, 2014 at 9:44 AM, Sudeep Holla sudeep.ho...@arm.com wrote: Hi Abhilash, On Wednesday 10 December 2014 09:31 AM, Abhilash Kesavan wrote: Hi, On Fri, Nov 28, 2014 at 8:20 PM, Abhilash Kesavan a.kesa...@samsung.com wrote: The arm-cci driver completes the probe

Re: [PATCH RFT 1/2] drivers: bus: check cci device tree node status

2014-12-09 Thread Sudeep Holla
On Wednesday 10 December 2014 09:55 AM, Abhilash Kesavan wrote: Hi Sudeep, On Wed, Dec 10, 2014 at 9:44 AM, Sudeep Holla sudeep.ho...@arm.com wrote: Hi Abhilash, On Wednesday 10 December 2014 09:31 AM, Abhilash Kesavan wrote: Hi, On Fri, Nov 28, 2014 at 8:20 PM, Abhilash Kesavan