Re: [PATCH v2 1/7] drm/exynos: add super device support

2014-04-08 Thread Inki Dae
2014-04-08 0:40 GMT+09:00, Tomasz Figa tomasz.f...@gmail.com: On 07.04.2014 17:16, Inki Dae wrote: Hi Andrzej, 2014-04-07 23:18 GMT+09:00 Andrzej Hajda a.ha...@samsung.com: Hi Inki and Tomasz, On 04/06/2014 05:15 AM, Inki Dae wrote: (...) The code creating the list of components to wait

Re: [PATCH V2 17/17] ARM: exynos: config: Enable cpuidle

2014-04-08 Thread Bartlomiej Zolnierkiewicz
On Monday, April 07, 2014 11:33:57 AM Olof Johansson wrote: On Mon, Apr 7, 2014 at 10:44 AM, Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com wrote: Hi, On Monday, April 07, 2014 09:28:39 AM Olof Johansson wrote: On Fri, Apr 4, 2014 at 9:09 AM, Bartlomiej Zolnierkiewicz

Re: [PATCH v11 0/4] thermal: samsung: Clean up and add support for Exynos5420

2014-04-08 Thread Javi Merino
On Thu, Mar 20, 2014 at 02:45:54AM +, Naveen Krishna Ch wrote: Hello Tomasz, On 20 March 2014 00:58, Tomasz Figa t.f...@samsung.com wrote: Hi Leela, On 19.03.2014 12:19, Leela Krishna Amudala wrote: Hi All, I didn't see this series in mainline, Any comments for this ?

Re: [PATCH V2 17/17] ARM: exynos: config: Enable cpuidle

2014-04-08 Thread Bartlomiej Zolnierkiewicz
On Tuesday, April 08, 2014 09:27:04 AM Sachin Kamat wrote: On 8 April 2014 00:03, Olof Johansson o...@lixom.net wrote: On Mon, Apr 7, 2014 at 10:44 AM, Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com wrote: Hi, On Monday, April 07, 2014 09:28:39 AM Olof Johansson wrote: On Fri,

[PATCH] video: exynos: Add a dependency to the menu

2014-04-08 Thread Jean Delvare
All drivers under menu EXYNOS_VIDEO depend on either ARCH_S5PV210 or ARCH_EXYNOS, so add these as dependencies to the menu itself. This avoids presenting an empty and useless menu on other architectures. Then drivers under the menu only need a dependency if they depend on one of the supported

[PATCH V3 03/17] ARM: exynos: cpuidle: change function name prefix

2014-04-08 Thread Daniel Lezcano
The driver was initially written for exynos4 but the driver is used also for exynos5. Change the function prefix name exynos4 - exynos Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar viresh.ku...@linaro.org Reviewed-by: Bartlomiej Zolnierkiewicz

[PATCH V3 00/17] ARM: exynos: cpuidle: Move the driver to drivers/cpuidle

2014-04-08 Thread Daniel Lezcano
Changelog: V3: * Added patch : ARM: exynos: cpuidle: Disable cpuidle for 5440 * Removed patch : ARM: exynos: config: Enable cpuidle * Removed default ARM_EXYNOS4210_CPUIDLE=y * Added comment about bug fix side effect 'for_each_possible_cpu' V2: * Added

[PATCH V3 01/17] ARM: exynos: cpuidle: Prevent forward declaration

2014-04-08 Thread Daniel Lezcano
Move the structure below the 'exynos4_enter_lowpower' function so no more need of forward declaration. Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar viresh.ku...@linaro.org Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com ---

[PATCH V3 02/17] ARM: exynos: cpuidle: use cpuidle_register

2014-04-08 Thread Daniel Lezcano
Use the cpuidle generic function 'cpuidle_register'. That saves us from some extra lines of code and unneeded variables. A side effect of this change is a bug fix where before the cpuidle driver was registered for each_online_cpu and now it is for each_possible_cpu. Signed-off-by: Daniel Lezcano

[PATCH V3 08/17] ARM: exynos: cpuidle: Move scu_enable in the cpu_pm notifier

2014-04-08 Thread Daniel Lezcano
We make the cpuidle code less arch dependent. Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar viresh.ku...@linaro.org Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com --- arch/arm/mach-exynos/cpuidle.c |6 -- arch/arm/mach-exynos/pm.c

[PATCH V3 07/17] ARM: exynos: cpuidle: Use the cpu_pm notifier

