On Tuesday 06 December 2011 12:01 PM, Jingoo Han wrote:
This patch adds USB ohci device definition for Exynos SoCs.
Signed-off-by: Jingoo Hanjg1@samsung.com
---
arch/arm/mach-exynos/Kconfig |5 +++
arch/arm/mach-exynos/Makefile |1 +
Tushar Behera wrote:
Subject: Re: [PATCH v2 1/3] ARM: EXYNOS: Add USB OHCI device
On Tuesday 06 December 2011 12:01 PM, Jingoo Han wrote:
This patch adds USB ohci device definition for Exynos SoCs.
Signed-off-by: Jingoo Hanjg1@samsung.com
---
arch/arm/mach-exynos/Kconfig
Mark Brown wrote:
On Mon, Dec 05, 2011 at 01:15:18AM +0100, Rafael J. Wysocki wrote:
On Monday, December 05, 2011, Mark Brown wrote:
It might make sense for it to go via the Samsung tree - the third
patch
depends on it and there's some other stuff going on with the s3c64xx
power
Padmavathi Venna wrote:
SPI platform devices are defined in respective machine folder of
Samsung S3C64XX and S5P series SoCs.This patchset moves S3C64XX
and S5P series of SPI platform devices to a common place plat-samsung.
This patchset also creates SPI setup files for GPIO configurations
Hi,
When PM_RUNTIME is enabled, PL330 probe fails because of some
mismatch in pm_runtime calls. This patchset fixes those issues.
This patch is based on Kukjin's for-next branch and tested on
EXYNOS4 based Origen board.
d3d936c Merge branch 'samsung-fixes-2' into for-next
Tushar Behera (2):
To
amba_probe() now calls pm_runtime_get_noresume() and pm_runtime_enable()
for the devices before the device probe is called. Hence we don't need
to call pm_runtime_get_xxx and pm_runtime_enable() in device probe again.
In the same way, since amba_remove() calls the respective pm_runtime
functions,
Amba core assumes the pclk to be named as apb_pclk. During device probe,
it tries to get that clock and enable that. When PM_RUNTIME is enabled,
dma clock is not explicitly enabled in pl330_probe, which causes device
probe to fail. Adding a clkdev entry for apb_pclk for mdma1 fixes the
problem.
Denis Kuzmenko wrote:
Fix compilation error when CONFIG_CPU_FREQ_S3C24XX_DEBUGFS selected.
Signed-off-by: Denis Kuzmenko li...@solonet.org.ua
---
Patch is against 3.2-rc3.
CONFIG_S3C2410_IOTIMING wasn't present in Kconfig but was referenced by
Makefile. Because of this the file
Denis Kuzmenko wrote:
Add new LCD (W35i) support for Mini2440 board
Signed-off-by: Denis Kuzmenko li...@solonet.org.ua
---
diff --git a/arch/arm/mach-s3c2440/mach-mini2440.c
b/arch/arm/mach-s3c2440/mach-mini2440.c
index fc2dc0b..951eadd 100644
---
Hello,
I'm trying to integrate your SYSMMU driver with my DMA-mapping IOMMU
API integration patches. I've noticed some issues, please see my comments below.
On Friday, November 18, 2011 10:48 AM KyongHo Cho wrote:
This is the System MMU driver and IOMMU API implementation for
Exynos SOC
Hello,
On Friday, November 18, 2011 10:47 AM KyongHo Cho wrote:
Handling System MMUs with an identifier is not flexible to manage
System MMU platform devices because of the following reasons:
1. A device driver which needs to handle System MMU must know the ID.
2. A System MMU may not
Hello,
On Tuesday, December 06, 2011 11:20 AM Kukjin Kim wrote:
Mark Brown wrote:
On Mon, Dec 05, 2011 at 01:15:18AM +0100, Rafael J. Wysocki wrote:
On Monday, December 05, 2011, Mark Brown wrote:
It might make sense for it to go via the Samsung tree - the third
patch
On Tue, Dec 6, 2011 at 8:24 AM, Kyungmin Park kmp...@infradead.org wrote:
On 12/6/11, Joerg Roedel joerg.roe...@amd.com wrote:
On Fri, Nov 18, 2011 at 06:47:28PM +0900, KyongHo Cho wrote:
Patch Summary:
[PATCH v7 1/2] ARM: EXYNOS: Change System MMU platform device definitions
[PATCH v7 2/2]
On Tue, Dec 6, 2011 at 8:48 PM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
Hello,
I'm trying to integrate your SYSMMU driver with my DMA-mapping IOMMU
API integration patches. I've noticed some issues, please see my comments
below.
Thank you!
On Friday, November 18, 2011 10:48 AM
On Tue, Dec 6, 2011 at 9:13 PM, KyongHo Cho pullip@samsung.com wrote:
On Tue, Dec 6, 2011 at 8:24 AM, Kyungmin Park kmp...@infradead.org wrote:
On 12/6/11, Joerg Roedel joerg.roe...@amd.com wrote:
On Fri, Nov 18, 2011 at 06:47:28PM +0900, KyongHo Cho wrote:
Patch Summary:
[PATCH v7 1/2]
On Tue, Dec 06, 2011 at 09:13:18PM +0900, KyongHo Cho wrote:
BTW, how do you test it at mainline kernel?
I merged IOMMU mainline branch to our kernel branch and tested it with
our FIMC, MFC, JPEG, 2D.
This is not sufficient. Please do it the other way around, merge your
outstanding changes
On Tue, Dec 6, 2011 at 12:16 AM, Mark Brown
broo...@opensource.wolfsonmicro.com wrote:
I do also think that if we do decide to move more platforms to central
management it's going to be easier to first transition all their drivers
to a repetitive style of clock management and then do a big
Hello,
On Tuesday, December 06, 2011 1:21 PM KyongHo Cho wrote:
On Tue, Dec 6, 2011 at 8:48 PM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
Hello,
I'm trying to integrate your SYSMMU driver with my DMA-mapping IOMMU
API integration patches. I've noticed some issues, please see my
On Tue, Dec 06, 2011 at 01:04:53PM +0100, Marek Szyprowski wrote:
Please fix your mailer to word wrap at less than 80 columns, I've
reflowed your text for legibility.
What about similar patches for S5PV210/S5PC110 series and Exynos4?
I don't really have access to these systems (well, I have a
On Mon, Dec 05, 2011 at 04:47:15PM +0100, Joerg Roedel wrote:
Okay, I merged it into arm/exynos, but it is not pushed yet. Actually
there were conflicts while merging, which I resolved. What I failed
to find is a config for Exynos that actually builds for upstream Linux.
Probably I havn't
On Tuesday, December 06, 2011, Kukjin Kim wrote:
Mark Brown wrote:
On Mon, Dec 05, 2011 at 01:15:18AM +0100, Rafael J. Wysocki wrote:
On Monday, December 05, 2011, Mark Brown wrote:
It might make sense for it to go via the Samsung tree - the third
patch
depends on it and
From: Jaecheol Lee jc@samsung.com
To support various EXYNOS series SoCs commonly,
added exynos common structure.
exynos-cpufreq.c = EXYNOS series common cpufreq driver
exynos4210-cpufreq.c = EXYNOS4210 support cpufreq driver
Signed-off-by: Jaecheol Lee jc@samsung.com
Signed-off-by:
Jingoo Han wrote:
The SMDK board uses LT3591 as backlight LED driver of LTE480WV LCD.
According to the LT3591 datasheet, the switching frequency should
be 1MHz. So, PWM period is calculated by following formula:
PWM period = 1/switching frequency
= 1/1MHz
= 1000ns
23 matches
Mail list logo
