Re: [RFT 0/3] usb: usb3503: Fix probing on Arndale board (missing phy)

Hi Krzystof, Krzysztof Kozlowski writes: > Introduction > > This patchset tries to fix probing of usb3503 on Arndale board > if the Samsung PHY driver is probed later (or built as a module). > > *The patchset was not tested on Arndale board.* > I don't have

Re: [PATCH] ARM: EXYNOS: reset KFC cores when cpu is up

Abhilash Kesavan writes: > On Tue, Sep 1, 2015 at 5:51 AM, Krzysztof Kozlowski > wrote: >> On 01.09.2015 07:46, Javier Martinez Canillas wrote: [...] >>> I posted a similar patch that instead disabling CCI for the XU3 board, >>> it disables

Re: [PATCH] ARM: EXYNOS: reset KFC cores when cpu is up

nux-arm-kernel/2015-July/356610.html > > Cc: Joonyoung Shim <jy0922.s...@samsung.com> > Cc: Chanwoo Choi <cw00.c...@samsung.com> > Cc: Kevin Hilman <khil...@kernel.org> > Cc: Heesub Shin <heesub.s...@samsung.com> > Cc: Mauro Ribeiro <mauro.ribe...@hardkernel.com> &

Re: [PATCH] Documentation: ARM: EXYNOS: Describe boot loaders interface