2014-04-08 Thread Daniel Lezcano
Use the cpu_pm_enter/exit notifier to group some pm code inside the pm file. The save and restore code is duplicated across pm.c and cpuidle.c. By using the cpu_pm notifier, we can factor out the routine. Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar

[PATCH V3 06/17] ARM: exynos: cpuidle: Fix S5P_WAKEUP_STAT call

2014-04-08 Thread Daniel Lezcano
This function should be called only when the powerdown sequence fails. Even if the current code does not hurt, by moving this line, we have the same code than the one in pm.c. Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar viresh.ku...@linaro.org Reviewed-by:

[PATCH V3 04/17] ARM: exynos: cpuidle: encapsulate register access inside a function

2014-04-08 Thread Daniel Lezcano
That makes the code cleaner and encapsulted. The function will be reused in the next patch. Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar viresh.ku...@linaro.org Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com --- arch/arm/mach-exynos/pm.c |

[PATCH V3 13/17] ARM: exynos: cpuidle: Move clock setup to pm.c

2014-04-08 Thread Daniel Lezcano
One more step is moving the clock ratio setting at idle time in pm.c The macro names have been changed to be consistent with the other macros name in the file. Note, the clock divider was working only when cpuidle was enabled because it was in its init routine. With this change, the clock

[PATCH V3 15/17] ARM: exynos: cpuidle: Disable cpuidle for 5440

2014-04-08 Thread Daniel Lezcano
There is no point to register the cpuidle driver for the 5440 as it has only one WFI state which is the default idle function when the cpuidle driver is disabled. By disabling cpuidle we prevent to enter to the governor computation for nothing, thus saving a lot of processing time. The only

[PATCH V3 17/17] ARM: exynos: cpuidle: Move the driver to drivers/cpuidle directory

2014-04-08 Thread Daniel Lezcano
Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar viresh.ku...@linaro.org Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com --- arch/arm/mach-exynos/Makefile |1 - drivers/cpuidle/Kconfig.arm|6

[PATCH V3 05/17] ARM: exynos: cpuidle: Move some code inside the idle_finisher

2014-04-08 Thread Daniel Lezcano
Move the code around to differentiate different section of code and prepare it to be factored out in the next patches. The call order changed but hat doesn't have a side effect because they are independent. The important call is cpu_do_idle() which must be done the last. Signed-off-by: Daniel

[PATCH V3 09/17] ARM: exynos: cpuidle: Remove ifdef for scu_enable

2014-04-08 Thread Daniel Lezcano
The scu_enable function is already a noop in the scu's header file is CONFIG_SMP=n, so no need to use these macros in the code. Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar viresh.ku...@linaro.org Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com

[PATCH V3 12/17] ARM: exynos: cpuidle: Move S5P_CHECK_AFTR in a header

2014-04-08 Thread Daniel Lezcano
Move the S5P_CHECK_AFTR definition to the header it belongs to. Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar viresh.ku...@linaro.org Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com --- arch/arm/mach-exynos/cpuidle.c |2 --

[PATCH V3 11/17] ARM: exynos: cpuidle: Move the power sequence call in the cpu_pm notifier

2014-04-08 Thread Daniel Lezcano
The code to initiate and exit the powerdown sequence is the same in pm.c and cpuidle.c. Let's split the common part in the pm.c and reuse it from the cpu_pm notifier. That is one more step forward to make the cpuidle driver arch indenpendant. Signed-off-by: Daniel Lezcano

[PATCH V3 10/17] ARM: exynos: cpuidle: Move exynos_set_wakeupmask in the cpu_pm notifier

2014-04-08 Thread Daniel Lezcano
Let's encapsulate more the PM code inside the PM file by moving the 'exynos_set_wakeupmask' function inside the pm.c and the call in the cpu_pm notifier. Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org Reviewed-by: Viresh Kumar viresh.ku...@linaro.org Reviewed-by: Bartlomiej

Re: AFTR does not work on arndale 5250

2014-04-08 Thread Vikas Sajjan
Hi Daniel, I checked AFTR on v3.14 ( https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs/tags/v3.14) on exynos5250 based chromebook (exynos5250-snow.dtb) I am able to hotplug CPU1 (echo 0 /sys/devices/system/cpu/cpu1/online). I can see, it enters

Re: AFTR does not work on arndale 5250

2014-04-08 Thread Chander Kashyap
Hi Daniel, I have tested on v3.14 Stable on arndale board. I have tested wit cramfs. Last commit on tree is: 01d5f3b598b18a5035426c30801adf65822dbd0c Below are the logs from the console. $ uname -a Linux (none) 3.14.0-00604-g0c6d388 #28 SMP PREEMPT Tue Apr 8 19:19:09 IST 2014 armv7l unknown $

