The exynos SoCs uses MCT(Multi-Core Timer) so it doesn't need to map PWM
memory area to virtual memory(S3C_VA_TIMER) statically for timer.
This patch also remove functions call dependent to S3C_VA_TIMER.
- s3c_pwmclk_init()
- s5p_init_irq()
They access PWM registers via S3C_VA_TIMER but exynos
This is PWM driver to support 4 pwm for Exynos SoCs. Also this supports
device tree node.
The existing s3c24xx-pwm driver has many dependence with arch specific
codes and it is difficult to support device tree by static mapping of
PMW memory area. Also it can't support multi pwm to one device and
V5 patches are based on Mark Brown's for-next branch of
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
Changes since V4:
- Add a new patch for renaming the samsung i2s secondary fifo interface
device name from samsung-i2s.4 to samsung-i2s-sec
- Add
All Samsung SoCs has max 3 i2s controllers. So the i2s secondary fifo
interface device id was named as samsung-i2s.4. Renaming this to
samsung-i2s-sec to support device tree in i2s driver.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
sound/soc/samsung/i2s.c | 31
Add support for device based discovery.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
.../devicetree/bindings/sound/samsung-i2s.txt | 75 +++
sound/soc/samsung/dma.c|1 +
sound/soc/samsung/dma.h|1 +
This patch series adds pinctrl driver support for Samsung's Exynos5250 SoC.
The first patch adds the required Exynos5250 SoC specific data which is
used by the Samsung pinctrl driver to setup the pinctrl/pinmux/eint
controllers. The second and third patches skips the wakeup interrupt and
gpiolib
Add Samsung Exynos5250 SoC specific data to enable pinctrl support for
all platforms based on Exynos5250.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
drivers/pinctrl/pinctrl-exynos.c | 108 +
drivers/pinctrl/pinctrl-samsung.c |2 +
Skip exynos5250 gpiolib registration if pinctrl support for exynos5250
is enabled.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
drivers/gpio/gpio-samsung.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/gpio/gpio-samsung.c
Skip the wakeup interrupt registration for Exynos5250 if pinctrl support
is enabled for Exynos5250.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
arch/arm/mach-exynos/common.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-exynos/common.c
Add pinctrl device nodes for Exynos5250 SoC.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
Few notes on this patch:
- Only pinctrl-0 and pinctrl-3 nodes have been added. Since pinctrl-1 is
mostly used for camera interface, and since I do not have good
understanding of this
Using chip specific compatible string as it should be.
So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
which till now used a generic 'exynos' in their compatible strings.
This goes as per the discussion happened in the thread for
[PATCH v2] ARM: Exynos5250: Enabling dwc3-exynos driver
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/host/ehci-s5p.c|2 +-
drivers/usb/host/ohci-exynos.c |2 +-
2 files changed, 2 insertions(+), 2
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/dwc3/dwc3-exynos.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
CC: LKML
On Thu, Dec 13, 2012 at 8:22 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Using chip specific compatible string as it should be.
So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
which till now used a generic 'exynos' in their compatible strings.
This goes as per the
On Thu, Dec 13, 2012 at 8:22 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/host/ehci-s5p.c|2
CC: LKML
On Thu, Dec 13, 2012 at 8:22 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Changes from v2:
- Changed the compatible string to chip specific(samsung,exynos4210),
since ehci-s5p and ohci-exynos are being used from exynso4210 onwards.
- Based on changes for drivers available at:
http://www.mail-archive.com/devicetree-discuss@lists.ozlabs.org/msg23218.html
Changes
Adding EHCI device tree node for Exynos5250 along with
the device base adress and gpio line for vbus.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
---
.../devicetree/bindings/usb/exynos-usb.txt | 25
Adding OHCI device tree node for Exynos5250 along with
the device base address.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
---
.../devicetree/bindings/usb/exynos-usb.txt | 15 +++
arch/arm/boot/dts/exynos5250.dtsi
Adding DWC3 device tree node for Exynos5250 along with the
device address and clock support needed for the controller.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Changes from v2:
- Changed the compatible string to chip specific(samsung,exynos5250),
since dwc3-exynos is being
The s3c-pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com
---
drivers/pwm/pwm-samsung.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pwm/pwm-samsung.c b/drivers/pwm/pwm-samsung.c
index 023a3be..b415102 100644
---
This patchset adds
1. Support for generic gpio based i2c bus arbitration between 2 i2c Masters
Ex: between AP(exynos), device(EC).
2. Documentation and sample implmentation in i2c-s3c2410 driver.
Naveen Krishna Chatradhi (2):
i2c-core: Add gpio based bus arbitration implementation
The arbitrator is a general purpose function which uses two GPIOs to
communicate with another device to claim/release a bus.
i2c_transfer()
if adapter-gpio_arbit
i2c_bus_claim();
__i2c_transfer();
i2c_bus_release();
Signed-off-by:
On Fri, Dec 14, 2012 at 01:20:09PM +0900, Joonyoung Shim wrote:
The s3c-pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com
---
drivers/pwm/pwm-samsung.c |2 ++
1 file changed, 2 insertions(+)
diff --git
The s3c-pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com
---
Changelog from v1:
- move the assignment code to below.
drivers/pwm/pwm-samsung.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pwm/pwm-samsung.c
On Fri, Dec 14, 2012 at 03:58:58PM +0900, Joonyoung Shim wrote:
The s3c-pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com
I've modified the subject a bit to make it clear the assignment of
s3c-pwm_id was missing, not the s3c-pwm_id
On 12/14/2012 04:34 PM, Thierry Reding wrote:
On Fri, Dec 14, 2012 at 03:58:58PM +0900, Joonyoung Shim wrote:
The s3c-pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com
I've modified the subject a bit to make it clear the assignment
27 matches
Mail list logo
