date:20110817

[PATCH] ARM: EXYNOS4: ADD USB EHCI device to SMDKV310

2011-08-17 Thread Sachin Kamat

Signed-off-by: Bhuvana Kakunoori bhuvana.kakuno...@linaro.org
Signed-off-by: Pankaj Dubey pankaj.du...@samsung.com
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
 arch/arm/mach-exynos4/Kconfig |2 ++
 arch/arm/mach-exynos4/mach-smdkv310.c |   16 
 2 files changed, 18 insertions(+), 0 deletions(-)

diff --git a/arch/arm/mach-exynos4/Kconfig b/arch/arm/mach-exynos4/Kconfig
index bb29d51..cc97d23 100644
--- a/arch/arm/mach-exynos4/Kconfig
+++ b/arch/arm/mach-exynos4/Kconfig
@@ -136,6 +136,7 @@ config MACH_SMDKV310
bool SMDKV310
select CPU_EXYNOS4210
select S5P_DEV_FIMD0
+   select S5P_DEV_USB_EHCI
select S3C_DEV_RTC
select S3C_DEV_WDT
select S3C_DEV_I2C1
@@ -151,6 +152,7 @@ config MACH_SMDKV310
select SAMSUNG_DEV_PWM
select EXYNOS4_DEV_SYSMMU
select EXYNOS4_SETUP_FIMD0
+   select EXYNOS4_SETUP_USB_PHY
select EXYNOS4_SETUP_I2C1
select EXYNOS4_SETUP_KEYPAD
select EXYNOS4_SETUP_SDHCI
diff --git a/arch/arm/mach-exynos4/mach-smdkv310.c 
b/arch/arm/mach-exynos4/mach-smdkv310.c
index 5f62b2b..b6c28ea 100644
--- a/arch/arm/mach-exynos4/mach-smdkv310.c
+++ b/arch/arm/mach-exynos4/mach-smdkv310.c
@@ -33,6 +33,8 @@
 #include plat/gpio-cfg.h
 #include plat/backlight.h
 #include plat/mfc.h
+#include plat/ehci.h
+#include plat/clock.h
 
 #include mach/map.h
 
@@ -167,6 +169,16 @@ static struct i2c_board_info i2c_devs1[] __initdata = {
{I2C_BOARD_INFO(wm8994, 0x1a),},
 };
 
+/* USB EHCI */
+static struct s5p_ehci_platdata smdkv310_ehci_pdata;
+
+static void __init smdkv310_ehci_init(void)
+{
+   struct s5p_ehci_platdata *pdata = smdkv310_ehci_pdata;
+
+   s5p_ehci_set_platdata(pdata);
+}
+
 static struct platform_device *smdkv310_devices[] __initdata = {
s3c_device_hsmmc0,
s3c_device_hsmmc1,
@@ -175,6 +187,7 @@ static struct platform_device *smdkv310_devices[] 
__initdata = {
s3c_device_i2c1,
s3c_device_rtc,
s3c_device_wdt,
+   s5p_device_ehci,
exynos4_device_ac97,
exynos4_device_i2s0,
samsung_device_keypad,
@@ -258,6 +271,9 @@ static void __init smdkv310_machine_init(void)
 
samsung_bl_set(smdkv310_bl_gpio_info, smdkv310_bl_data);
 
+   smdkv310_ehci_init();
+   clk_xusbxti.rate = 2400;
+
platform_add_devices(smdkv310_devices, ARRAY_SIZE(smdkv310_devices));
s5p_device_mfc.dev.parent = exynos4_device_pd[PD_MFC].dev;
 }
-- 
1.7.4.1


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

[PATCH] ARM: EXYNOS4: Enable system MMU support on Origen

2011-08-17 Thread Sachin Kamat

Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
 arch/arm/mach-exynos4/Kconfig   |1 +
 arch/arm/mach-exynos4/mach-origen.c |1 +
 2 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/arch/arm/mach-exynos4/Kconfig b/arch/arm/mach-exynos4/Kconfig
index 3ab0f18..bdb76e2 100644
--- a/arch/arm/mach-exynos4/Kconfig
+++ b/arch/arm/mach-exynos4/Kconfig
@@ -192,6 +192,7 @@ config MACH_ORIGEN
select S3C_DEV_RTC
select S3C_DEV_WDT
select S3C_DEV_HSMMC2
+   select EXYNOS4_DEV_SYSMMU
select EXYNOS4_SETUP_SDHCI
help
  Machine support for ORIGEN based on Samsung EXYNOS4210
diff --git a/arch/arm/mach-exynos4/mach-origen.c 
b/arch/arm/mach-exynos4/mach-origen.c
index ed59f86..d04f7ee 100644
--- a/arch/arm/mach-exynos4/mach-origen.c
+++ b/arch/arm/mach-exynos4/mach-origen.c
@@ -83,6 +83,7 @@ static struct platform_device *origen_devices[] __initdata = {
s3c_device_hsmmc2,
s3c_device_rtc,
s3c_device_wdt,
+   exynos4_device_sysmmu,
 };
 
 static void __init origen_map_io(void)
-- 
1.7.4.1


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Need help on Parameterized Trigger Plugin of Jenkins

2011-08-17 Thread Deepti Kalakeri

On Wed, Aug 17, 2011 at 4:05 AM, Michael Hudson-Doyle
michael.hud...@canonical.com wrote:

On Tue, 16 Aug 2011 20:47:33 +0530, Deepti Kalakeri
deepti.kalak...@linaro.org wrote:
On Tue, Aug 16, 2011 at 8:15 PM, James Westby james.wes...@linaro.org
wrote:

On Tue, 16 Aug 2011 18:02:02 +0530, Deepti Kalakeri
deepti.kalak...@linaro.org wrote:
Hello,

I am using jenkins for continuous integration work.
I have a requirement where I need to trigger a job as part of the
post
build
step of a job.
For example I have a job to build a source and I would like to
trigger
the
job that tests the binaries as part of the post build step.
Although I am aware how to trigger a job in the post build step I am
failing
to understand how to pass
certain parameters[ information that the next job needs to know to
execute]
to the next job.
I came across the Parameterized Trigger Plugin

https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin
but
it does not explain how to access the parameters passed in the new
job.

Can someone help me with this ?

Hi,

https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin?focusedCommentId=47087758#comment-47087758

states that the downstream job just sees the values as environment
variables.

What do you want to do with parameters that are passed?

I need to capture the name of the new hardware pack that is built to be
used
further down for testing.
Right now I am using a file to write this information and then in the
testing job I read this file.

Any suggestion or alternative?

I think the Parameters from properties file option might be what you
want? It seems to me that your first job should create a file in its
workspace that contains

46 matches

Mail list logo