Re: [PATCH v11 0/3] Exynos 5410 support
Tarek Dakhran t.dakh...@gmail.com writes: Hi, On Fri, May 30, 2014 at 7:41 AM, Tushar Behera trbli...@gmail.com wrote: On Thu, May 29, 2014 at 11:30 PM, Andreas Färber afaer...@suse.de wrote: Hi Tarek, And I reproducibly get failures for CPUs 1-3, resulting in only one CPU in /proc/cpuinfo (compared to 4 on downstream 3.14): [0.045778] CPU: Testing write buffer coherency: ok [0.045968] /cpus/cpu@0 missing clock-frequency property [0.045993] /cpus/cpu@1 missing clock-frequency property [0.046016] /cpus/cpu@2 missing clock-frequency property [0.046040] /cpus/cpu@3 missing clock-frequency property [0.046059] CPU0: thread -1, cpu 0, socket 0, mpidr 8000 [0.046135] Setting up static identity map for 0x403a8920 - 0x403a8978 [2.075052] CPU1: failed to come online [4.085095] CPU2: failed to come online [6.095142] CPU3: failed to come online [6.095237] Brought up 1 CPUs [6.095269] SMP: Total of 1 processors activated. [6.095303] CPU: All CPU(s) started in HYP mode. [6.095336] CPU: Virtualization extensions available. I also notice another apparent device tree issue: [7.341814] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' [7.341850] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' Are any of those known issues and being worked on? (The CPU failures affected 5420 Arndale Octa as well iirc.) Can you check after applying following two patches for Arndale-Octa ([1],[2])? In other words, a patch similar to [2] might be required for this board too if it is booting under secure mode. Firmware node already present into exynos5410-smdk5410.dts So with only patch[1] 4xA15 cores will boot on ODROID-XU and SMDK5410. I also confirm that with 4xA15 cores boot when adding patch [1]. Kevin [1] http://www.spinics.net/lists/linux-samsung-soc/msg31776.html [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode [2] http://www.spinics.net/lists/linux-samsung-soc/msg31777.html [PATCH v2 Resend 2/2] ARM: dts: Add secure firmware support for Arndale-octa -- Tushar Behera Best regards, Tarek -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Hi, On Fri, May 30, 2014 at 7:41 AM, Tushar Behera trbli...@gmail.com wrote: On Thu, May 29, 2014 at 11:30 PM, Andreas Färber afaer...@suse.de wrote: Hi Tarek, And I reproducibly get failures for CPUs 1-3, resulting in only one CPU in /proc/cpuinfo (compared to 4 on downstream 3.14): [0.045778] CPU: Testing write buffer coherency: ok [0.045968] /cpus/cpu@0 missing clock-frequency property [0.045993] /cpus/cpu@1 missing clock-frequency property [0.046016] /cpus/cpu@2 missing clock-frequency property [0.046040] /cpus/cpu@3 missing clock-frequency property [0.046059] CPU0: thread -1, cpu 0, socket 0, mpidr 8000 [0.046135] Setting up static identity map for 0x403a8920 - 0x403a8978 [2.075052] CPU1: failed to come online [4.085095] CPU2: failed to come online [6.095142] CPU3: failed to come online [6.095237] Brought up 1 CPUs [6.095269] SMP: Total of 1 processors activated. [6.095303] CPU: All CPU(s) started in HYP mode. [6.095336] CPU: Virtualization extensions available. I also notice another apparent device tree issue: [7.341814] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' [7.341850] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' Are any of those known issues and being worked on? (The CPU failures affected 5420 Arndale Octa as well iirc.) Can you check after applying following two patches for Arndale-Octa ([1],[2])? In other words, a patch similar to [2] might be required for this board too if it is booting under secure mode. Firmware node already present into exynos5410-smdk5410.dts So with only patch[1] 4xA15 cores will boot on ODROID-XU and SMDK5410. [1] http://www.spinics.net/lists/linux-samsung-soc/msg31776.html [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode [2] http://www.spinics.net/lists/linux-samsung-soc/msg31777.html [PATCH v2 Resend 2/2] ARM: dts: Add secure firmware support for Arndale-octa -- Tushar Behera Best regards, Tarek -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Hi all, On Fri, May 30, 2014 at 10:16 PM, Sachin Kamat sachin.ka...@linaro.org wrote: On Friday, 30 May 2014, Tushar Behera trbli...@gmail.com wrote: On Thu, May 29, 2014 at 11:30 PM, Andreas Färber afaer...@suse.de wrote: Hi Tarek, And I reproducibly get failures for CPUs 1-3, resulting in only one CPU in /proc/cpuinfo (compared to 4 on downstream 3.14): [0.045778] CPU: Testing write buffer coherency: ok [0.045968] /cpus/cpu@0 missing clock-frequency property [0.045993] /cpus/cpu@1 missing clock-frequency property [0.046016] /cpus/cpu@2 missing clock-frequency property [0.046040] /cpus/cpu@3 missing clock-frequency property [0.046059] CPU0: thread -1, cpu 0, socket 0, mpidr 8000 [0.046135] Setting up static identity map for 0x403a8920 - 0x403a8978 [2.075052] CPU1: failed to come online [4.085095] CPU2: failed to come online [6.095142] CPU3: failed to come online [6.095237] Brought up 1 CPUs [6.095269] SMP: Total of 1 processors activated. [6.095303] CPU: All CPU(s) started in HYP mode. [6.095336] CPU: Virtualization extensions available. I also notice another apparent device tree issue: [7.341814] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' [7.341850] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' Are any of those known issues and being worked on? (The CPU failures affected 5420 Arndale Octa as well iirc.) [snip] [1] http://www.spinics.net/lists/linux-samsung-soc/msg31776.html [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode [2] http://www.spinics.net/lists/linux-samsung-soc/msg31777.html [PATCH v2 Resend 2/2] ARM: dts: Add secure firmware support for Arndale-octa Kukjin, Can you please apply the above patches? Patches [1], [2] tested on ODROID-XU, SMDK5410 and Arndale Octa boards. Tested-by: Tarek Dakhran t.dakh...@samsung.com Best regards, Tarek -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Hi Tarek and Kevin, Am 27.05.2014 19:06, schrieb Kevin Hilman: Tarek Dakhran t.dakh...@samsung.com writes: The series of patches represent support of Exynos 5410 SoC The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture Patches add new platform description, support of clock controller and device tree for Exynos 5410. Has been build on Samsung Linux Kernel (branch: for-next, commit: 97eae6c Merge branch 'v3.16-next/multiplatform' into for-next) Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) Tested-by: Kevin Hilman khil...@linaro.org FYI, I boot tested this on an odroid-xu (exynos_defconfig and multi_v7_defconfig.) Could you clarify: Are you using exynos5410-smdk5410.dts with the ODROID-XU or do you have some upcoming exynos5410-odroidxu.dts based on exynos5410.dtsi? Thanks, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Hi Andreas, On 05/29/2014 05:36 PM, Andreas Färber wrote: Hi Tarek and Kevin, Am 27.05.2014 19:06, schrieb Kevin Hilman: Tarek Dakhran t.dakh...@samsung.com writes: The series of patches represent support of Exynos 5410 SoC The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture Patches add new platform description, support of clock controller and device tree for Exynos 5410. Has been build on Samsung Linux Kernel (branch: for-next, commit: 97eae6c Merge branch 'v3.16-next/multiplatform' into for-next) Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) Tested-by: Kevin Hilman khil...@linaro.org FYI, I boot tested this on an odroid-xu (exynos_defconfig and multi_v7_defconfig.) Could you clarify: Are you using exynos5410-smdk5410.dts with the ODROID-XU or do you have some upcoming exynos5410-odroidxu.dts based on exynos5410.dtsi? We use exynos5410-smdk5410.dts for booting ODROID-XU. Thanks, Andreas -- Best regards, Tarek Dakhran -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Hi Tarek, [shortening the CC list a bit] Am 29.05.2014 16:46, schrieb Tarek Dakhran: On 05/29/2014 05:36 PM, Andreas Färber wrote: Am 27.05.2014 19:06, schrieb Kevin Hilman: Tarek Dakhran t.dakh...@samsung.com writes: Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) Tested-by: Kevin Hilman khil...@linaro.org FYI, I boot tested this on an odroid-xu (exynos_defconfig and multi_v7_defconfig.) Could you clarify: Are you using exynos5410-smdk5410.dts with the ODROID-XU or do you have some upcoming exynos5410-odroidxu.dts based on exynos5410.dtsi? We use exynos5410-smdk5410.dts for booting ODROID-XU. Thanks a lot for your work! I've successfully booted for-next on ODROID-XU using that .dts and exynos_defconfig plus some systemd and KVM options. Once I got the following panic: [7.579120] Freeing unused kernel memory: 260K (c04f5000 - c0536000) [7.647496] Unhandled fault: asynchronous external abort (0x1211) at 0x [7.659656] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0007 [7.659656] [7.667345] CPU: 0 PID: 1 Comm: init Not tainted 3.15.0-rc4-00074-gca610da #1 [7.674465] [c00218b4] (unwind_backtrace) from [c001eaa4] (show_stack+0x10/0x14) [7.682174] [c001eaa4] (show_stack) from [c03a316c] (dump_stack+0x80/0xc0) [7.689371] [c03a316c] (dump_stack) from [c03a0618] (panic+0xa4/0x200) [7.696222] [c03a0618] (panic) from [c002c79c] (complete_and_exit+0x0/0x1c) [7.703503] [c002c79c] (complete_and_exit) from [0001] (0x1) [7.709844] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0007 [7.709844] And I reproducibly get failures for CPUs 1-3, resulting in only one CPU in /proc/cpuinfo (compared to 4 on downstream 3.14): [0.045778] CPU: Testing write buffer coherency: ok [0.045968] /cpus/cpu@0 missing clock-frequency property [0.045993] /cpus/cpu@1 missing clock-frequency property [0.046016] /cpus/cpu@2 missing clock-frequency property [0.046040] /cpus/cpu@3 missing clock-frequency property [0.046059] CPU0: thread -1, cpu 0, socket 0, mpidr 8000 [0.046135] Setting up static identity map for 0x403a8920 - 0x403a8978 [2.075052] CPU1: failed to come online [4.085095] CPU2: failed to come online [6.095142] CPU3: failed to come online [6.095237] Brought up 1 CPUs [6.095269] SMP: Total of 1 processors activated. [6.095303] CPU: All CPU(s) started in HYP mode. [6.095336] CPU: Virtualization extensions available. I also notice another apparent device tree issue: [7.341814] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' [7.341850] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' Are any of those known issues and being worked on? (The CPU failures affected 5420 Arndale Octa as well iirc.) Some of the low-hanging fruit like no heartbeat/SD LEDs, no RTC, no usb3503 and thus no network I'm already looking into myself. For now I'm putting everything into the SMDK .dts, but I guess we'll need to split off -odroidxu.dts and -pinctrl.dtsi at some point. What about graphics? The 5410 is an oddball in using PowerVR rather than Mali GPU - should a framebuffer on HDMI or DisplayPort work if we add DT nodes, or will the GPU require larger code changes? Cheers, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
On Thu, May 29, 2014 at 11:30 PM, Andreas Färber afaer...@suse.de wrote: Hi Tarek, And I reproducibly get failures for CPUs 1-3, resulting in only one CPU in /proc/cpuinfo (compared to 4 on downstream 3.14): [0.045778] CPU: Testing write buffer coherency: ok [0.045968] /cpus/cpu@0 missing clock-frequency property [0.045993] /cpus/cpu@1 missing clock-frequency property [0.046016] /cpus/cpu@2 missing clock-frequency property [0.046040] /cpus/cpu@3 missing clock-frequency property [0.046059] CPU0: thread -1, cpu 0, socket 0, mpidr 8000 [0.046135] Setting up static identity map for 0x403a8920 - 0x403a8978 [2.075052] CPU1: failed to come online [4.085095] CPU2: failed to come online [6.095142] CPU3: failed to come online [6.095237] Brought up 1 CPUs [6.095269] SMP: Total of 1 processors activated. [6.095303] CPU: All CPU(s) started in HYP mode. [6.095336] CPU: Virtualization extensions available. I also notice another apparent device tree issue: [7.341814] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' [7.341850] of_get_named_gpiod_flags: can't parse gpios property of node '/soc/mmc@1222/slot@0[0]' Are any of those known issues and being worked on? (The CPU failures affected 5420 Arndale Octa as well iirc.) Can you check after applying following two patches for Arndale-Octa ([1],[2])? In other words, a patch similar to [2] might be required for this board too if it is booting under secure mode. [1] http://www.spinics.net/lists/linux-samsung-soc/msg31776.html [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode [2] http://www.spinics.net/lists/linux-samsung-soc/msg31777.html [PATCH v2 Resend 2/2] ARM: dts: Add secure firmware support for Arndale-octa -- Tushar Behera -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Hi Andreas, On 29.05.2014 20:00, Andreas Färber wrote: [snip] Some of the low-hanging fruit like no heartbeat/SD LEDs, no RTC, no usb3503 and thus no network I'm already looking into myself. For now I'm putting everything into the SMDK .dts, but I guess we'll need to split off -odroidxu.dts and -pinctrl.dtsi at some point. Odroid XU needs its own dts for sure. I think you can make a copy of SMDK dts and name it -odroidxu straightaway and work further with it. exynos5410-pinctrl.dtsi is used for generic SoC-wide pinctrl definitions, such as pin banks and pin groups. There should be no board-specific things defined in it. Instead respective board dts should have them. What about graphics? The 5410 is an oddball in using PowerVR rather than Mali GPU - should a framebuffer on HDMI or DisplayPort work if we add DT nodes, or will the GPU require larger code changes? The 3D GPU is completely independent from display controllers, which are standard Samsung IP blocks, so you should be able to get unaccelerated output using VP+Mixer+HDMI or FIMD+DP using existing drivers. Best regards, Tomasz -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Tarek Dakhran t.dakh...@samsung.com writes: The series of patches represent support of Exynos 5410 SoC The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture Patches add new platform description, support of clock controller and device tree for Exynos 5410. Has been build on Samsung Linux Kernel (branch: for-next, commit: 97eae6c Merge branch 'v3.16-next/multiplatform' into for-next) Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) Tested-by: Kevin Hilman khil...@linaro.org FYI, I boot tested this on an odroid-xu (exynos_defconfig and multi_v7_defconfig.) Kevin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Kevin Hilman khil...@linaro.org writes: Tarek Dakhran t.dakh...@samsung.com writes: The series of patches represent support of Exynos 5410 SoC The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture Patches add new platform description, support of clock controller and device tree for Exynos 5410. Has been build on Samsung Linux Kernel (branch: for-next, commit: 97eae6c Merge branch 'v3.16-next/multiplatform' into for-next) Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) Tested-by: Kevin Hilman khil...@linaro.org FYI, I boot tested this on an odroid-xu (exynos_defconfig and multi_v7_defconfig.) Oops, I may have spoke to soon. There seem to be some problems with multi_v7_defconfig. Applying this series directly on the commit mentioned above and testing, it works just fine using multi_v7_defconfig. However, if I directly test the current contents of the samsung for-next branch (where this series has been merged) it no longer boots on the odroid-xu. A quick diff shows that there are some other changes to multi_v7_defconfig in the samsung/for-next branch that may be causing problems here. Kevin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Hi, On Tue, May 27, 2014 at 9:44 PM, Kevin Hilman khil...@linaro.org wrote: Kevin Hilman khil...@linaro.org writes: Tarek Dakhran t.dakh...@samsung.com writes: The series of patches represent support of Exynos 5410 SoC The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture Patches add new platform description, support of clock controller and device tree for Exynos 5410. Has been build on Samsung Linux Kernel (branch: for-next, commit: 97eae6c Merge branch 'v3.16-next/multiplatform' into for-next) Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) Tested-by: Kevin Hilman khil...@linaro.org FYI, I boot tested this on an odroid-xu (exynos_defconfig and multi_v7_defconfig.) Oops, I may have spoke to soon. There seem to be some problems with multi_v7_defconfig. Applying this series directly on the commit mentioned above and testing, it works just fine using multi_v7_defconfig. Thank you for testing. However, if I directly test the current contents of the samsung for-next branch (where this series has been merged) it no longer boots on the odroid-xu. A quick diff shows that there are some other changes to multi_v7_defconfig in the samsung/for-next branch that may be causing problems here. Yes. Right you are. There is no ARCH_EXYNOS defined in multi_v7_defconfig at current state (branch: for-next commit: ca610da Merge branch 'v3.16-next/dt-samsung-3' into for-next). So booting kernel on 5410 SoC is not possible with multi_v7_defconfig. Please use exynos_defconfig. Kevin Best regards, Tarek -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
On 27.05.2014 22:17, Tarek Dakhran wrote: Hi, On Tue, May 27, 2014 at 9:44 PM, Kevin Hilman khil...@linaro.org wrote: Kevin Hilman khil...@linaro.org writes: Tarek Dakhran t.dakh...@samsung.com writes: The series of patches represent support of Exynos 5410 SoC The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture Patches add new platform description, support of clock controller and device tree for Exynos 5410. Has been build on Samsung Linux Kernel (branch: for-next, commit: 97eae6c Merge branch 'v3.16-next/multiplatform' into for-next) Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) Tested-by: Kevin Hilman khil...@linaro.org FYI, I boot tested this on an odroid-xu (exynos_defconfig and multi_v7_defconfig.) Oops, I may have spoke to soon. There seem to be some problems with multi_v7_defconfig. Applying this series directly on the commit mentioned above and testing, it works just fine using multi_v7_defconfig. Thank you for testing. However, if I directly test the current contents of the samsung for-next branch (where this series has been merged) it no longer boots on the odroid-xu. A quick diff shows that there are some other changes to multi_v7_defconfig in the samsung/for-next branch that may be causing problems here. Yes. Right you are. There is no ARCH_EXYNOS defined in multi_v7_defconfig at current state (branch: for-next commit: ca610da Merge branch 'v3.16-next/dt-samsung-3' into for-next). So booting kernel on 5410 SoC is not possible with multi_v7_defconfig. Please use exynos_defconfig. I wonder if this patch isn't maybe the missing part: http://thread.gmane.org/gmane.linux.kernel.samsung-soc/32414 Olof asked Kukjin to separate it from his pull requests, so it can be applied directly to ARM SoC tree to avoid conflicts. Best regards, Tomasz -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
Hi, On 26.05.2014 05:23, Tarek Dakhran wrote: The series of patches represent support of Exynos 5410 SoC The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture Patches add new platform description, support of clock controller and device tree for Exynos 5410. Has been build on Samsung Linux Kernel (branch: for-next, commit: 97eae6c Merge branch 'v3.16-next/multiplatform' into for-next) Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) I hope this is clean and would be applied. Tarek. Tarek Dakhran (3): ARM: EXYNOS: Add support for EXYNOS5410 SoC clk: exynos5410: register clocks using common clock framework ARM: dts: Add initial device tree support for EXYNOS5410 .../devicetree/bindings/clock/exynos5410-clock.txt | 45 + arch/arm/boot/dts/Makefile |1 + arch/arm/boot/dts/exynos5410-smdk5410.dts | 82 arch/arm/boot/dts/exynos5410.dtsi | 206 +++ arch/arm/mach-exynos/Kconfig |5 + arch/arm/mach-exynos/common.h | 12 +- drivers/clk/samsung/Makefile |1 + drivers/clk/samsung/clk-exynos5410.c | 209 include/dt-bindings/clock/exynos5410.h | 33 9 files changed, 592 insertions(+), 2 deletions(-) create mode 100644 Documentation/devicetree/bindings/clock/exynos5410-clock.txt create mode 100644 arch/arm/boot/dts/exynos5410-smdk5410.dts create mode 100644 arch/arm/boot/dts/exynos5410.dtsi create mode 100644 drivers/clk/samsung/clk-exynos5410.c create mode 100644 include/dt-bindings/clock/exynos5410.h Reviewed-by: Tomasz Figa t.f...@samsung.com Best regards, Tomasz -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v11 0/3] Exynos 5410 support
On 05/26/14 20:11, Tomasz Figa wrote: Hi, Hi On 26.05.2014 05:23, Tarek Dakhran wrote: The series of patches represent support of Exynos 5410 SoC The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture Patches add new platform description, support of clock controller and device tree for Exynos 5410. Has been build on Samsung Linux Kernel (branch: for-next, commit: 97eae6c Merge branch 'v3.16-next/multiplatform' into for-next) Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) Thanks for your test with exynos_defconfig and multi_v7_defconfig. I hope this is clean and would be applied. Tarek. Tarek Dakhran (3): ARM: EXYNOS: Add support for EXYNOS5410 SoC clk: exynos5410: register clocks using common clock framework ARM: dts: Add initial device tree support for EXYNOS5410 .../devicetree/bindings/clock/exynos5410-clock.txt | 45 + arch/arm/boot/dts/Makefile |1 + arch/arm/boot/dts/exynos5410-smdk5410.dts | 82 arch/arm/boot/dts/exynos5410.dtsi | 206 +++ arch/arm/mach-exynos/Kconfig |5 + arch/arm/mach-exynos/common.h | 12 +- drivers/clk/samsung/Makefile |1 + drivers/clk/samsung/clk-exynos5410.c | 209 include/dt-bindings/clock/exynos5410.h | 33 9 files changed, 592 insertions(+), 2 deletions(-) create mode 100644 Documentation/devicetree/bindings/clock/exynos5410-clock.txt create mode 100644 arch/arm/boot/dts/exynos5410-smdk5410.dts create mode 100644 arch/arm/boot/dts/exynos5410.dtsi create mode 100644 drivers/clk/samsung/clk-exynos5410.c create mode 100644 include/dt-bindings/clock/exynos5410.h Reviewed-by: Tomasz Figat.f...@samsung.com Applied this whole series. Thanks, Kukjin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v11 0/3] Exynos 5410 support
The series of patches represent support of Exynos 5410 SoC The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture Patches add new platform description, support of clock controller and device tree for Exynos 5410. Has been build on Samsung Linux Kernel (branch: for-next, commit: 97eae6c Merge branch 'v3.16-next/multiplatform' into for-next) Has been tested on: 1) Exynos 5410 reference board (exynos_defconfig) 2) Exynos 5410 reference board (multi_v7_defconfig) 3) Odroid-XU board (exynos_defconfig) 4) Odroid-XU board (multi_v7_defconfig) I hope this is clean and would be applied. Tarek. Tarek Dakhran (3): ARM: EXYNOS: Add support for EXYNOS5410 SoC clk: exynos5410: register clocks using common clock framework ARM: dts: Add initial device tree support for EXYNOS5410 .../devicetree/bindings/clock/exynos5410-clock.txt | 45 + arch/arm/boot/dts/Makefile |1 + arch/arm/boot/dts/exynos5410-smdk5410.dts | 82 arch/arm/boot/dts/exynos5410.dtsi | 206 +++ arch/arm/mach-exynos/Kconfig |5 + arch/arm/mach-exynos/common.h | 12 +- drivers/clk/samsung/Makefile |1 + drivers/clk/samsung/clk-exynos5410.c | 209 include/dt-bindings/clock/exynos5410.h | 33 9 files changed, 592 insertions(+), 2 deletions(-) create mode 100644 Documentation/devicetree/bindings/clock/exynos5410-clock.txt create mode 100644 arch/arm/boot/dts/exynos5410-smdk5410.dts create mode 100644 arch/arm/boot/dts/exynos5410.dtsi create mode 100644 drivers/clk/samsung/clk-exynos5410.c create mode 100644 include/dt-bindings/clock/exynos5410.h -- 1.7.9.5 -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
