Re: [RFC 02/15] drivers/base: add restrack framework

2014-12-15 Thread Andrzej Hajda
On 12/12/2014 05:52 PM, Mark Brown wrote: On Wed, Dec 10, 2014 at 04:48:20PM +0100, Andrzej Hajda wrote: restrack framework allows tracking presence of resources with dynamic life time. Typical example of such resources are all resources provided by device I don't know about anyone else but

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

2014-12-15 Thread Thierry Reding
On Sun, Dec 14, 2014 at 02:45:36PM +0200, Laurent Pinchart wrote: Hi Marek, Thank you for the patch. On Wednesday 19 November 2014 12:15:47 Marek Szyprowski wrote: This patch introduces IOMMU_OF_DECLARE-based initialization to the driver, which replaces subsys_initcall-based procedure.

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

2014-12-15 Thread Krzysztof Kozlowski
On pią, 2014-12-12 at 12:42 +0900, Chanwoo Choi wrote: Hi Krzysztof, I replied again this mail because I'll use the mutex for set_event()/get_event() according to your comment. But, of_parse_phandle() seems that this function don't need the of_node_put() function. On 12/11/2014 11:13

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

2014-12-15 Thread Javier Martinez Canillas
Hello Dmitry, 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 former so this series add support for the

[PATCH 1/2] Input: atmel_mxt_ts - Implement support for T100 touch object

2014-12-15 Thread Javier Martinez Canillas
From: Nick Dyer nick.d...@itdev.co.uk The T100 object replaces the old T9 multitouch touchscreen object in new chips. This patch was cherry-picked from the Atmel touch downstream tree The original patch had different initialization functions for the T9 and T100 multi-touch input devices but

[PATCH 2/2] Input: atmel_mxt_ts - Split out touchpad initialisation logic

2014-12-15 Thread Javier Martinez Canillas
From: Sjoerd Simons sjoerd.sim...@collabora.co.uk If the linux,gpio-keymap DT property is defined, the T19 keys are configured and the device is setup as a touchpad rather than a touchscreen. The logic is part of the input device initialization routine but it can be factored out to its own

Re: [RFC 02/15] drivers/base: add restrack framework

2014-12-15 Thread Mark Brown
On Mon, Dec 15, 2014 at 09:28:41AM +0100, Andrzej Hajda wrote: On 12/12/2014 05:52 PM, Mark Brown wrote: On Wed, Dec 10, 2014 at 04:48:20PM +0100, Andrzej Hajda wrote: I don't know about anyone else but I'm having a hard time reading the restrack name, it looks like a misspelling of

Re: [RFC 01/15] drivers/base: add track framework

2014-12-15 Thread Mark Brown
On Sat, Dec 13, 2014 at 12:12:19AM +0100, AH wrote: Mark Brown wrote on 12.12.2014 17:36: On Wed, Dec 10, 2014 at 04:48:19PM +0100, Andrzej Hajda wrote: + kfree(ptask); + + if (empty) + break; + + track_process_task(track, task); ...we

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

2014-12-15 Thread Krzysztof Kozłowski
On 15.12.2014 14:00, 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 keep things

Re: [RFC 01/15] drivers/base: add track framework

2014-12-15 Thread Andrzej Hajda
On 12/15/2014 01:55 PM, Mark Brown wrote: On Sat, Dec 13, 2014 at 12:12:19AM +0100, AH wrote: Mark Brown wrote on 12.12.2014 17:36: On Wed, Dec 10, 2014 at 04:48:19PM +0100, Andrzej Hajda wrote: + kfree(ptask); + + if (empty) + break; + +

Re: [PATCH V8 00/14] drm/exynos: few patches to enhance bridge chip support

2014-12-15 Thread Tomi Valkeinen
On 12/12/14 11:51, Javier Martinez Canillas wrote: Tomi and Laurent, You asked Ajay to change his series to use the video port and enpoints DT bindings instead of phandles, could you please review his latest version? Looking only at the binding documentation patch, looks good to me. Tomi

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

2014-12-15 Thread Krzysztof Kozlowski
On pią, 2014-12-12 at 17:27 +0900, Chanwoo Choi wrote: 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. -

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

2014-12-15 Thread Krzysztof Kozlowski
On pią, 2014-12-12 at 17:27 +0900, Chanwoo Choi wrote: 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 -

[PATCH v2 3/3] ARM: dts: Add devfreq to Exynos3250 and Rinato board

