Add information about the Exynos4210 pin banks, SoC specific configuration
callbacks and driver data which is used by the Samsung pinctrl driver.
Signed-off-by: Thomas Abraham
---
drivers/pinctrl/Kconfig |7 ++
drivers/pinctrl/Makefile |1 +
drivers/pinctrl/pinctrl-exy
Pinctrl driver, when enabled, registers all the gpio pins and hence the
registration of gpio pins by this driver can be skipped.
Signed-off-by: Thomas Abraham
---
drivers/gpio/gpio-samsung.c | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/drivers/gpi
Add a new pinctrl and gpiolib driver for Samsung SoC's. This driver provides a
common framework for all Samsung SoC's to interface with the pinctrl and
gpiolib subsystems.
This driver is split into two parts: the pinctrl interface and the gpiolib
interface. The pinctrl interface registers pinctrl
This patch series adds a common pinctrl driver for all Samsung platforms and
enables the pinctrl driver support for Exynos4210 based device tree enabled
platforms. The scope of this driver is limited to only device tree enabled
platforms.
The intention of this driver is to replace the existing gpi
Hi Jonghwa,
I didn't know about confirmation of your mfd driver by Samuel Oritz.
So please feel free to revise and submit your patch set.
Anyways, I am interested only in getting the driver for max77686 in mainline.
Thanks,
Yadwinder.
On Wed, May 23, 2012 at 3:48 PM, Mark Brown
wrote:
> On Wed,
During all transfers in one message, the device will not be chagned.
So we don't need to deassert chipselect during one message.
Signed-off-by: Kyoungil Kim
---
drivers/spi/spi-s3c64xx.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-s3c64xx.c b/drivers
Setting SW_RST does TX/RX FIFO flush.
After FIFO flush, SW_RST should be cleared.
The above setting and clearing SW_RST operation should be done after spi
channel off.
Signed-off-by: Kyoungil Kim
---
drivers/spi/spi-s3c64xx.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
di
On Wed, May 23, 2012 at 02:33:28PM +0900, jonghwa3@samsung.com wrote:
> I inform you my mfd driver has been confirmed by Samuel Oritz and there
> is no mfd private API. This situation looks unusual that we registers
> mfd driver and regulator driver separately. But how should we do? For
> corp
From: Bartlomiej Zolnierkiewicz
Subject: [PATCH] ARM: EXYNOS: Remove leftovers of the Samsung specific power
domain control
Nowadays we use generic power domain support instead of Samsung
specific power domain control driver.
Cc: Thomas Abraham
Cc: Rob Herring
Cc: Grant Likely
Cc: Rafael J.