[PATCH] ARM: S3C64XX: Don't specify an irq_base for WM1192-EV1 board

2012-07-10 Thread Mark Brown
None of the GPIO IRQs are connected so there is no reason to specify a base. Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com --- arch/arm/mach-s3c64xx/mach-smdk6410.c |1 - 1 file changed, 1 deletion(-) diff --git a/arch/arm/mach-s3c64xx/mach-smdk6410.c

Re: [GIT PULL] Samsung cleanup-1 for v3.6

2012-07-10 Thread Arnd Bergmann
On Tuesday 10 July 2012, Kukjin Kim wrote: arch/arm/mach-exynos/common.c | 25 -- arch/arm/mach-exynos/include/mach/spi-clocks.h | 16 arch/arm/mach-exynos/mach-nuri.c|1 - arch/arm/mach-exynos/mach-origen.c |1 -

Re: [GIT PULL] Samsung devel-dma ops for v3.6

2012-07-10 Thread Arnd Bergmann
On Tuesday 10 July 2012, Kukjin Kim wrote: Hi Arnd, Olof, Here is updating DMA common operation for Samsung SoCs. Since some DMA client driver such as spi needs to change the configuration after dma_request() so this branch adds dma_config() can configure DMA transmit option which is

Re: [GIT PULL] Samsung board-1 for v3.6

2012-07-10 Thread Arnd Bergmann
On Tuesday 10 July 2012, Kukjin Kim wrote: Kukjin Kim kgene@samsung.com, Senior Engineer, SW Solution Development Team, Samsung Electronics Co., Ltd. The following changes since commit cfaf025112d3856637ff34a767ef785ef5cf2ca9: Linux 3.5-rc2 (2012-06-08 18:40:09 -0700) are

[PATCH v4 3/6] ARM: Samsung: Remove pdev pointer parameter from spi gpio setup functions

2012-07-10 Thread Thomas Abraham
The platform data pointer that is passed to the spi gpio setup functions is not used. Hence, this paremeter is removed from all the spi gpio setup functions. Signed-off-by: Thomas Abraham thomas.abra...@linaro.org Acked-by: Jaswinder Singh jaswinder.si...@linaro.org ---

[PATCH v4 4/6] ARM: Samsung: Modify s3c64xx_spi{0|1|2}_set_platdata function

2012-07-10 Thread Thomas Abraham
With the spi controller hardware configuration moved into the driver data, there are no more default hardware configuration data that is passed through platform data. Accordingly, the s3c64xx_spi{0|1|2}_set_platdata functions are adapted to these changes. Signed-off-by: Thomas Abraham

[PATCH v4 5/6] spi: s3c64xx: Remove the 'set_level' callback from controller data

2012-07-10 Thread Thomas Abraham
The set_level callback in the controller data, which is used to configure the slave select line, cannot be supported when migrating the driver to device tree based discovery. Since all the platforms currently use gpio as the slave select line, this callback can be removed from the controller data

Re: [PATCH v4 5/6] spi: s3c64xx: Remove the 'set_level' callback from controller data

2012-07-10 Thread Mark Brown
On Tue, Jul 10, 2012 at 07:57:38PM +0530, Thomas Abraham wrote: The set_level callback in the controller data, which is used to configure the slave select line, cannot be supported when migrating the driver to device tree based discovery. Since all the platforms currently use gpio as the slave

Re: [PATCH v4 5/6] spi: s3c64xx: Remove the 'set_level' callback from controller data

2012-07-10 Thread Thomas Abraham
On 10 July 2012 20:08, Mark Brown broo...@opensource.wolfsonmicro.com wrote: On Tue, Jul 10, 2012 at 07:57:38PM +0530, Thomas Abraham wrote: The set_level callback in the controller data, which is used to configure the slave select line, cannot be supported when migrating the driver to device

Re: [PATCH v4 5/6] spi: s3c64xx: Remove the 'set_level' callback from controller data

2012-07-10 Thread Mark Brown
On Tue, Jul 10, 2012 at 10:22:31PM +0530, Thomas Abraham wrote: In non-dt case, the platform code supplying the gpio number (slave select line) is responsible for requesting the gpio during the machine_init call. So the gpio request is not called in the driver for that gpio. In dt case, the

Re: [PATCH v4 5/6] spi: s3c64xx: Remove the 'set_level' callback from controller data

2012-07-10 Thread Thomas Abraham
On 10 July 2012 22:27, Mark Brown broo...@opensource.wolfsonmicro.com wrote: On Tue, Jul 10, 2012 at 10:22:31PM +0530, Thomas Abraham wrote: In non-dt case, the platform code supplying the gpio number (slave select line) is responsible for requesting the gpio during the machine_init call. So

Re: [PATCH 1/4] [SCSI] ufs: Separate PCI glue driver for ufshcd

2012-07-10 Thread vinayak holikatti
On Mon, Jul 2, 2012 at 8:47 PM, Arnd Bergmann a...@arndb.de wrote: On Monday 02 July 2012, Vinayak Holikatti wrote: This patch separates PCI and core UFS host controller driver. In the current implementation PCI specific code is with ufshcd.c. To provide way for adding multiple bus glue

Re: [PATCH 2/4] [SCSI] ufs: Add Platform glue driver for ufshcd

2012-07-10 Thread vinayak holikatti
On Mon, Jul 2, 2012 at 8:57 PM, Arnd Bergmann a...@arndb.de wrote: On Monday 02 July 2012, Vinayak Holikatti wrote: +static struct platform_driver ufshcd_pltfrm_driver = { + .probe = ufshcd_pltfrm_probe, + .remove = __devexit_p(ufshcd_pltfrm_remove), +#ifdef CONFIG_PM +

Re: [PATCH 3/4] [SCSI] ufs: Add AMBA glue driver to ufshcd

2012-07-10 Thread vinayak holikatti
On Mon, Jul 2, 2012 at 8:50 PM, Arnd Bergmann a...@arndb.de wrote: On Monday 02 July 2012, Vinayak Holikatti wrote: +static struct amba_id ufshcd_amba_ids[] = { + { + /* Fake id for Primecell.*/ + .id = 0x00041FF0, + .mask = 0x000f,