Re: Spurious IPIs on secondary cpu bringup with EXYNOS 4412

2012-10-01 Thread Kyungmin Park
On 10/2/12, Matthew Leach wrote: > Hi, > > I applied the secondary CPU bringup patch [1] to mainline, however when > booting I get the following spurious IPIs after each core has booted: > > [0.05] CPU1: Booted secondary processor > [0.075000] CPU1: thread -1, cpu 1, socket 10, mpidr 8

Re: Problem using S3C2416's HSSPI

2012-10-01 Thread Heiko Stübner
Am Montag, 1. Oktober 2012, 21:40:35 schrieb Sylwester Nawrocki: > On 10/01/2012 09:18 PM, Heiko Stübner wrote: > > Hi José, > > > > Am Montag, 1. Oktober 2012, 19:32:15 schrieb José Miguel Gonçalves: > >> I'm trying to use the HSSPI controller on a S3C2416 based board but I'm > >> having some pro

Re: Problem using S3C2416's HSSPI

2012-10-01 Thread José Miguel Gonçalves
On 10/01/2012 08:18 PM, Heiko Stübner wrote: Hi José, Am Montag, 1. Oktober 2012, 19:32:15 schrieb José Miguel Gonçalves: I'm trying to use the HSSPI controller on a S3C2416 based board but I'm having some problems. I've added "&s3c64xx_device_spi0" to my array of platform devices and added a

Re: Problem using S3C2416's HSSPI

2012-10-01 Thread Sylwester Nawrocki
Hi, On 10/01/2012 09:18 PM, Heiko Stübner wrote: > Hi José, > > Am Montag, 1. Oktober 2012, 19:32:15 schrieb José Miguel Gonçalves: >> I'm trying to use the HSSPI controller on a S3C2416 based board but I'm >> having some problems. >> >> I've added "&s3c64xx_device_spi0" to my array of platform d

Re: Problem using S3C2416's HSSPI

2012-10-01 Thread Heiko Stübner
Hi José, Am Montag, 1. Oktober 2012, 19:32:15 schrieb José Miguel Gonçalves: > I'm trying to use the HSSPI controller on a S3C2416 based board but I'm > having some problems. > > I've added "&s3c64xx_device_spi0" to my array of platform devices and added > a call to s3c64xx_spi0_set_platdata(NULL

Problem using S3C2416's HSSPI

2012-10-01 Thread José Miguel Gonçalves
Hi, I'm trying to use the HSSPI controller on a S3C2416 based board but I'm having some problems. I've added "&s3c64xx_device_spi0" to my array of platform devices and added a call to s3c64xx_spi0_set_platdata(NULL, 0, 1) before platform_add_devices(). When the kernel starts I see the follow

Spurious IPIs on secondary cpu bringup with EXYNOS 4412

2012-10-01 Thread Matthew Leach
Hi, I applied the secondary CPU bringup patch [1] to mainline, however when booting I get the following spurious IPIs after each core has booted: [0.05] CPU1: Booted secondary processor [0.075000] CPU1: thread -1, cpu 1, socket 10, mpidr 8a01 [0.08] CPU1: Unknown IPI messa

Re: [PATCH V6 2/2] video: drm: exynos: Add device tree support

2012-10-01 Thread Stephen Warren
On 09/30/2012 11:29 PM, Leela Krishna Amudala wrote: > Hello Stephen Warren, > > The binding names that I use in my dts file should match with the > names given in > http://lists.freedesktop.org/archives/dri-devel/2012-July/024875.html > right? I don't think so; the binding in that link is for e

[PATCH 2/2] ARM: Exynos4: Register clocks via common clock framework

2012-10-01 Thread chander . kashyap
From: Thomas Abraham Register clocks for Exynos4 platfotms using common clock framework. Also included are set of helper functions for clock registration that can be reused on other Samsung platforms as well. Cc: Mike Turquette Cc: Kukjin Kim Signed-off-by: Thomas Abraham --- arch/arm/mach-e

[PATCH 0/2] ARM: Exynos4: Migrate to common clock framework.

2012-10-01 Thread chander . kashyap
From: Thomas Abraham This patch series migrates Exynos4 clock support to common clock framework. The first patch in this series removes the existing Exynos4 clock support that uses the Samsung specific clock framework. The second patch in this series add Exynos4 clock support using common clock f

Re: [PATCH 3/3] DMA: PL330: Balance module remove function with probe

2012-10-01 Thread Inderpal Singh
On 28 September 2012 16:28, Jassi Brar wrote: > On Fri, Sep 28, 2012 at 10:03 AM, Inderpal Singh > wrote: >> >> Now, if we have to check if any client is using the channel and then >> decide. We will have to traverse the channel list twice once to check >> the usage and second time to delete the