Re: [PATCHv3 0/7] Support new Exynos3250 SoC based on Cortex-A7 dual core

From: Chanwoo Choi
Date: Sun Apr 20 2014 - 21:11:17 EST


Dear Kukjin,

Please review this patchset for Exynos3250 SoC.

Best Regards,
Chanwoo Choi

On 04/18/2014 10:15 AM, Chanwoo Choi wrote:
> This patchset support new Exynos3250 Samsung SoC based on Cortex-A7 dual core.
> Exynos3250 is a System-On-Chip (SoC) that is based on 32-bit RISC processor
> for Smartphone. It is desigend with the 28nm low-power high-K metal gate process
> and provides the best performance features.
>
> This patchset include some patches such as:
> - Support secondary CPU of Exynos3250 (cpu up/down)
> - Supoort uart/mct/adc/gic/i2c/spi/power-domain/pmu/mshc/pwm/amba
> - Support the clock control for Exynos3250 using common clk framework
>
> This patchset is based on following git repo/branch.
> - git repo : git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> - branch : for-next (Linux 3.15-rc1)
>
> Additional patch description about static memory mapping:
> This patchset must need to map memory mapping about SYSRAM/PMU for CPU UP/DOWN.
> So, this patchset need to merge following patchset to remove static memory
> mapping for SYSRAM[1] / PMU ([2] or [3]).
>
> [1] http://www.spinics.net/lists/arm-kernel/msg323011.html
> [2] https://lkml.org/lkml/2014/4/2/48
> [3] http://www.spinics.net/lists/arm-kernel/msg316013.html
>
> And,
> The pinctrl patch for Exynos3250 was posted as separated patch[4].
> [4] https://lkml.org/lkml/2014/4/13/156
>
> Changes from v2:
> - Remove static memory mapping about SYSRAM/PMU such as following patches:
> ARM: EXYNOS: Add IO mapping for non-secure SYSRAM of Exynos3250
> ARM: EXYNOS: Add IO mapping for PMU of Exynos3250
> - Add description for secondary CPU boot of Exynos4212/Exynos3250
> - Fix description in exynos_cpu_die() to remove particular SoC series
> - Fix minor coding style
> - Add documentation for Exynos3250 clock controller
>
> Changes from v1:
> - Add new "samsung,exynos3" compatible name
> - Add comment about exynos_cpu_boot in Exynos4212
> - Remove unnecessary 'goto' statement in firmware.c
> - Use read_cpuid_part_number() function instead of assembler directly
> - Post separated pinctrl patch from this patchset
> : https://lkml.org/lkml/2014/4/13/156
> - Remove unused pmu interrupts due to Exynos3250 dual-core
> - Cosolidate all the patches related to exynos3250.dtsi into one patch
> - Fix gic compatible name to "cortex-a15-gic" because Cortex-A7 GIC is same
> - Add sign-off of sender to all this patches
> - Fix minor typo
>
> Chanwoo Choi (4):
> ARM: EXYNOS: Add Exynos3250 SoC ID
> ARM: EXYNOS: Support secondary CPU boot of Exynos3250
> ARM: EXYNOS: Enter a15 lowpower mode for Exynos3250 based on Cortex-a7
> dt-bindings: add documentation for Exynos3250 clock controller
>
> Kyungmin Park (1):
> ARM: EXYNOS: Support secondary CPU boot of Exynos4212
>
> Tomasz Figa (2):
> clk: samsung: exynos3250: Add clocks using common clock framework
> ARM: dts: Add device tree sources for Exynos3250
>
> .../devicetree/bindings/clock/exynos3250-clock.txt | 41 ++
> arch/arm/boot/dts/exynos3250-pinctrl.dtsi | 477 +++++++++++++
> arch/arm/boot/dts/exynos3250.dtsi | 427 +++++++++++
> arch/arm/mach-exynos/Kconfig | 22 +
> arch/arm/mach-exynos/exynos.c | 2 +
> arch/arm/mach-exynos/firmware.c | 21 +-
> arch/arm/mach-exynos/hotplug.c | 19 +-
> arch/arm/plat-samsung/include/plat/cpu.h | 10 +
> drivers/clk/samsung/Makefile | 1 +
> drivers/clk/samsung/clk-exynos3250.c | 785 +++++++++++++++++++++
> include/dt-bindings/clock/exynos3250.h | 256 +++++++
> 11 files changed, 2053 insertions(+), 8 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/clock/exynos3250-clock.txt
> create mode 100644 arch/arm/boot/dts/exynos3250-pinctrl.dtsi
> create mode 100644 arch/arm/boot/dts/exynos3250.dtsi
> create mode 100644 drivers/clk/samsung/clk-exynos3250.c
> create mode 100644 include/dt-bindings/clock/exynos3250.h
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/