Re: [PATCH v5 0/7] platform/chrome: Add user-space dev inferface support

2015-02-17 Thread Simon Glass
Hi, On 16 February 2015 at 01:19, Javier Martinez Canillas javier.marti...@collabora.co.uk wrote: Hello Olof, On 02/02/2015 12:26 PM, Javier Martinez Canillas wrote: Hello, The mainline ChromeOS Embedded Controller (EC) driver is still missing some features that are present in the

RE: [PATCH 0/9] ARM: samsung: randconfig build fixes

2015-02-17 Thread Kukjin Kim
Arnd Bergmann wrote: This is a set of mostly trivial build fixes for bugs I have encountered in random configurations. I'm sending them separate from the other platforms since we have a lot of them for the various samsung platforms here. Kukjin, please pick them up into a fixes branch for

[PATCH] Revert drm/exynos: IOMMU support should not be selectable by user

2015-02-17 Thread Charles Keepax
This reverts commit 8dcc14f82f06fce997e35f4c77ced9d4ed192f31. This patch causes this error on Arndale: [1.643800] kernel BUG at drivers/iommu/exynos-iommu.c:481! [1.649355] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM [1.655170] Modules linked in: [1.658203] CPU: 1 PID: 1

[PATCH] drm/exynos: Check for NULL dereference of crtc

2015-02-17 Thread Charles Keepax
The commit drm/exynos: remove exynos_plane_dpms (d9ea6256) removed the use of the enabled flag, which means that the code may attempt to call win_enable on a NULL crtc. This results in the following oops on Arndale: [1.673479] Unable to handle kernel NULL pointer dereference at virtual

Re: exynos4412: misc issues on Hardkernel Odroid boards

2015-02-17 Thread Krzysztof Kozlowski
2015-02-14 19:14 GMT+01:00 Tobias Jakobi tjak...@math.uni-bielefeld.de: Hello! Marek Szyprowski wrote: 4) Spinlock BUGs triggered by the sdhci subsystem (so for the people using the system with a SD card). This is also a known problem, I think first mentioned here:

Re: [PATCH] Revert drm/exynos: IOMMU support should not be selectable by user

2015-02-17 Thread Charles Keepax
On Tue, Feb 17, 2015 at 09:18:28PM +0100, Javier Martinez Canillas wrote: Hello Charles, On Tue, Feb 17, 2015 at 5:58 PM, Charles Keepax ckee...@opensource.wolfsonmicro.com wrote: This reverts commit 8dcc14f82f06fce997e35f4c77ced9d4ed192f31. This patch causes this error on Arndale:

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

2015-02-17 Thread Javier Martinez Canillas
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 support should not be selectable by user), it is selected if

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

2015-02-17 Thread Tobias Jakobi
Hello! Lukasz Majewski wrote: Hi Krzysztof, Thomas, 2015-01-08 22:17 GMT+01:00 Kevin Hilman khil...@kernel.org: Hi Thomas, Do you plan to continue with this work? It would be very helpful. +1 from me. I also wonder if Exynos 4412 could be re-added (without the boost if these

Re: [PATCH] Revert drm/exynos: IOMMU support should not be selectable by user

2015-02-17 Thread Javier Martinez Canillas
Hello Charles, On Tue, Feb 17, 2015 at 5:58 PM, Charles Keepax ckee...@opensource.wolfsonmicro.com wrote: This reverts commit 8dcc14f82f06fce997e35f4c77ced9d4ed192f31. This patch causes this error on Arndale: IMHO the commit you are referring is correct so it should not be reverted but I also

Re: [PATCH] ARM: EXYNOS: Don't use LDREX and STREX after disabling cache coherency

2015-02-17 Thread Stephen Boyd
On 02/16/15 05:36, Krzysztof Kozlowski wrote: During CPU shutdown the exynos_cpu_power_down() is called after disabling cache coherency and it uses LDREX and STREX instructions (by calling of_machine_is_compatible() - kobject_get() - kref_get()). The LDREX and STREX should not be used after

drm/exynos: DRM_EXYNOS7DECON?

2015-02-17 Thread Paul Bolle
Your commit 96976c3d9aff (drm/exynos: Add DECON driver) is included in today's linux-next (ie, next-20150217). I noticed because a script I use to check linux-next spotted a problem with it. It added an (optional) dependency on DRM_EXYNOS7DECON instead of DRM_EXYNOS7_DECON (see drivers/gpu/drm

Re: drm/exynos: DRM_EXYNOS7DECON?

2015-02-17 Thread Inki Dae
On 2015년 02월 17일 18:04, Paul Bolle wrote: Your commit 96976c3d9aff (drm/exynos: Add DECON driver) is included in today's linux-next (ie, next-20150217). I noticed because a script I use to check linux-next spotted a problem with it. It added an (optional) dependency on DRM_EXYNOS7DECON

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

2015-02-17 Thread Krzysztof Kozlowski
On wto, 2015-02-17 at 12:38 +0100, Javier Martinez Canillas wrote: 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

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

2015-02-17 Thread Marek Szyprowski
Hello, On 2015-02-17 12:38, Javier Martinez Canillas wrote: 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 support

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

2015-02-17 Thread Javier Martinez Canillas
in Exynos defconfig until things get sorted out. On which board you got this error? Sorry, I should had mention it in the commit message. I get that error with at least Exynos5800 Peach Pi, Exynos5420 Peach Pit and Exynos5250 Snow Chromebooks with today's next (next-20150217). The problem

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

2015-02-17 Thread Krzysztof Kozlowski
Pit and Exynos5250 Snow Chromebooks with today's next (next-20150217). The problem is that the Exynos IOMMU driver does not set a struct exynos_iommu_owner in dev.archdata.iommu but __exynos_sysmmu_enable() has a BUG_ON(!has_sysmmu(dev)). Marek's series [1] solves this issue by filling