Krzysztof Kozlowski k.kozlowsk...@gmail.com writes: Various boot loaders for Exynos based boards use certain memory addresses during booting for different purposes. Mostly this is one of following : 1. as a CPU boot address, 2. for storing magic cookie related to low power mode (AFTR,

Re: [RFC] ARM: exynos: MCPM: [is this a] fix for secondary boot on 5422?

Krzysztof Kozłowski k.kozlowsk...@gmail.com writes: 2014-11-25 15:21 GMT+09:00 Kevin Hilman khil...@kernel.org: From: Kevin Hilman khil...@linaro.org Using the current exynos_defconfig on the exynos5422-odroid-xu3, only 6 of 8 CPUs come online with MCPM boot. CPU0 is an A7, CPUs 1-4

Re: [RFC] ARM: exynos: MCPM: [is this a] fix for secondary boot on 5422?

Przemyslaw Marczak p.marc...@samsung.com writes: On 06/15/2015 01:19 PM, Amit Kucheria wrote: On Mon, Jun 15, 2015 at 3:49 PM, Przemyslaw Marczak p.marc...@samsung.com wrote: Hello Krzysztof, On 06/14/2015 10:56 AM, Krzysztof Kozłowski wrote: snip I'm trying port the hardkernel's SPL

Re: [GIT PULL 4/5] Samsung another DT updates for v4.2

Kukjin Kim kg...@kernel.org writes: Hi, Here is another Samsung DT updates for v4.2 but this is based on v4.1-rc6 + previous tags/samsung-dt-3 because this touches all of exynos DT stuff and some fixes have been merged until -rc6... In the future, it would be helpful to describe what fixes

Re: [GIT PULL 5/5] Samsung mach updates for v4.2

Kukjin Kim kg...@kernel.org writes: Hi, Here is Samsung mach updates for v4.2 and this is based on v4.1-rc4 because of dependencies with previous Samsung fixes during -rc Please pull and if any problems, please let me know. Thanks, Kukjin The following changes since commit

Re: [GIT PULL 5/5] Samsung mach updates for v4.2

Kukjin Kim kg...@kernel.org writes: Hi, Here is Samsung mach updates for v4.2 and this is based on v4.1-rc4 because of dependencies with previous Samsung fixes during -rc Please pull and if any problems, please let me know. Thanks, Kukjin The following changes since commit

Re: [GIT PULL 2/5] Samsung 2nd defconfig for v4.2

Kukjin Kim kg...@kernel.org writes: Hi, Here is 2nd defconfig updates for v4.2 but actually just one patch for Samsung updates for multi_v7_defconfig. Please pull or apply the patch directly, anyway I'm fine either way. Note that this is based on arm-soc/next/defconfig to avoid useless

Re: [GIT PULL 3/5] Samsung DT updates for v4.2

Kukjin Kim kg...@kernel.org writes: The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031: Linux 4.1-rc1 (2015-04-26 17:59:10 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git tags/samsung-dt-3

Re: [PATCH v2] MAINTAINERS: ARM64: EXYNOS: Extend entry for ARM64 DTS

...@kernel.org Cc: Kevin Hilman khil...@kernel.org Cc: Arnd Bergmann a...@arndb.de Cc: Olof Johansson o...@lixom.net Cc: linux-samsung-soc@vger.kernel.org Cc: linux-arm-ker...@lists.infradead.org Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com Reviewed-by: Javier Martinez Canillas

Re: [PATCH v2] MAINTAINERS: ARM64: EXYNOS: Extend entry for ARM64 DTS

On Thu, Jun 11, 2015 at 4:35 PM, Krzysztof Kozlowski k.kozlow...@samsung.com wrote: W dniu 12.06.2015 o 06:48, Kevin Hilman pisze: Hi Krzysztof, On Sat, Jun 6, 2015 at 3:02 AM, Krzysztof Kozlowski k.kozlow...@samsung.com wrote: Extend the Exynos entry to ARM64 device tree sources. Cc

Re: [PATCH] ARM: multi_v7_defconfig: enable usb3503

Javier Martinez Canillas javier.marti...@collabora.co.uk writes: Hello Kevin, On 06/04/2015 03:08 AM, Kevin Hilman wrote: riku.voi...@linaro.org writes: From: Riku Voipio riku.voi...@linaro.org CONFIG_USB_HSIC_USB3503 is needed by exynos5250-arndale for the on-board asix network

Re: [PATCH] ARM: multi_v7_defconfig: enable usb3503

riku.voi...@linaro.org writes: From: Riku Voipio riku.voi...@linaro.org CONFIG_USB_HSIC_USB3503 is needed by exynos5250-arndale for the on-board asix network controller. Enable it so networking works with multi_v7_defconfig out of box like it does with exynos_defconfig. USB3503 is also

Re: [PATCH] ARM: dts: add exynos5422.dtsi to correct cpu order

Marek Szyprowski m.szyprow...@samsung.com writes: Hello, On 2015-05-28 06:00, Chanho Park wrote: -Original Message- From: Joonyoung Shim [mailto:jy0922.s...@samsung.com] Sent: Thursday, May 28, 2015 10:59 AM To: Chanho Park; kg...@kernel.org; k.kozlow...@samsung.com Cc:

Re: [PATCH 2/2] ARM: dts: Fix pinctrl settings for S2MPS11 RTC alarm IRQ on Arndale Octa

Hi Krzystof, Krzysztof Kozlowski k.kozlow...@samsung.com writes: 2015-04-02 23:36 GMT+09:00 Krzysztof Kozlowski k.kozlow...@samsung.com: On Arndale Octa the S2MPS11 RTC alarm interrupt was not handled at all because of wrong configuration of interrupt and gpx3-2. 1. Interrupt is signaled by

Re: [RFT PATCH] drm/exynos: Enable DP clock to fix display on Exynos5250 and other

Krzysztof Kozlowski k.kozlow...@samsung.com writes: After adding display power domain for Exynos5250 in commit 2d2c9a8d0a4f (ARM: dts: add display power domain for exynos5250) the display on Chromebook Snow and others stopped working after boot. The reason for this suggested Andrzej Hajda:

Re: [PATCH 0/4] cpufreq: use generic cpufreq drivers for Exynos5250 platform

Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com writes: [...] However, with the default governor set to userspace it boots fine until my userspace (ubuntu) tries to enable the ondemand governor, and then it hangs. For it to boot, I have to disable the ondemand governor, and set the

Re: [PATCH 0/4] cpufreq: use generic cpufreq drivers for Exynos5250 platform

Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com writes: On Monday, April 20, 2015 02:07:33 PM Kevin Hilman wrote: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com writes: Hi, This patch series removes the use of Exynos5250 specific support from exynos-cpufreq driver and enables

Re: [PATCH 0/4] cpufreq: use generic cpufreq drivers for Exynos5250 platform

Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com writes: Hi, This patch series removes the use of Exynos5250 specific support from exynos-cpufreq driver and enables the use of cpufreq-dt driver for this platform. The exynos-cpufreq driver itself is also removed as it is no longer

Re: [RFC PATCH v3 2/2] clk: exynos5420: Make sure MDMA0 clock is enabled during suspend

Martinez Canillas javier.marti...@collabora.co.uk Tested-by: Kevin Hilman khil...@linaro.org on exynos5800-peach-pi Kevin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http

Re: [RFC PATCH v3 2/2] clk: exynos5420: Make sure MDMA0 clock is enabled during suspend

Abhilash Kesavan kesavan.abhil...@gmail.com writes: On Wed, Apr 1, 2015 at 2:32 AM, Kevin Hilman khil...@kernel.org wrote: Javier Martinez Canillas javier.marti...@collabora.co.uk writes: [...] Unfortunately I don't fully understand why this clock needs to be enabled. It would be good

Re: [RFC PATCH v3 2/2] clk: exynos5420: Make sure MDMA0 clock is enabled during suspend

Javier Martinez Canillas javier.marti...@collabora.co.uk writes: [...] Unfortunately I don't fully understand why this clock needs to be enabled. It would be good if someone at Samsung can explain in more detail what the real problem really is. +1 Maybe Abhilash can shed some light here?

exynos5800-peach-pi: suspend/resume (still) broken

I've tried suspend/resume on peach-pi using v4.0-rc4, next/master and samsung/for-next, and it doesn't seem to work on any of them. The first problem was the exynos DRM driver is faulting so I had to set CONFIG_\ DRM_EXYNOS=n for testing in mainline, this is fixed in -next. Note that RTC wake

Re: [PATCH v2] ARM: EXYNOS: Use platform device name as power domain name

javier.marti...@collabora.co.uk Suggested-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk Reviewed-by: Kevin Hilman khil...@linaro.org I still think we need some more detail as wel, but this is a good step in the right

Re: [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support

Javier Martinez Canillas javier.marti...@collabora.co.uk writes: +Gustavo which has been looking at the issues Hello, On 03/04/2015 09:50 AM, Marek Szyprowski wrote: Hello, On 2015-03-03 21:36, Kevin Hilman wrote: Javier Martinez Canillas javier.marti...@collabora.co.uk writes

Re: [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support

Javier Martinez Canillas javier.marti...@collabora.co.uk writes: Enabling Exynos DRM IOMMU support for Exynos is currently broken and causes a BUG on exynos-iommu driver. This was not an issue since the options was disabled in exynos_defconfig but after commit 8dcc14f82f06 (drm/exynos: IOMMU

[PATCH v3] ARM: dts: exynos5422-odroidxu3: add on-board INA231 sensors

From: Kevin Hilman khil...@linaro.org The odroid-xu3 has 4 INA231 current sensors on board which can be accessed from the Linux via the hwmon interface. There is one sensor for each of these power rails: - A15 cluster: VDD_ARM - A7 cluster: VDD_KFC - GPU: VDD_G3D - memory: VDD_MEM In addition

Re: [PATCH v2] ARM: dts: exynos5422-odroidxu3: add on-board INA231 sensors

Joonyoung Shim jy0922.s...@samsung.com writes: Hi Kevin, On 01/15/2015 10:08 AM, Kevin Hilman wrote: From: Kevin Hilman khil...@linaro.org The odroid-xu3 has 4 INA231 current sensors on board which can be accessed from the Linux via the hwmon interface. There is one sensor for each

Re: [PATCH] ARM: dts: exynos5422-odroidxu3: add INA2xx sensors

Kukjin Kim kg...@kernel.org writes: On 01/14/15 09:03, Kevin Hilman wrote: From: Kevin Hilman khil...@linaro.org The odroid-xu3 has 4 INA231 current sensors on board which can be accessed from the Linux via the hwmon interface. There is one sensor for each of these power rails: - A15

Re: [PATCH] hwmon: (ina2xx) Add ina231 compatible string

Guenter Roeck li...@roeck-us.net writes: On Wed, Jan 14, 2015 at 03:57:32PM -0800, Kevin Hilman wrote: From: Kevin Hilman khil...@linaro.org Add support for ina231 as compatible string. Tested with the Exynos5422-based odroid-xu3 board which has on-board INA231 sensors. Signed-off

[PATCH v2] hwmon: (ina2xx) Add ina231 compatible string

From: Kevin Hilman khil...@linaro.org Add support for ina231 as compatible string, and update Documentation and Kconfig accordingly. Tested with the Exynos5422-based odroid-xu3 board which has on-board INA231 sensors. Signed-off-by: Kevin Hilman khil...@linaro.org --- Documentation/hwmon

Re: [PATCH] ARM: dts: exynos5422-odroidxu3: add INA2xx sensors

Sjoerd Simons sjoerd.sim...@collabora.co.uk writes: Hey kevin, On Tue, 2015-01-13 at 16:03 -0800, Kevin Hilman wrote: From: Kevin Hilman khil...@linaro.org The odroid-xu3 has 4 INA231 current sensors on board which can be accessed from the Linux via the hwmon interface. There is one

[PATCH] hwmon: (ina2xx) Add ina231 compatible string

From: Kevin Hilman khil...@linaro.org Add support for ina231 as compatible string. Tested with the Exynos5422-based odroid-xu3 board which has on-board INA231 sensors. Signed-off-by: Kevin Hilman khil...@linaro.org --- drivers/hwmon/ina2xx.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2] ARM: dts: exynos5422-odroidxu3: add on-board INA231 sensors

From: Kevin Hilman khil...@linaro.org The odroid-xu3 has 4 INA231 current sensors on board which can be accessed from the Linux via the hwmon interface. There is one sensor for each of these power rails: - A15 cluster: VDD_ARM - A7 cluster: VDD_KFC - GPU: VDD_G3D - memory: VDD_MEM In addition

Re: [RFC v2 0/4] Add basic support for ASV

On Tue, Dec 3, 2013 at 10:00 PM, Sachin Kamat sachin.ka...@linaro.org wrote: Hi Abhilash, On 3 December 2013 20:16, Abhilash Kesavan kesavan.abhil...@gmail.com wrote: Hi Yadwinder and Sachin, CC'ing Doug and Andrew who have also worked on ASV. I tested these patches on a 5250 Chromebook

[PATCH] ARM: dts: exynos5422-odroidxu3: add INA2xx sensors

From: Kevin Hilman khil...@linaro.org The odroid-xu3 has 4 INA231 current sensors on board which can be accessed from the Linux via the hwmon interface. There is one sensor for each of these power rails: - A15 cluster: VDD_ARM - A7 cluster: VDD_KFC - GPU: VDD_G3D - memory: VDD_MEM In addition

Re: [PATCH v3] ARM: dts: Add dts file for odroid XU3 board

-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk Boot tested on top of next-20150109 (with and without my hack for bringing up 8 cores.) Tested-by: Kevin Hilman khil...@linaro.org Kevin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord

Re: [PATCH v2] ARM: dts: Add dts file for odroid XU3 board

Sjoerd Simons sjoerd.sim...@collabora.co.uk writes: On Wed, 2015-01-07 at 23:49 +, Jonathan Stone -SISA wrote: On On Wed, 2015-01-07 at 18:37 +, Sjoerd Simons writes wrote: On Wed, 2015-01-07 at 18:37 +, Anand Moon wrote: [...] Only 4 core cpu's are on my board. Also CpuFreq

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

who is supposed to pick this up. So far, most of the CCI patches are merged through arm-soc. Would you be OK picking this up as is or do you want me to re-send this with the RFT tag dropped ? Please resend without the RFT, and collect the Tested-by tags you can add mine: Tested-by: Kevin

Re: [PATCH 4/4] PM: Eliminate CONFIG_PM_RUNTIME

into a user-selectable option and drop the former entirely from the tree. Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com Reviewed-by: Ulf Hansson ulf.hans...@linaro.org Acked-by: Kevin Hilman khil...@linaro.org I assume you're planning to get this in early in the v3.19-rc cycle

Re: Enable runtime PM automatically?

Geert Uytterhoeven ge...@linux-m68k.org writes: [...] On Thu, Dec 18, 2014 at 10:29 PM, Kevin Hilman khil...@kernel.org wrote: However, if PM domains are active, drivers must be runtime PM-aware for the gpd_dev_ops.start() method to be called in the first place (perhaps this is just one

Re: Enable runtime PM automatically?

Geert Uytterhoeven ge...@linux-m68k.org writes: On Tue, Dec 16, 2014 at 11:10 PM, Kevin Hilman khil...@kernel.org wrote: At a deeper level, the problem with this approach is that this is more generically a runtime PM dependency problem, not a genpd problem. For example, what happens when

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

On Wed, Dec 17, 2014 at 10:58 PM, Mike Turquette mturque...@linaro.org wrote: Quoting Mike Turquette (2014-12-17 07:23:22) Quoting Krzysztof Kozlowski (2014-12-16 00:20:15) On pon, 2014-12-15 at 14:26 -0800, Kevin Hilman wrote: Kevin Hilman khil...@kernel.org writes: Sylwester

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

amit daniel kachhap amit.dan...@samsung.com writes: On Wed, Dec 17, 2014 at 3:40 AM, Kevin Hilman khil...@kernel.org wrote: Marek Szyprowski m.szyprow...@samsung.com writes: Hello, On 2014-12-13 17:51, Amit Daniel Kachhap wrote: Instead of using bool to restore suspended devices initially

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

Marek Szyprowski m.szyprow...@samsung.com 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

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

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

Re: [PATCH v4 0/3] Fix Arndale Octa/Peach Pi boot on Audio subsystem clocks

and exynos5420-arndale-octa it fixes the boot hangs I was seeing with linux-next on those platforms. Feel free to add: Tested-by: Kevin Hilman khil...@linaro.org Kevin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org

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

both exynos_defconfig and multi_v7_defconfig. Tested-by: Kevin Hilman khil...@linaro.org Kevin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2] ARM: dts: Add dts file for odroid XU3 board

to be used by the MFC Kevin, Tyler, even though the changes are small i didn't want to just stick your Tested-By on. Could you both be so kind to retest this on your XU3's ? Tested-by: Kevin Hilman khil...@linaro.org Tested on top of linux-next(ish) and Javier's dp-integ branch and it's booting

Re: [PATCH] ARM: dts: Add dts file for odroid XU3 board

-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk Tested-by: Kevin Hilman khil...@linaro.org Tried this on top of linux-next (next-20141125 and next20141203) and boots fine on my odroid-xu3. Thanks for doing this, I've been meaning to get a DTS upstream for this platform myself. I also noticed

Re: [PATCH v2 2/7] ARM: Exynos: add support for sub-power domains

Marek Szyprowski m.szyprow...@samsung.com writes: Hello, On 2014-12-03 13:36, Geert Uytterhoeven wrote: Hi Marek, On Wed, Dec 3, 2014 at 1:33 PM, Marek Szyprowski m.szyprow...@samsung.com wrote: diff --git a/Documentation/devicetree/bindings/arm/exynos/power_domain.txt

Re: [PATCH] ARM: dts: Add dts file for odroid XU3 board

Sjoerd Simons sjoerd.sim...@collabora.co.uk writes: On Wed, 2014-12-03 at 11:53 -0800, Kevin Hilman wrote: Sjoerd Simons sjoerd.sim...@collabora.co.uk writes: Tried this on top of linux-next (next-20141125 and next20141203) and boots fine on my odroid-xu3. Thanks for doing this, I've been

Re: [PATCH RFT 2/2] arm: dts: disable CCI on exynos420 based arndale-octa

for the arndale-octa board. Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com Tested-by: Kevin Hilman khil...@linaro.org Tested on top of next-20141128 with exynos_defconfig on my Octa board and I'm not seeing the imprecise aborts anymore. Thanks, Kevin -- To unsubscribe from this list

Re: [PATCH V4 1/3] PM / Domains: Initial PM clock support for genpd

-off-by: Ulf Hansson ulf.hans...@linaro.org Acked-by: Geert Uytterhoeven geert+rene...@glider.be Acked-by: Kevin Hilman khil...@linaro.org Are you also planning to add a way to enable this option from DT? Kevin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc

Re: [RFC] ARM: exynos: MCPM: [is this a] fix for secondary boot on 5422?

Hello, Heesub Shin heesub.s...@samsung.com writes: Using the current exynos_defconfig on the exynos5422-odroid-xu3, only 6 of 8 CPUs come online with MCPM boot. CPU0 is an A7, CPUs 1-4 are A15s and CPU5-7 are the other A7s, but with the current code, CPUs 5 and 7 do not boot: [...]

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

Abhilash Kesavan kesavan.abhil...@gmail.com writes: Hi Kevin, On Wed, Nov 26, 2014 at 6:30 AM, Kevin Hilman khil...@kernel.org wrote: Hi Abhilash, Abhilash Kesavan kesavan.abhil...@gmail.com writes: [...] To be honest, since I don't have the exynos5420 arndale, chromebook...but smdk

Re: [PATCH v12 0/6] cpufreq: use generic cpufreq drivers for exynos platforms

Kevin Hilman khil...@kernel.org writes: Hi Thomas, Thomas Abraham thomas...@samsung.com writes: Changes since v11: - Rebased on top of git://linuxtv.org/snawrocki/samsung.git for-v3.19-exynos-clk Thanks for rebasing/reposting. This patch series removes the use of Exynos4210

Re: [PATCH v12 0/6] cpufreq: use generic cpufreq drivers for exynos platforms

Hi Thomas, On Mon, Nov 24, 2014 at 10:58 AM, Kevin Hilman khil...@kernel.org wrote: [...] Second, as with earlier versions of this series, I'm still seeing lots of wait_until_divider_stable: timeout in divider stablization messages coming out when running powertop. I found a simpler way

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

Hi Abhilash, Abhilash Kesavan kesavan.abhil...@gmail.com writes: [...] To be honest, since I don't have the exynos5420 arndale, chromebook...but smdk which has different bootloader, I couldn't test it...I'll try to make a test farm like you guys... Do you have some colleagues with any

Re: screen blank causing lockup in exynos-reference/exynos5-v3.18-rc2

Hi Vivek, Vivek Gautam gautamvivek1...@gmail.com writes: On Sat, Nov 22, 2014 at 12:53 AM, Kevin Hilman khil...@kernel.org wrote: Hi Ajay, AJAY KUMAR RAMAKRISHNA SHYMALAMMA ajaykumar...@samsung.com writes: I tried to reproduce the issue which you reported, but I am sorry I am not able

Re: [PATCH v12 0/6] cpufreq: use generic cpufreq drivers for exynos platforms

Hi Thomas, Thomas Abraham thomas...@samsung.com writes: Changes since v11: - Rebased on top of git://linuxtv.org/snawrocki/samsung.git for-v3.19-exynos-clk Thanks for rebasing/reposting. This patch series removes the use of Exynos4210 and Exynos5250 specific cpufreq drivers and enables

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

Kukjin, On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman khil...@kernel.org wrote: Kukjin Kim kg...@kernel.org writes: Kevin Hilman wrote: From: Kevin Hilman khil...@linaro.org The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts during boot testing, causing various

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson o...@lixom.net wrote: On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman khil...@kernel.org wrote: Kukjin, On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman khil...@kernel.org wrote: Kukjin Kim kg...@kernel.org writes: Kevin Hilman wrote: From

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson o...@lixom.net wrote: On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman khil...@kernel.org wrote: On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson o...@lixom.net wrote: On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman khil...@kernel.org wrote: Kukjin

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

On Mon, Nov 24, 2014 at 5:50 PM, Kukjin Kim kg...@kernel.org wrote: Olof Johansson wrote: On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson o...@lixom.net wrote: On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman khil...@kernel.org wrote: On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson o

[RFC] ARM: exynos: MCPM: [is this a] fix for secondary boot on 5422?

From: Kevin Hilman khil...@linaro.org Using the current exynos_defconfig on the exynos5422-odroid-xu3, only 6 of 8 CPUs come online with MCPM boot. CPU0 is an A7, CPUs 1-4 are A15s and CPU5-7 are the other A7s, but with the current code, CPUs 5 and 7 do not boot: [...] Exynos MCPM support

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

Javier Martinez Canillas javier.marti...@collabora.co.uk writes: [adding Kukjin as cc and dropping dri-devel] Hello Kevin, On 11/20/2014 07:22 PM, Kevin Hilman wrote: My kernel command line is almost the same with the difference that I'm using clk_ignore_unused and I just checked

Re: screen blank causing lockup in exynos-reference/exynos5-v3.18-rc2

Hi Ajay, AJAY KUMAR RAMAKRISHNA SHYMALAMMA ajaykumar...@samsung.com writes: I tried to reproduce the issue which you reported, but I am sorry I am not able to reproduce it. I tried with my patches for DRM on top of Linux-next. I don't see the issue on linux-next either. As I mentioned in

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

Hi Vivek, Vivek Gautam gautamvivek1...@gmail.com writes: [...] I tested linux-next on Exynos5800 peach-pi board with linux-next and and the two patches $Subject and [0]. Below is my git hash: 4d9e6ee drm/exynos: Move platform drivers registration to module init 4545ed4 POSTED: arm: dts:

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

Javier Martinez Canillas javier.marti...@collabora.co.uk writes: Hello, For completeness I'll comment what we talked with Kevin on IRC since probably this is the same issue that Paolo is facing. On 11/20/2014 05:41 PM, Kevin Hilman wrote: Peach # setenv preboot usb start; sleep 1setenv

Re: exynos boot falures in linux-next

On Mon, Nov 17, 2014 at 7:49 PM, Kevin Hilman khil...@kernel.org wrote: Javier Martinez Canillas javier.marti...@collabora.co.uk writes: Hello Kevin, On 11/17/2014 11:24 PM, Kevin Hilman wrote: As might have been expected, reverting the change that enables the DRM/display options

Re: [PATCH v11 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4210/5250/5420

Hi Thomas, On Mon, Oct 20, 2014 at 4:41 AM, Thomas Abraham thomas...@samsung.com wrote: The new CPU clock type allows the use of generic CPUfreq drivers. So for Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420, which did not have CPUfreq driver support, enable the use of

Re: [PATCH] ARM: multi_v7_defconfig: fix failure setting CPU voltage by enabling dependent I2C controller

Kukjin Kim kgene@samsung.com writes: On 11/19/14 04:10, Tyler Baker wrote: Hi, + Arnd, Olof and Kevin This patch fixes a long standing issue introduced during the 3.16 merge window. Shortly after the merge, exynos5250-based arndale boards began to produce the following errors:

screen blank causing lockup in exynos-reference/exynos5-v3.18-rc2

As I'm hunting around trying to figure out how to make exynos-drm work with v3.18 or linux-next, I noticed there was an exynos5-v3.18-rc2 branch in the exynos-reference tree[1], so I gave that a spin on my exynos5800-peach-pi. It seemed to work OK, but I noticed that as soon as the screen blanked

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

Paolo Pisati p.pis...@gmail.com writes: On Wed, Nov 19, 2014 at 10:35:40AM +0100, Javier Martinez Canillas wrote: Hello Ajay, On 11/18/2014 07:20 AM, Ajay kumar wrote: On Sat, Nov 15, 2014 at 3:24 PM, Ajay Kumar ajaykumar...@samsung.com wrote: This series is based on master branch of

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

Javier Martinez Canillas javier.marti...@collabora.co.uk writes: [adding Paolo and Vivek as cc] Hello, On 11/18/2014 07:41 PM, Kevin Hilman wrote: It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then it proceeds to panic in the workqueue code called by the asoc

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

Kevin Hilman khil...@kernel.org writes: Javier Martinez Canillas javier.marti...@collabora.co.uk writes: [adding Paolo and Vivek as cc] Hello, On 11/18/2014 07:41 PM, Kevin Hilman wrote: It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then it proceeds to panic

Re: [PATCH 0/3] PM / Domains: Add initial PM clock support to genpd

Ulf Hansson ulf.hans...@linaro.org writes: It's quite common for PM domains to use PM clocks. Typically from SOC specific code, the per device PM clock list is created and pm_clk_suspend|resume() are invoked to handle clock gating/ungating. A step towards consolidation is to integrate PM

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

(). Fix this by moving the platform drivers registration to exynos_drm_init(). Suggested-by: Andrzej Hajda a.ha...@samsung.com Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk --- This issue was reported by both Krzysztof Kozlowski [0] and Kevin Hilman [1]. Inki Dae said

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

Gustavo Padovan gust...@padovan.org writes: 2014-11-18 Kevin Hilman khil...@kernel.org: Javier Martinez Canillas javier.marti...@collabora.co.uk writes: The Exynos DRM driver register its sub-devices platform drivers in the probe function but after commit 43c0767 (of/platform: Move

exynos boot falures in linux-next (was: next boot: 94 boots: 79 pass, 13 fail, 2 untried (next-20141117))

FYI... Various new exynos5 boot failures starting next-20141117. Looking in the boot logs, the boot stops during DRM initialization. Note that the boot failures are only on exynos_defconfig, and not multi_v7_defconfig. Excerpt from boot report below, or recent exynos boots can also be explored

Re: [PATCH] PM / Domains: Power on the PM domain right after attach completes

Ulf Hansson ulf.hans...@linaro.org writes: The amba bus, amba drivers and a vast amount of platform drivers which enables runtime PM, don't invoke a pm_runtime_get_sync() while probing their devices. Instead, once they have turned on their PM resourses during -probe() and are ready to

Re: exynos boot falures in linux-next

Kevin Hilman khil...@kernel.org writes: FYI... Various new exynos5 boot failures starting next-20141117. Looking in the boot logs, the boot stops during DRM initialization. Note that the boot failures are only on exynos_defconfig, and not multi_v7_defconfig. As might have been expected

Re: exynos boot falures in linux-next

Javier Martinez Canillas javier.marti...@collabora.co.uk writes: Hello Kevin, On 11/17/2014 11:24 PM, Kevin Hilman wrote: As might have been expected, reverting the change that enables the DRM/display options in exynos_defconfig fixes the problem. Kevin I'm sorry for causing a boot

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

Kukjin Kim kg...@kernel.org writes: Kevin Hilman wrote: From: Kevin Hilman khil...@linaro.org The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts during boot testing, causing various userspace startup failures. Disable until it has gotten more testing. Cc: Kukjin

Re: [PATCH 03/12] PM / Domains: Add notifier support for power domain transitions

Sylwester Nawrocki s.nawro...@samsung.com writes: On 04/11/14 07:44, amit daniel kachhap wrote: On Mon, Nov 3, 2014 at 11:53 PM, Kevin Hilman khil...@kernel.org wrote: Rafael J. Wysocki r...@rjwysocki.net writes: On Monday, November 03, 2014 09:23:01 AM Amit Daniel Kachhap wrote: These power

Re: [PATCH] PM / Domains: Fix initial default state of the need_restore flag

trace 40cd58bcd6988f12 ]--- Fixes: a4a8c2c4962bb655 (ARM: exynos: Move to generic PM domain DT bindings) Reported-by: Sylwester Nawrocki s.nawro...@samsung.com Signed-off-by: Ulf Hansson ulf.hans...@linaro.org Reviewed-by: Kevin Hilman khil...@linaro.org And looks like we need this for v3.18-rc

Re: [PATCH] PM / Domains: Fix initial default state of the need_restore flag

Dmitry Torokhov dmitry.torok...@gmail.com writes: On Fri, Nov 07, 2014 at 11:47:53AM -0800, Kevin Hilman wrote: Ulf Hansson ulf.hans...@linaro.org writes: The initial state of the device's need_restore flag should'nt depend on the current state of the PM domain. For example it should

Re: [PATCH] PM / Domains: Change prototype for the -attach_dev() callback

Dmitry Torokhov dmitry.torok...@gmail.com writes: On Thu, Oct 30, 2014 at 01:38:30PM -0700, Kevin Hilman wrote: Rafael J. Wysocki r...@rjwysocki.net writes: On Thursday, October 30, 2014 01:02:49 PM Ulf Hansson wrote: Convert the prototype to return and int. This is just an initial step

Re: [RFC 1/2] PM / Domains: Power on domain early during system resume

Andrzej Hajda a.ha...@samsung.com writes: On 10/30/2014 08:36 AM, Krzysztof Kozlowski wrote: On śro, 2014-10-29 at 10:46 -0700, Kevin Hilman wrote: Krzysztof Kozlowski k.kozlow...@samsung.com writes: When resuming the system the power domain has to be powered on early so any runtime PM

Re: pm_runtime_enable() in -probe()

Rafael J. Wysocki r...@rjwysocki.net writes: On Saturday, November 01, 2014 02:08:57 AM Rafael J. Wysocki wrote: On Saturday, November 01, 2014 01:20:38 AM Rafael J. Wysocki wrote: On Friday, October 31, 2014 10:16:14 AM Ulf Hansson wrote: On 24 October 2014 18:12, Kevin Hilman khil

Re: [PATCH 03/12] PM / Domains: Add notifier support for power domain transitions

+Mike Turquette Hi Amit, Rafael J. Wysocki r...@rjwysocki.net writes: CC: Kevin, Ulf, Geert. On Monday, November 03, 2014 09:23:01 AM Amit Daniel Kachhap wrote: These power domain transition notifiers will assist in carrying out some activity associated with domain power on/off such as

Re: exynos5420/arndale-octa: imprecise external aborts on exynos_defconfig

On Wed, Sep 17, 2014 at 5:39 PM, Kevin Hilman khil...@kernel.org wrote: Thomas Abraham ta.oma...@gmail.com writes: On Thu, Sep 11, 2014 at 12:16 AM, Kevin Hilman khil...@kernel.org wrote: Tyler Baker tyler.ba...@linaro.org writes: Exynos5420-based Arndale octa boards have recently started

[PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

From: Kevin Hilman khil...@linaro.org The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts during boot testing, causing various userspace startup failures. Disable until it has gotten more testing. Cc: Kukjin Kim kgene@samsung.com, Cc: Javier Martinez Canillas javier.marti

Re: [PATCH] PM / Domains: Change prototype for the -attach_dev() callback

Rafael J. Wysocki r...@rjwysocki.net writes: On Thursday, October 30, 2014 01:02:49 PM Ulf Hansson wrote: Convert the prototype to return and int. This is just an initial step, needed to support error handling. Signed-off-by: Ulf Hansson ulf.hans...@linaro.org Acked-by: Kevin Hilman khil

Re: [PATCH v3 0/9] PM / Domains: Fix race conditions during boot

Mark Brown broo...@kernel.org writes: On Fri, Oct 24, 2014 at 09:12:39AM -0700, Kevin Hilman wrote: Ulf Hansson ulf.hans...@linaro.org writes: There may be more than one device in a PM domain which then will be probed at different points in time. Depending on timing and runtime PM

Re: [PATCH v3 4/9] drivercore / platform: Keep PM domain powered during -probe()

Ulf Hansson ulf.hans...@linaro.org writes: To sucessfully probe some devices their corresponding PM domains may need to be powered. Isn't that what pm_runtime_get*() is supposed to be doing? Why isn't that working? Kevin -- To unsubscribe from this list: send the line unsubscribe

Re: [RFC 1/2] PM / Domains: Power on domain early during system resume

Krzysztof Kozlowski k.kozlow...@samsung.com writes: When resuming the system the power domain has to be powered on early so any runtime PM aware devices could resume. This fixes following scenario reproduced on Exynos DRM: 1. Power domain is off before suspending the system. 2. System is

  1   2   >