2014-12-15 Thread Krzysztof Kozlowski
Add devfreq to Exynos3250 common file and enable it for Rinato board. Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com --- arch/arm/boot/dts/exynos3250-rinato.dts | 12 arch/arm/boot/dts/exynos3250.dtsi | 26 ++ 2 files changed, 38

[PATCH v2 0/3] devfreq: exynos: Add driver for Exynos3250

2014-12-15 Thread Krzysztof Kozlowski
Hi, Changes since v1 1. Patch 1/3, bindings: fixes after review from Mark Rutland. 2. Patch 2/3, driver: update perf benchmarks. 3. Rebase on Chanwoo's devfreq-event class patches v3 [1]. Description === The aim of patchset is to gather feedback about adding new

[PATCH v2 2/3] devfreq: exynos: Add driver for Exynos3250

2014-12-15 Thread Krzysztof Kozlowski
Add new devfreq driver for Exynos3250. The driver utilizes devfreq event class for bus utilization data is multiplatform safe. Currently it does not support ASV (Adaptive Supply Voltage). Driver creates two devices: - Dynamic Memory Controller (DMC) and memory bus, - peripheral (left/right)

[PATCH v2 1/3] devfreq: dt-bindings: Document bindings for Exynos3250 bus DVFS driver

2014-12-15 Thread Krzysztof Kozlowski
Add documentation for bindings used by Exynos3250 Dynamic Voltage and Frequency Scaling (DVFS) driver. Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com --- .../bindings/arm/samsung/exynos3250-devfreq.txt| 62 ++ 1 file changed, 62 insertions(+) create mode

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

2014-12-15 Thread Mark Brown
On Mon, Dec 15, 2014 at 02:10:37PM +0100, Krzysztof Kozłowski wrote: Hi Mark, Few days ago I posted similar patch: https://lkml.org/lkml/2014/12/5/268 but no one have picked it up. Anyway the fix of yours seems fine to me. I don't mind either way, it just seemed to be easier to report the

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

2014-12-15 Thread Will Deacon
On Mon, Dec 15, 2014 at 03:35:29PM +, Mark Brown wrote: On Mon, Dec 15, 2014 at 02:10:37PM +0100, Krzysztof Kozłowski wrote: Few days ago I posted similar patch: https://lkml.org/lkml/2014/12/5/268 but no one have picked it up. Anyway the fix of yours seems fine to me. I don't

[PATCH] iommu/exynos: Fix arm64 allmodconfig build

2014-12-15 Thread Mark Brown
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 keep things building until either the driver has the ARM

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

2014-12-15 Thread Mark Brown
On Mon, Dec 15, 2014 at 03:38:04PM +, Will Deacon wrote: On Mon, Dec 15, 2014 at 03:35:29PM +, Mark Brown wrote: I don't mind either way, it just seemed to be easier to report the bug with a patch. If Jeorg is busy perhaps it can go via the arm64 tree, the issue is triggered by

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

2014-12-15 Thread Will Deacon
On Sun, Dec 14, 2014 at 12:45:36PM +, Laurent Pinchart wrote: On Wednesday 19 November 2014 12:15:47 Marek Szyprowski wrote: This patch introduces IOMMU_OF_DECLARE-based initialization to the driver, which replaces subsys_initcall-based procedure. exynos_iommu_of_setup ensures that each

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

2014-12-15 Thread Laurent Pinchart
Hi Will, On Monday 15 December 2014 17:17:00 Will Deacon wrote: On Sun, Dec 14, 2014 at 12:45:36PM +, Laurent Pinchart wrote: On Wednesday 19 November 2014 12:15:47 Marek Szyprowski wrote: This patch introduces IOMMU_OF_DECLARE-based initialization to the driver, which replaces

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

2014-12-15 Thread Will Deacon
On Mon, Dec 15, 2014 at 05:27:30PM +, Laurent Pinchart wrote: On Monday 15 December 2014 17:17:00 Will Deacon wrote: On Sun, Dec 14, 2014 at 12:45:36PM +, Laurent Pinchart wrote: On Wednesday 19 November 2014 12:15:47 Marek Szyprowski wrote: +static int __init

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

2014-12-15 Thread Laurent Pinchart
Hi Will, On Monday 15 December 2014 17:43:02 Will Deacon wrote: On Mon, Dec 15, 2014 at 05:27:30PM +, Laurent Pinchart wrote: On Monday 15 December 2014 17:17:00 Will Deacon wrote: On Sun, Dec 14, 2014 at 12:45:36PM +, Laurent Pinchart wrote: On Wednesday 19 November 2014

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

