Re: drm: exynos: mixer: fix using usleep() in atomic context

On Mon, Dec 01, 2014 at 05:16:17PM +0100, Tobias Jakobi wrote: > On 2014-12-01 16:54, Thierry Reding wrote: > >On Sun, Nov 30, 2014 at 01:35:25AM +0100, tjak...@math.uni-bielefeld.de > >wrote: > >>From: Tomasz Stanislawski > >> > >>This patch fixes calling usleep_range() after taking reg_slock > >

[PATCH] arm64: dts: Add jpeg device node for Exynos7

Add jpeg device node for Exynos7 Signed-off-by: Tony K Nadackal --- arch/arm64/boot/dts/exynos/exynos7.dtsi | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm64/boot/dts/exynos/exynos7.dtsi b/arch/arm64/boot/dts/exynos/exynos7.dtsi index 332537c..db3561f 100644 --- a/arch/arm

[PATCH] arm64: dts: Add device node for mscl on exynos7

Add device node for mscl on exynos7 SoC. Signed-off-by: Tony K Nadackal --- arch/arm64/boot/dts/exynos/exynos7.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/boot/dts/exynos/exynos7.dtsi b/arch/arm64/boot/dts/exynos/exynos7.dtsi index f67319a..332537c 100644 --- a/arc

[PATCH] clk: samsung: exynos7: Add clocks for MSCL block

Add clock support for the MSCL block for Exynos7. Signed-off-by: Tony K Nadackal --- .../devicetree/bindings/clock/exynos7-clock.txt| 1 + drivers/clk/samsung/clk-exynos7.c | 124 + include/dt-bindings/clock/exynos7-clk.h| 40 ++- 3 fil

[PATCH] [media] s5p-jpeg: Adding Exynos7 Jpeg variant support

Fimp_jpeg used in Exynos7 is a revised version. Some register configurations are slightly different from Jpeg in Exynos4. Added one more variant SJPEG_EXYNOS7 to handle these differences. Signed-off-by: Tony K Nadackal --- This patch is created and tested on top of linux-next-20141210. It can be

[PATCH] [media] s5p-jpeg: Initialize cb and cr to zero.

To avoid garbage value written into image base address planes, initialize cb and cr of structure s5p_jpeg_addr to zero. Signed-off-by: Tony K Nadackal --- This patch is created and tested on top of linux-next-20141210. It can be cleanly applied on media-next and kgene/for-next. drivers/media/pl

[PATCH] [media] s5p-jpeg: Fix crash in jpeg isr due to multiple interrupts.

In case of corrupt images, multiple interrupts may occur due to different error scenarios. Since we are removing the src and dest buffers in the first interrupt itself, crash occurs in the second error interrupts. Disable the global interrupt before we start processing the interrupt avoid the cra

[PATCH] [media] s5p-jpeg: Clear JPEG_CODEC_ON bits in sw reset function

Bits EXYNOS4_DEC_MODE and EXYNOS4_ENC_MODE do not get cleared on software reset. These bits need to be cleared explicitly. Signed-off-by: Tony K Nadackal --- This patch is created and tested on top of linux-next-20141210. It can be cleanly applied on media-next and kgene/for-next. drivers/medi

[PATCH v7 2/3] ARM: dts: exynos3250-rinato: Add regulator-haptic node for haptics

This patch adds regulator-haptic device node controlled by regulator. Signed-off-by: Jaewon Kim Reviewed-by: Chanwoo Choi --- arch/arm/boot/dts/exynos3250-rinato.dts |7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts b/arch/arm/boot/dts/exynos

[PATCH v7 3/3] ARM: dts: exynos3250-monk: Add regulator-haptic node for haptics

This patch adds regulator-haptic device node controlled by regulator. Signed-off-by: Jaewon Kim --- arch/arm/boot/dts/exynos3250-monk.dts |7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/exynos3250-monk.dts b/arch/arm/boot/dts/exynos3250-monk.dts index 24822aa..71

[PATCH v7 1/3] Input: add regulator haptic driver

This patch adds support for haptic driver controlled by voltage of regulator. And this driver support for Force Feedback interface from input framework Signed-off-by: Jaewon Kim Signed-off-by: Hyunhee Kim Acked-by: Kyungmin Park Tested-by: Chanwoo Choi Reviewed-by: Chanwoo Choi Reviewed-by: P

[PATCH v7 0/3] Add regulator-haptic driver

This patch series adds regulator-haptic driver. The regulator-haptic has haptic motor and it is controlled by voltage of regulator via force feedback framework. Changes in v7: - move platform_data or of_node check. - prevent to start playing effect when kernel entering suspend state. Changes in