Re: AFTR does not work on arndale 5250

2014-04-08 Thread Daniel Lezcano
On 04/08/2014 03:32 PM, Vikas Sajjan wrote: Hi Daniel, I checked AFTR on v3.14 ( https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs/tags/v3.14) on exynos5250 based chromebook (exynos5250-snow.dtb) I am able to hotplug CPU1 (echo 0

[PATCH V4 0/5] Add Exynos5 USB 3.0 phy driver based on generic PHY framework

2014-04-08 Thread Vivek Gautam
Based on 'next' branch of Kishon's phy tree (linux-phy). Tested on 'usb-next' of Greg's usb tree. Changes from V3: 1) Separated out the phy init sequences for utmi and pipe3 phys. 2) Changed the nomenclature across the phy to 'usbdrd-phy' to indicate USB 3.0 DRD PHY controller; and thereby

[PATCHv2 3/3] s5p-tv: hdmi: use hdmiphy as PHY

2014-04-08 Thread Tomasz Stanislawski
The HDMIPHY (physical interface) is controlled by a single bit in a power controller's regiter. It was implemented as clock. It was a simple but effective hack. This patch makes S5P-HDMI driver to control HDMIPHY via PHY interface. Signed-off-by: Tomasz Stanislawski t.stanisl...@samsung.com ---

[PATCHv2 2/3] drm: exynos: hdmi: use hdmiphy as PHY

2014-04-08 Thread Tomasz Stanislawski
The HDMIPHY (physical interface) is controlled by a single bit in a power controller's regiter. It was implemented as clock. It was a simple but effective hack. This patch makes HDMI driver to control HDMIPHY via PHY interface. Signed-off-by: Tomasz Stanislawski t.stanisl...@samsung.com ---

[PATCHv2 1/3] phy: Add exynos-simple-phy driver

2014-04-08 Thread Tomasz Stanislawski
Add exynos-simple-phy driver to support a single register PHY interfaces present on Exynos4 SoC. Signed-off-by: Tomasz Stanislawski t.stanisl...@samsung.com --- .../devicetree/bindings/phy/samsung-phy.txt| 24 +++ drivers/phy/Kconfig|5 +

[PATCH V4 5/5] usb-phy: samsung-usb3: Remove older phy-samsung-usb3 driver

2014-04-08 Thread Vivek Gautam
Removing this older USB 3.0 DRD controller PHY driver, since a new driver based on generic phy framework is now available. Also removing the dt node for older driver from Exynos5250 device tree and updating the dt node for DWC3 controller. Signed-off-by: Vivek Gautam gautam.vi...@samsung.com ---

[PATCH V4 3/5] dt: exynos5420: Enable support for DWC3 controller

2014-04-08 Thread Vivek Gautam
Add device tree nodes for DWC3 controller present on Exynos 5420 SoC, to enable support for USB 3.0. Signed-off-by: Vivek Gautam gautam.vi...@samsung.com --- arch/arm/boot/dts/exynos5420.dtsi | 34 ++ 1 file changed, 34 insertions(+) diff --git

[PATCH V4 1/5] phy: Add new Exynos5 USB 3.0 PHY driver

2014-04-08 Thread Vivek Gautam
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs. The new driver uses the generic PHY framework and will interact with DWC3 controller present on Exynos5 series of SoCs. Thereby, removing old phy-samsung-usb3 driver and related code used untill now which was based on usb/phy

[PATCHv2 0/3] phy: Add exynos-simple-phy driver

2014-04-08 Thread Tomasz Stanislawski
Hello everyone, The Samsung SoCs from Exynos family are enhanced with a bunch of devices that provide functionality of a physical layer for interfaces like USB, HDMI, SATA, etc. They are controlled by a simple interface, often a single bit that enables and/or resets the physical layer. An IP

Re: [PATCH 1/4] clk: propagate parent change up one level

2014-04-08 Thread Tomasz Figa
Hi, On 04.04.2014 16:53, Tomasz Stanislawski wrote: This patch adds support for propagation of setup of clock's parent one level up. This feature is helpful when a driver changes topology of its clocks using clk_set_parent(). The problem occurs when on one platform/SoC driver's clock is

Re: [PATCH 3/4] clk: exynos4: enable clk_set_parent() propagation for sclk_hdmi and sclk_mixer clocks