2014-12-15 Thread Will Deacon
On Mon, Dec 15, 2014 at 05:53:48PM +, Laurent Pinchart wrote: Hi Will, Hello again :) On Monday 15 December 2014 17:43:02 Will Deacon wrote: On Mon, Dec 15, 2014 at 05:27:30PM +, Laurent Pinchart wrote: On Monday 15 December 2014 17:17:00 Will Deacon wrote: Creating the

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

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

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

2014-12-15 Thread Kevin Hilman
Kevin Hilman khil...@kernel.org writes: Sylwester Nawrocki s.nawro...@samsung.com 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. On Exynos 5420 if clock for this

Re: [PATCH V8 00/14] drm/exynos: few patches to enhance bridge chip support

2014-12-15 Thread Laurent Pinchart
Hi Javier, On Friday 12 December 2014 10:51:50 Javier Martinez Canillas wrote: Hello, On 11/18/2014 07:20 AM, Ajay kumar wrote: On Sat, Nov 15, 2014 at 3:24 PM, Ajay Kumar wrote: This series is based on master branch of Linus tree at:

Re: [PATCH v3 1/2] serial: samsung: Add support for early console

2014-12-15 Thread Chanwoo Choi
On 10/20/2014 08:28 PM, Marek Szyprowski wrote: From: Tomasz Figa t.f...@samsung.com This patch adds support for early console initialized from device tree and kernel command line to all variants of Samsung serial driver. Signed-off-by: Tomasz Figa t.f...@samsung.com [mszyprow: added

[PATCH] cpufreq: exynos5440: protect call to dev_pm_opp_get_opp_count with RCU lock

2014-12-15 Thread Dmitry Torokhov
dev_pm_opp_get_opp_count() must be called with RCU lock held. Signed-off-by: Dmitry Torokhov d...@chromium.org --- Again, not tested... drivers/cpufreq/exynos5440-cpufreq.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/cpufreq/exynos5440-cpufreq.c

Re: [PATCH v6 1/2] Input: add regulator haptic driver

2014-12-15 Thread Jaewon Kim
Hi Dmitry, 2014년 12월 14일 04:56에 Dmitry Torokhov 이(가) 쓴 글: Hi Jaewon, On Fri, Dec 12, 2014 at 07:32:28PM +0900, Jaewon Kim wrote: This patch adds support for haptic driver controlled by voltage of regulator. And this driver support for Force Feedback interface from input framework

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

2014-12-15 Thread Chanwoo Choi
Hi Krzysztof, On 12/15/2014 11:53 PM, Krzysztof Kozlowski wrote: On pią, 2014-12-12 at 17:27 +0900, Chanwoo Choi wrote: 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

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

2014-12-15 Thread Chanwoo Choi
Hi Krzysztof, On 12/15/2014 11:53 PM, Krzysztof Kozlowski wrote: On pią, 2014-12-12 at 17:27 +0900, Chanwoo Choi wrote: 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

Re: [PATCH v6 1/2] Input: add regulator haptic driver

2014-12-15 Thread Dmitry Torokhov
On Tue, Dec 16, 2014 at 10:09:25AM +0900, Jaewon Kim wrote: Hi Dmitry, 2014년 12월 14일 04:56에 Dmitry Torokhov 이(가) 쓴 글: Hi Jaewon, On Fri, Dec 12, 2014 at 07:32:28PM +0900, Jaewon Kim wrote: ... +static int __maybe_unused regulator_haptic_suspend(struct device *dev) +{ + struct

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

2014-12-15 Thread Chanwoo Choi
Hi Krzysztof, On 12/15/2014 07:30 PM, Krzysztof Kozlowski wrote: On pią, 2014-12-12 at 12:42 +0900, Chanwoo Choi wrote: Hi Krzysztof, I replied again this mail because I'll use the mutex for set_event()/get_event() according to your comment. But, of_parse_phandle() seems that this function

Re: [alsa-devel] [PATCH/RFC 00/14] ASoC: samsung: Add clk provider for I2S internal clocks

2014-12-15 Thread Padma Venkat
Hi Sylwester, I need some more thought about interaction between the clk API calls on the clocks being exposed and the ASoC calls into sound/soc/samsung/i2s.c. I'm sending teh patches for review though to avoid any waste of time should it turn out the direction taken is wrong. This whole