Re: [PATCH 08/13] drm/irq: Check for valid VBLANK before dereference

On 17.12.2014 01:53, Thierry Reding wrote: > From: Thierry Reding > > When accessing the array of per-CRTC VBLANK structures we must always > check that the index into the array is valid before dereferencing to > avoid crashing. > > Signed-off-by: Thierry Reding > --- > drivers/gpu/drm/drm_irq

Re: [PATCH RFC v3 1/2] PM / Domains: Extend API pm_genpd_dev_need_restore to use restore types

On Tue, Dec 16, 2014 at 4:40 PM, Marek Szyprowski wrote: > Hello, > > On 2014-12-13 17:51, Amit Daniel Kachhap wrote: >> >> Instead of using bool to restore suspended devices initially, use flags >> like GPD_DEV_SUSPEND_INIT, GPD_DEV_RESTORE_INIT and GPD_DEV_RESTORE_FORCE. >> The first two flags w

[RESEND PATCH 0/2] ARM: dts: add display device nodes for Exynos4415

This patch series adds display device nodes for Exynos4415 SoC support. The drm/exynos part of original patchset[1] was merged but DTS part is not yet. This is based on for-next branch in linux-samsung git. [1] http://www.spinics.net/lists/linux-samsung-soc/msg38649.html YoungJun Cho (2): ARM:

[PATCH 1/2] ARM: dts: add fimd device node to exynos4415.dtsi

This patch adds fimd device node to exynos4415.dtsi. Signed-off-by: YoungJun Cho Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos4415.dtsi | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/exynos4415.dtsi b/arch/arm/boot/dts/exynos4415.dtsi index c1c9b37..

[PATCH 2/2] ARM: dts: add mipi dsi device node to exynos4415.dtsi

This patch adds mipi dsi device node to exynos4415.dtsi. Signed-off-by: YoungJun Cho Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos4415.dtsi | 15 +++ 1 file changed, 15 insertions(+) diff --git a/arch/arm/boot/dts/exynos4415.dtsi b/arch/arm/boot/dts/exynos4415.dtsi index 30

[PATCHv3] clocksource: exynos_mct: Add the support for Exynos 64bit SoC

This patch adds the support for Exynos 64bit SoC. The delay_timer is only used for Exynos 32bit SoC. Cc: Daniel Lezcano Cc: Thomas Gleixner Cc: Kukjin Kim Cc: Mark Rutland Signed-off-by: Chanwoo Choi --- This patch set is tested on 64-bit Exynos SoC. I send only this patch from following patc

[PATCHv4 5/8] ARM: dts: Add PPMU dt node for Exynos3250 SoC

This patch add PPMU (Platform Performance Monitoring Unit) 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 0x116A

[PATCHv4 7/8] ARM: dts: Add PPMU dt node for Exynos5260 SoC

This patch adds PPMU (Performance Profiling Monitoring Unit) dt node Exynos5260 SoC. Exynos5260 SoC has following PPMU IPs: - PPMU_DREX0_S0 0x10c6 - PPMU_DREX0_S1 0x10c7 - PPMU_DREX1_S0 0x10c8 - PPMU_DREX1_S1 0x10c9 - PPMU_EAGLE0x10cc - PPMU_KFC 0x10cd - PPMU_MFC

[PATCHv4 3/8] devfreq: event: Add exynos-ppmu devfreq event driver

This patch adds exynos-ppmu devfreq-event driver to get performance data of each IP for Samsung Exynos SoC. These event from Exynos PPMU provide useful information about the behavior of the SoC that you can use when analyzing system performance, and made visible and can be counted using logic in ea

[PATCHv4 8/8] ARM: dts: exynos: Add PPMU dt node to Exynos3250-based Rinato board

This patch add PPMU dt node to Exynos3250-base Rinato board. The PPMU dt node is used to get the utilization of DMC0/DMC1/LEFTBUS/RIGHTBUS Block. Cc: Kukjin Kim Signed-off-by: Chanwoo Choi Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos3250-rinato.dts | 40

[PATCHv4 4/8] devfreq: event: Add documentation for exynos-ppmu devfreq-event driver

This patch adds the documentation for Exynos PPMU (Platform Performance Monitoring Unit) devfreq-event driver. Cc: MyungJoo Ham Cc: Kyungmin Park Signed-off-by: Chanwoo Choi --- .../bindings/devfreq/event/exynos-ppmu.txt | 110 + 1 file changed, 110 insertions(+) c

[PATCHv4 2/8] devfreq: event: Add the list of supported devfreq-event type

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 - DEVFREQ_EVENT_T