2014-04-08 Thread Tomasz Figa
On 04.04.2014 16:53, Tomasz Stanislawski wrote: This patch enables clk_set_parent() propagation for clocks used by s5p-tv and exynos-drm drivers. Signed-off-by: Tomasz Stanislawski t.stanisl...@samsung.com --- drivers/clk/samsung/clk-exynos4.c |6 -- 1 file changed, 4 insertions(+),

Re: [PATCH 4/4] Revert drm/exynos: add mout_hdmi clock in hdmi driver to change parent

2014-04-08 Thread Tomasz Figa
Hi Tomasz, On 04.04.2014 16:53, Tomasz Stanislawski wrote: This reverts commit 59956d35a8618235ea715280b49447bb36f2c975. Probably a reason why this commit is being reverted would be a good idea. Signed-off-by: Tomasz Stanislawski t.stanisl...@samsung.com ---

Re: [PATCH 01/10] ARM: EXYNOS: Cleanup mach-exynos/common.h file

2014-04-08 Thread Tomasz Figa
Hi Pankaj, On 02.04.2014 09:50, Pankaj Dubey wrote: Remove unused declarations from mach-exynos/common.h Signed-off-by: Pankaj Dubey pankaj.du...@samsung.com --- arch/arm/mach-exynos/common.h |3 --- 1 file changed, 3 deletions(-) diff --git a/arch/arm/mach-exynos/common.h

Re: [PATCH 05/10] ARM: EXYNOS: Move regs-pmu header inclusion in common.h

2014-04-08 Thread Tomasz Figa
Hi Pankaj, On 02.04.2014 09:50, Pankaj Dubey wrote: There are many machine files under mach-exynos including regs-pmu.h as well as common.h, so better we move this header inclusion in common.h. Signed-off-by: Pankaj Dubey pankaj.du...@samsung.com --- arch/arm/mach-exynos/common.h |1 +

[PATCH] arm: exynos: generalize power register address calculation

2014-04-08 Thread Chander Kashyap
Currently status/configuration power register values are hard-coded for cpu1. Make it generic so that it is useful for SoC's with more than two cpus. Signed-off-by: Chander Kashyap chander.kash...@linaro.org --- arch/arm/mach-exynos/hotplug.c | 10 +++--- arch/arm/mach-exynos/platsmp.c

Re: [PATCH V3 15/17] ARM: exynos: cpuidle: Disable cpuidle for 5440

2014-04-08 Thread Nicolas Pitre
On Tue, 8 Apr 2014, Daniel Lezcano wrote: On 04/08/2014 02:51 PM, Amit Kucheria wrote: On Tue, Apr 8, 2014 at 5:49 PM, Daniel Lezcano daniel.lezc...@linaro.org mailto:daniel.lezc...@linaro.org wrote: There is no point to register the cpuidle driver for the 5440 as it has only

Re: [PATCH RESEND] usb: ohci-exynos: Remove locks for 'ohci' in suspend callback

2014-04-08 Thread Jingoo Han
On Tuesday, April 08, 2014 11:41 PM, Vivek Gautam wrote: Patch : 14982e3 USB: OHCI: Properly handle ohci-exynos suspend has already removed 'ohci_hcd' settings from exynos glue layer as a part of streamlining the ohci controller's suspend. So we don't need the locks for 'ohci_hcd' anymore.

[PATCH 1/2] usb: ehci-exynos: Return immediately from suspend if ehci_suspend fails

2014-04-08 Thread Vivek Gautam
Patch 'b8efdaf USB: EHCI: add check for wakeup/suspend race' adds a check for possible race between suspend and wakeup interrupt, and thereby it returns -EBUSY as error code if there's a wakeup interrupt. So the platform host controller should not proceed further with its suspend callback, rather

[PATCH 2/2] usb: ehci-platform: Return immediately from suspend if ehci_suspend fails

2014-04-08 Thread Vivek Gautam
Patch 'b8efdaf USB: EHCI: add check for wakeup/suspend race' adds a check for possible race between suspend and wakeup interrupt, and thereby it returns -EBUSY as error code if there's a wakeup interrupt. So the platform host controller should not proceed further with its suspend callback, rather

Re: [PATCH 1/2] usb: ehci-exynos: Return immediately from suspend if ehci_suspend fails

2014-04-08 Thread Jingoo Han
On Wednesday, April 09, 2014 1:01 PM, Vivek Gautam wrote: Patch 'b8efdaf USB: EHCI: add check for wakeup/suspend race' adds a check for possible race between suspend and wakeup interrupt, and thereby it returns -EBUSY as error code if there's a wakeup interrupt. So the platform host