[PATCHv4 1/8] devfreq: event: Add new devfreq_event class to provide basic data for devfreq governor

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 devfre

[PATCHv4 0/8] devfreq: Add devfreq-event class to provide raw data for devfreq device

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 utilization

[PATCHv4 6/8] ARM: dts: Add PPMU dt node for Exynos4 SoCs

This patch add PPMU (Platform Performance 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_ - PPMU

Re: [Linaro-mm-sig] [PATCH v3 18/19] iommu: exynos: init from dt-specific callback instead of initcall

Hi Arnd, On Tuesday 16 December 2014 13:10:59 Arnd Bergmann wrote: > On Tuesday 16 December 2014 14:07:11 Laurent Pinchart wrote: > > On Tuesday 16 December 2014 12:40:28 Arnd Bergmann wrote: > > > On Monday 15 December 2014 18:13:23 Will Deacon wrote: > > > IOMMUs are not as low-level as sys

Re: [PATCH RFC v3 1/2] PM / Domains: Extend API pm_genpd_dev_need_restore to use restore types

Marek Szyprowski writes: > Hello, > > On 2014-12-13 17:51, Amit Daniel Kachhap wrote: >> Instead of using bool to restore suspended devices initially, use flags >> like GPD_DEV_SUSPEND_INIT, GPD_DEV_RESTORE_INIT and GPD_DEV_RESTORE_FORCE. >> The first two flags will be similar to the existing tru

Re: [PATCH] iommu/exynos: Fix arm64 allmodconfig build

On Monday 15 December 2014 15:54:42 Mark Brown wrote: > The Exynos IOMMU driver uses the ARM specific dmac_flush_range() and > outer_flush_range() functions. This breaks the build on arm64 allmodconfig > in -next since support has been merged for some Exynos ARMv8 SoCs. Add a > dependency on ARM to

Re: [PATCH 11/13] drm/irq: Document return values more consistently

On Tue, Dec 16, 2014 at 05:53:33PM +0100, Thierry Reding wrote: > From: Thierry Reding > > Some of the functions are documented inconsistently. Add Returns: > sections where missing and use consistent style to describe the return > value. > > Signed-off-by: Thierry Reding With the comment in p

Re: [PATCH 12/13] drm/irq: Expel legacy API

On Tue, Dec 16, 2014 at 06:59:28PM +0100, Daniel Vetter wrote: > On Tue, Dec 16, 2014 at 05:53:34PM +0100, Thierry Reding wrote: > > From: Thierry Reding > > > > These legacy functions all operate on the struct drm_device * and an > > index to the CRTC that they should access. This is bad because

Re: [PATCH 12/13] drm/irq: Expel legacy API

On Tue, Dec 16, 2014 at 05:53:34PM +0100, Thierry Reding wrote: > From: Thierry Reding > > These legacy functions all operate on the struct drm_device * and an > index to the CRTC that they should access. This is bad because it > requires keeping track of a global data structures to resolve the i

Re: [PATCH 09/13] drm/irq: Make pipe unsigned and name consistent

On Tue, Dec 16, 2014 at 05:53:31PM +0100, Thierry Reding wrote: > -void drm_wait_one_vblank(struct drm_device *dev, int crtc) > +void drm_wait_one_vblank(struct drm_device *dev, unsigned int pipe) > { > + struct drm_vblank_crtc *vblank = &dev->vblank[pipe]; > int ret; > u32 last; >

Re: [PATCH 0/2] Input: atmel_mxt_ts - Add support for T100 multi-touch

Hello Nick, On 12/16/2014 06:07 PM, Nick Dyer wrote: > On 16/12/14 16:49, Javier Martinez Canillas wrote: >> Awesome, what do you think about the change to have a common input device >> initialization function that I squashed in your original patch? >> mxt_initialize_t100_input_device() and mxt_in

Re: [PATCH 05/13] drm/imx: Store correct CRTC index in events

Am Dienstag, den 16.12.2014, 17:53 +0100 schrieb Thierry Reding: > From: Thierry Reding > > A negative pipe causes a special case to be triggered for drivers that > don't have proper VBLANK support. i.MX does support VBLANKs, so there is > no need for the fallback code. > > Cc: Philipp Zabel >

Re: [PATCH 04/13] drm/imx: Make pipe number unsigned

Am Dienstag, den 16.12.2014, 17:53 +0100 schrieb Thierry Reding: > From: Thierry Reding > > There's no reason whatsoever why this should ever be negative. > > Cc: Philipp Zabel > Signed-off-by: Thierry Reding Acked-by: Philipp Zabel thanks Philipp -- To unsubscribe from this list: send the

Re: [PATCH 0/2] Input: atmel_mxt_ts - Add support for T100 multi-touch

On 16/12/14 16:49, Javier Martinez Canillas wrote: > Awesome, what do you think about the change to have a common input device > initialization function that I squashed in your original patch? > mxt_initialize_t100_input_device() and mxt_initialize_t9_input_device() > are very similar so I think th

[PATCH 12/13] drm/irq: Expel legacy API

From: Thierry Reding These legacy functions all operate on the struct drm_device * and an index to the CRTC that they should access. This is bad because it requires keeping track of a global data structures to resolve the index to CRTC object lookup. In order to get rid of this global data new AP

[PATCH 11/13] drm/irq: Document return values more consistently

From: Thierry Reding Some of the functions are documented inconsistently. Add Returns: sections where missing and use consistent style to describe the return value. Signed-off-by: Thierry Reding --- drivers/gpu/drm/drm_irq.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --

[PATCH 05/13] drm/imx: Store correct CRTC index in events

From: Thierry Reding A negative pipe causes a special case to be triggered for drivers that don't have proper VBLANK support. i.MX does support VBLANKs, so there is no need for the fallback code. Cc: Philipp Zabel Signed-off-by: Thierry Reding --- drivers/gpu/drm/imx/ipuv3-crtc.c | 3 ++- 1 f

[PATCH 03/13] drm/exynos: Store correct CRTC index in events

From: Thierry Reding A negative pipe causes a special case to be triggered for drivers that don't have proper VBLANK support. Exynos does support VBLANKs, so there is no need for the fallback code. Cc: Inki Dae Cc: Joonyoung Shim Cc: Seung-Woo Kim Cc: Kyungmin Park Signed-off-by: Thierry Red

[PATCH 02/13] drm/bochs: Store correct CRTC index in events

From: Thierry Reding Previously a negative pipe caused a special case to be triggered for drivers that didn't have proper VBLANK support. The trigger for this special case is now independent of the pipe, so the correct CRTC index can now be stored in events. Cc: Gerd Hoffmann Signed-off-by: Thi

[PATCH 06/13] drm/rockchip: Store correct CRTC index in events

From: Thierry Reding A negative pipe causes a special case to be triggered for drivers that don't have proper VBLANK support. Rockchip does support VBLANKs, so there is no need for the fallback code. Cc: Mark Yao Signed-off-by: Thierry Reding --- drivers/gpu/drm/rockchip/rockchip_drm_vop.c |

[PATCH 10/13] drm/irq: Add drm_crtc_vblank_count_and_time()

From: Thierry Reding This function is the KMS native variant of drm_vblank_count_and_time(). It takes a struct drm_crtc * instead of a struct drm_device * and an index of the CRTC. Eventually the goal is to access vblank data through the CRTC only so that the per-CRTC data can be moved to struct

[PATCH 07/13] drm/sti: Store correct CRTC index in events

From: Thierry Reding A negative pipe causes a special case to be triggered for drivers that don't have proper VBLANK support. STi does support VBLANKs, so there is no need for the fallback code. Cc: Benjamin Gaignard Signed-off-by: Thierry Reding --- drivers/gpu/drm/sti/sti_drm_crtc.c | 2 +-

[PATCH 09/13] drm/irq: Make pipe unsigned and name consistent

From: Thierry Reding Name all references to the pipe number (CRTC index) consistently to make it easier to distinguish which is a pipe number and which is a pointer to struct drm_crtc. While at it also make all references to the pipe number unsigned because there is no longer any reason why it s

[PATCH 08/13] drm/irq: Check for valid VBLANK before dereference

From: Thierry Reding When accessing the array of per-CRTC VBLANK structures we must always check that the index into the array is valid before dereferencing to avoid crashing. Signed-off-by: Thierry Reding --- drivers/gpu/drm/drm_irq.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(

[PATCH 04/13] drm/imx: Make pipe number unsigned

From: Thierry Reding There's no reason whatsoever why this should ever be negative. Cc: Philipp Zabel Signed-off-by: Thierry Reding --- drivers/gpu/drm/imx/imx-drm-core.c | 4 ++-- drivers/gpu/drm/imx/imx-drm.h | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/driver

[PATCH 13/13] drm/irq: Move some prototypes to drm_crtc.h

From: Thierry Reding The new prototypes that deal with struct drm_crtc * directly are better located in include/drm/drm_crtc.h along with the other functions that deal with CRTCs. Signed-off-by: Thierry Reding --- include/drm/drmP.h | 17 - include/drm/drm_crtc.h | 15 +

[PATCH 01/13] drm/irq: Remove negative CRTC index special-case

From: Thierry Reding The drm_send_vblank_event() function treats negative CRTC indices as meaning that a driver doesn't have proper VBLANK handling. This is the only place where DRM needs negative CRTC indices, so in order to enable subsequent cleanup, remove this special case and replace it by t

Re: [PATCH 0/2] Input: atmel_mxt_ts - Add support for T100 multi-touch

Hello Nick, On 12/16/2014 05:39 PM, Nick Dyer wrote: > On 16/12/14 16:34, Javier Martinez Canillas wrote: >> On 12/16/2014 05:16 PM, Nick Dyer wrote: Nick Dyer (1): Input: atmel_mxt_ts - Implement support for T100 touch object >>> I posted an updated version of this patch on 9th Decemb

Re: [PATCH 0/2] Input: atmel_mxt_ts - Add support for T100 multi-touch

On 16/12/14 16:34, Javier Martinez Canillas wrote: > On 12/16/2014 05:16 PM, Nick Dyer wrote: >>> Nick Dyer (1): >>> Input: atmel_mxt_ts - Implement support for T100 touch object >> I posted an updated version of this patch on 9th December and would prefer >> you apply that rather than this versi

Re: [PATCH 0/2] Input: atmel_mxt_ts - Add support for T100 multi-touch

Hello Nick, On 12/16/2014 05:16 PM, Nick Dyer wrote: > On 15/12/14 10:39, Javier Martinez Canillas wrote: >> There are different multi-touch protocols used by Atmel maXTouch touchscreen >> chips. Old chips use the T9 multi-touch object type while newer chips use the >> T100 multi-touch object type

Re: [PATCH 0/2] Input: atmel_mxt_ts - Add support for T100 multi-touch

On 15/12/14 10:39, Javier Martinez Canillas wrote: > There are different multi-touch protocols used by Atmel maXTouch touchscreen > chips. Old chips use the T9 multi-touch object type while newer chips use the > T100 multi-touch object type. The Atmel touch driver currently only supports > the form

Re: [Linaro-mm-sig] [PATCH v3 18/19] iommu: exynos: init from dt-specific callback instead of initcall

On Tuesday 16 December 2014 14:07:11 Laurent Pinchart wrote: > Hi Arnd, > > On Tuesday 16 December 2014 12:40:28 Arnd Bergmann wrote: > > On Monday 15 December 2014 18:13:23 Will Deacon wrote: > > IOMMUs are not as low-level as system interrupt controllers or > > system clocks. I'm begin

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

On 2014년 12월 11일 01:57, Gustavo Padovan wrote: > From: Daniel Kurtz > > 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 hardware > copi

Re: [PATCH v3 18/19] iommu: exynos: init from dt-specific callback instead of initcall

Hi Arnd, On Tuesday 16 December 2014 12:40:28 Arnd Bergmann wrote: > On Monday 15 December 2014 18:13:23 Will Deacon wrote: > IOMMUs are not as low-level as system interrupt controllers or > system clocks. I'm beginning to agree with Thierry that they should > be treated as normal p

Re: [PATCH v3 18/19] iommu: exynos: init from dt-specific callback instead of initcall

On Monday 15 December 2014 18:13:23 Will Deacon wrote: > > > > IOMMUs are not as low-level as system interrupt controllers or system > > > > clocks. I'm beginning to agree with Thierry that they should be treated > > > > as normal platform devices as they're not required earlier than probe > > > >

Re: [PATCH RFC v3 1/2] PM / Domains: Extend API pm_genpd_dev_need_restore to use restore types

Hello, On 2014-12-13 17:51, Amit Daniel Kachhap wrote: Instead of using bool to restore suspended devices initially, use flags like GPD_DEV_SUSPEND_INIT, GPD_DEV_RESTORE_INIT and GPD_DEV_RESTORE_FORCE. The first two flags will be similar to the existing true/false functionality. The third flag m

Re: [PATCH v3 18/19] iommu: exynos: init from dt-specific callback instead of initcall

Hello, On 2014-12-15 19:19, Laurent Pinchart wrote: On Monday 15 December 2014 18:13:23 Will Deacon wrote: On Mon, Dec 15, 2014 at 05:53:48PM +, Laurent Pinchart wrote: On Monday 15 December 2014 17:43:02 Will Deacon wrote: On Mon, Dec 15, 2014 at 05:27:30PM +, Laurent Pinchart wrote:

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

On pon, 2014-12-15 at 14:26 -0800, Kevin Hilman wrote: > Kevin Hilman writes: > > > Sylwester Nawrocki writes: > > > >> 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.