arm: vf610: Add Freescale Vybrid VF610 CPU and VF610TWR board support
Subsystems (5)
v4 cover arm: vf610: Add Freescale Vybrid VF610 CPU and VF610TWR board support
This series contain the support for Freescale Vybrid VF610 CPU and VF610TWR board.
Vybird devices are built on an asymmetrical-multiprocessing architecture using ARM cores. The families in the Vybrid portfolio span entry-level, single core Cortex-A class SoCs all the way to dual heterogeneous core SoCs with multiple communication and connectivity options.
Part of the Vybrid platform, VF610 is a dual-core eMPU combining the ARM Cortex A5 and Cortex M4 cores.
VF610 shares some IPs with i.MX family, such as FEC,ESDHC,WATCHDOG,I2C,ASRC and ESAI. VF610 also shares some IPs with ColdFire family, such as eDMA and DSPI. VF610 still has its own IPs, such as PIT,SAI,UART,QSPI and DCU.
More documents for this soc can be found at:
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=VF6xx&fsrch=1&sr=5
http://www.freescale.com/webapp/sps/site/homepage.jsp?code=VYBRID
To align with the description in the above documents, "VF610" is used as the SoC name instead of "MVF600".
The u-boot runs on Cortex A5 core.
Changes in v4:
- Rename "MVF600" to "VF610"
- Define PAD_CTL_PUS_47K_UP and PAD_CTL_PUS_100K_UP with PAD_CTL_PUE enabled
- Reorganize the definitions
- Correct the spaces and tabs
- Rename mvf_pins.h to iomux-vf610.h
- Add README.vf610 about fuse assignments for MAC addresses
- Rename directory name 'mvf600' to 'vf610'
- Rename directory 'arch-mvf600' to 'arch-vf610'
- Add Vybrid VF610 to mxc_ocotp document
- Rename directory name 'mvf600twr' to 'vf610twr'
- Rename mvf600twr.h to vf610twr.h
- Use NEW_PAD_CTRL instead of MUX_PAD_CTRL
- Remove CONFIG_ETHPRIME option
- Add CONFIG_CMD_MEMSET option
Changes in v3:
- Rename the common functions and enums
- Move the structure definitions to imx-regs.h
- Define PAD_CTL_PUE with PKE enabled
- Remove the changes for FEC_RCNTRL_RGMII / FEC_RCNTRL_RMII / FEC_RCNTRL_MII_MODE bits, as they are already set in fec_reg_setup()
- Replace BOOT_FROM by BOOT_OFFSET
- Enable CONFIG_OF_LIBFDT option
- Add useful define instead of raw number
- Use clrsetbits_le32 to set the single bits
- Move setup_iomux_enet() to board_early_init_f and remove board_eth_init()
- Remove redundant define
- Move CONFIG_IOMUX_SHARE_CONF_REG to imx-regs.h
Changes in v2:
- Remove vybrid-common directory
- Rename directory name 'vybrid' to 'mvf600'
- Add generic.c file
- Rewrite get_reset_cause() to make it readable
- Remove reset_cpu(), and use the function in imx_watchdog.c
- Rewrite timer.c file
- Use vybrid_get_clock(VYBRID_UART_CLK) instead of vybrid_get_uartclk()
- Remove lowlevel_init.S, and add clock_init() in board_early_init_f()
- Remove useless CONFIG_SYS_ defines
- Move CONFIG_MACH_TYPE to board configuration file
- Define C structures and access C structures to set/read registers
- Remove useless errata
- Remove useless macros
- Rename directory 'arch-vybrid' to 'arch-mvf600'
- Use common iomux-v3 code
- Use common FEC driver fec_mxc.c
- Add watchdog support
- Add an entry to MAINTAINERS file
- Rename directory name 'vybird' to 'mvf600twr'
- Use standard method to set gd->ram_size
- Rewrite board_mmc_getcd() function
- Remove useless undef
- Remove hardcoded IP addresses and MAC addresses
- Move CONFIG_MACH_TYPE to board configuration file
----------------------------------------------------------------
Alison Wang (7):
arm: vf610: Add IOMUX support for Vybrid VF610
arm: vf610: Add Vybrid VF610 CPU support
net: fec_mxc: Add support for Vybrid VF610
arm: vf610: Add watchdog support for Vybrid VF610
arm: vf610: Add uart support for Vybrid VF610
arm: vf610: Add Vybrid VF610 to mxc_ocotp document
arm: vf610: Add basic support for Vybrid VF610TWR board
MAINTAINERS | 4 + Makefile | 2 +- arch/arm/cpu/armv7/vf610/Makefile | 42 +++++++++++ arch/arm/cpu/armv7/vf610/generic.c | 324 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ arch/arm/cpu/armv7/vf610/timer.c | 103 ++++++++++++++++++++++++++ arch/arm/imx-common/Makefile | 2 +- arch/arm/imx-common/iomux-v3.c | 6 ++ arch/arm/include/asm/arch-vf610/clock.h | 39 ++++++++++ arch/arm/include/asm/arch-vf610/crm_regs.h | 225 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ arch/arm/include/asm/arch-vf610/imx-regs.h | 419 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ arch/arm/include/asm/arch-vf610/iomux-vf610.h | 101 +++++++++++++++++++++++++ arch/arm/include/asm/imx-common/iomux-v3.h | 18 +++++ board/freescale/vf610twr/Makefile | 39 ++++++++++ board/freescale/vf610twr/imximage.cfg | 33 +++++++++ board/freescale/vf610twr/vf610twr.c | 410 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ boards.cfg | 1 + doc/README.mxc_ocotp | 1 + doc/README.vf610 | 10 +++ drivers/net/fec_mxc.c | 4 +- drivers/serial/Makefile | 1 + drivers/serial/serial_lpuart.c | 132 +++++++++++++++++++++++++++++++++ drivers/watchdog/Makefile | 2 +- include/configs/vf610twr.h | 140 +++++++++++++++++++++++++++++++++++ 23 files changed, 2052 insertions(+), 6 deletions(-) create mode 100644 arch/arm/cpu/armv7/vf610/Makefile create mode 100644 arch/arm/cpu/armv7/vf610/generic.c create mode 100644 arch/arm/cpu/armv7/vf610/timer.c create mode 100644 arch/arm/include/asm/arch-vf610/clock.h create mode 100644 arch/arm/include/asm/arch-vf610/crm_regs.h create mode 100644 arch/arm/include/asm/arch-vf610/imx-regs.h create mode 100644 arch/arm/include/asm/arch-vf610/iomux-vf610.h create mode 100644 board/freescale/vf610twr/Makefile create mode 100644 board/freescale/vf610twr/imximage.cfg create mode 100644 board/freescale/vf610twr/vf610twr.c create mode 100644 doc/README.vf610 create mode 100644 drivers/serial/serial_lpuart.c create mode 100644 include/configs/vf610twr.h
PATCH v4 1/7 arm: vf610: Add IOMUX support for Vybrid VF610
This patch adds the IOMUX support for Vybrid VF610 platform.
There is a little difference for IOMUXC module between VF610 and i.MX platform, the muxmode and pad configuration share one 32bit register on VF610, but they are two independent registers on I.MX platform. A CONFIG_IOMUX_SHARE_CONFIG_REG was introduced to fit this difference.
---
Changes in v4:
- Rename "MVF600" to "VF610"
- Define PAD_CTL_PUS_47K_UP and PAD_CTL_PUS_100K_UP with PAD_CTL_PUE enabled
- Reorganize the definitions
- Correct the spaces and tabs
Changes in v3:
- Define PAD_CTL_PUE with PKE enabled
Changes in v2:
- Use common iomux-v3 code
arch/arm/imx-common/Makefile | 2 +- arch/arm/imx-common/iomux-v3.c | 6 ++++++ arch/arm/include/asm/imx-common/iomux-v3.h | 18 ++++++++++++++++++ 3 files changed, 25 insertions(+), 1 deletion(-)
arch/arm/imx-common/Makefile +1 -1
@@ -27,7 +27,7 @@ include $(TOPDIR)/config.mk LIB = $(obj)libimx-common.o -ifeq ($(SOC),$(filter $(SOC),mx25 mx35 mx5 mx6)) +ifeq ($(SOC),$(filter $(SOC),mx25 mx35 mx5 mx6 vf610)) COBJS-y = iomux-v3.o endif ifeq ($(SOC),$(filter $(SOC),mx5 mx6))
arch/arm/imx-common/iomux-v3.c +6 -0
@@ -48,8 +48,14 @@ void imx_iomux_v3_setup_pad(iomux_v3_cfg_t pad)if (sel_input_ofs)__raw_writel (sel_input, base + sel_input_ofs); +#ifdef CONFIG_IOMUX_SHARE_CONF_REG +if (!(pad_ctrl &NO_PAD_CTRL )) +__raw_writel ((mux_mode <<PAD_MUX_MODE_SHIFT ) | pad_ctrl, + base + pad_ctrl_ofs); +#else if (!(pad_ctrl &NO_PAD_CTRL ) && pad_ctrl_ofs)__raw_writel (pad_ctrl, base + pad_ctrl_ofs); +#endif } void imx_iomux_v3_setup_multiple_pads(iomux_v3_cfg_t const *pad_list,
arch/arm/include/asm/imx-common/iomux-v3.h +18 -0
@@ -121,6 +121,24 @@ typedef u64 iomux_v3_cfg_t;#define PAD_CTL_DSE_40ohm (6 << 3)#define PAD_CTL_DSE_34ohm (7 << 3) +#elif defined(CONFIG_VF610 ) + +#define PAD_MUX_MODE_SHIFT 20 + +#define PAD_CTL_SPEED_MED (1 << 12) +#define PAD_CTL_SPEED_HIGH (3 << 12) + +#define PAD_CTL_DSE_50ohm (3 << 6) +#define PAD_CTL_DSE_25ohm (6 << 6) +#define PAD_CTL_DSE_20ohm (7 << 6) + +#define PAD_CTL_PUS_47K_UP (1 << 4 | PAD_CTL_PUE) +#define PAD_CTL_PUS_100K_UP (2 << 4 | PAD_CTL_PUE) +#define PAD_CTL_PKE (1 << 3) +#define PAD_CTL_PUE (1 << 2 | PAD_CTL_PKE) + +#define PAD_CTL_OBE_IBE_ENABLE (3 << 0) +#else #define PAD_CTL_DVS (1 << 13)
Signature · 1 line
1.8.0
PATCH v4 1/7 arm: vf610: Add IOMUX support for Vybrid VF610
Hi Alison,
Quoted 8 lines · Alison Wang
This patch adds the IOMUX support for Vybrid VF610 platform.
There is a little difference for IOMUXC module between VF610 and i.MX platform, the muxmode and pad configuration share one 32bit register on VF610, but they are two independent registers on I.MX platform. A
CONFIG_IOMUX_SHARE_CONFIG_REGwas introduced to fit this difference.Signed-off-by Alison Wang <[email protected]>
[...]
arch/arm/imx-common/iomux-v3.c void imx_iomux_v3_setup_pad(iomux_v3_cfg_t pad) · line 51
Quoted 9 lines
arch/arm/imx-common/iomux-v3.c +1
-0@@ -48,8 +48,14 @@ void imx_iomux_v3_setup_pad(iomux_v3_cfg_t pad)if (sel_input_ofs)__raw_writel (sel_input, base + sel_input_ofs); +#ifdef CONFIG_IOMUX_SHARE_CONF_REG
Where is this one defined? I don't see it in include/configs/vf610twr.h.
Why not use "#ifdef CONFIG_VF610" since this is a platform-dependent code, and not a board-specific config option?
arch/arm/imx-common/iomux-v3.c void imx_iomux_v3_setup_pad(iomux_v3_cfg_t pad) · line 61
Quoted 10 lines
arch/arm/imx-common/iomux-v3.c +5
-0+if (!(pad_ctrl &NO_PAD_CTRL )) +__raw_writel ((mux_mode <<PAD_MUX_MODE_SHIFT ) | pad_ctrl, + base + pad_ctrl_ofs); +#else if (!(pad_ctrl &NO_PAD_CTRL ) && pad_ctrl_ofs)__raw_writel (pad_ctrl, base + pad_ctrl_ofs); +#endif } void imx_iomux_v3_setup_multiple_pads(iomux_v3_cfg_t const *pad_list,
[...]
Apart from that, this patch is OK.
Best regards,
Beno?t
PATCH v4 1/7 arm: vf610: Add IOMUX support for Vybrid VF610
Hi, Benoit,
Quoted 8 lines
Quoted 8 lines
(quoted diff) +0
-0
b/arch/arm/imx-common/iomux-v3.cindex 7fe5ce7..35880c7 100644arch/arm/imx-common/iomux-v3.c +0
-0@@ -48,8 +48,14 @@ void imx_iomux_v3_setup_pad(iomux_v3_cfg_t pad)if (sel_input_ofs)__raw_writel (sel_input, base + sel_input_ofs);
Quoted 4 lines
arch/arm/imx-common/iomux-v3.c void imx_iomux_v3_setup_pad(iomux_v3_cfg_t pad) · line 51
Quoted 1 line
arch/arm/imx-common/iomux-v3.c +1
-0+#ifdef CONFIG_IOMUX_SHARE_CONF_REG Where is this one defined? I don't see it in
include/configs/vf610twr.h.
[Alison Wang] CONFIG_IOMUX_SHARE_CONF_REG is defined in arch/arm/include/asm/arch-vf610/imx-regs.h. Because this is not a board configuration, it is related to the SOC.
Please refer to Stefano's comments below which also could be found in the email on May 15th.
Review
Quoted 3 lines · Stefano
(quoted diff) +3
-0+ +/* MUX mode and PAD ctrl are in one register */ +#define CONFIG_IOMUX_SHARE_CONF_REG
NAK. This is not a board configuration, it is related to the SOC. This setup should flow into the related imx-regs.h for this SOC. When you set CONFIG_MVF600, this value should be set automatically.
Quoted 2 lines
Why not use "#ifdef
CONFIG_VF610" since this is a platform-dependent code, and not a board-specific config option?
[Alison Wang] I use this CONFIG_IOMUX_SHARE_CONF_REG option, because this part of codes
not only could be used on VF610 platform, but also could be used on VF620 or other platforms. When it is used on VF620 or others, you could just enable CONFIG_IOMUX_SHARE_CONF_REG
in the related imx-regs.h.
Otherwise, if "ifdef CONFIG_VF610" is used, you need to add "#if defined(CONFIG_VF610) || defined(CONFIG_VF620)" When this part of codes is also used on VF620. Then when this part of codes is used on VF630 too, this line will be very very long.
Quoted 10 lines
Quoted 10 lines
arch/arm/imx-common/iomux-v3.c +5
-0+if (!(pad_ctrl &NO_PAD_CTRL )) +__raw_writel ((mux_mode <<PAD_MUX_MODE_SHIFT ) | pad_ctrl, + base + pad_ctrl_ofs); +#else if (!(pad_ctrl &NO_PAD_CTRL ) && pad_ctrl_ofs)__raw_writel (pad_ctrl, base + pad_ctrl_ofs); +#endif }
Quoted 6 lines
arch/arm/imx-common/iomux-v3.c void imx_iomux_v3_setup_pad(iomux_v3_cfg_t pad) · line 61
Quoted 1 line
arch/arm/imx-common/iomux-v3.c +0
-0void imx_iomux_v3_setup_multiple_pads(iomux_v3_cfg_t const *pad_list,[...]
Apart from that, this patch is OK.
Thanks.
Best Regards,
Alison Wang
PATCH v4 1/7 arm: vf610: Add IOMUX support for Vybrid VF610
Quoted 17 lines · On 29/05/2013 07:29, Wang Huan-B18965 wrote:
Quoted 2 lines
Where is this one defined? I don't see it in
include/configs/vf610twr.h.[Alison Wang]
CONFIG_IOMUX_SHARE_CONF_REGis defined inarch/arm/include/asm/arch-vf610/imx-regs.h. Because this is not a board configuration, it is related to the SOC.Please refer to Stefano's comments below which also could be found in the email on May 15th.
Review
Quoted 3 lines · Stefano
(quoted diff) +3
-0+ +/* MUX mode and PAD ctrl are in one register */ +#define CONFIG_IOMUX_SHARE_CONF_REGNAK. This is not a board configuration, it is related to the SOC. This setup should flow into the related
imx-regs.hfor this SOC. When you setCONFIG_MVF600, this value should be set automatically.Quoted 2 lines
Why not use "#ifdef
CONFIG_VF610" since this is a platform-dependent code, and not a board-specific config option?
Quoted 7 lines
[Alison Wang] I use this
CONFIG_IOMUX_SHARE_CONF_REGoption, because this part of codes
not only could be used on VF610 platform, but also could be used on VF620 or other platforms. When it is used on VF620 or others, you could just enableCONFIG_IOMUX_SHARE_CONF_REG
in the relatedimx-regs.h.
Otherwise, if "ifdefCONFIG_VF610" is used, you need to add "#ifdefined(CONFIG_VF610)||defined(CONFIG_VF620)" When this part of codes is also used on VF620. Then when this part of codes is used on VF630 too, this line will be very very long.
Agree. This is a property of the processor and should be automatically set. It should not flow into board config file, and having a family of processor we cannot use ifdef CONFIG_VF610.
IMHO the patch is ok.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 1/7 arm: vf610: Add IOMUX support for Vybrid VF610
Hi Stefano,
Quoted 35 lines · Stefano Babic
Quoted 20 lines · On 29/05/2013 07:29, Wang Huan-B18965 wrote:
Quoted 2 lines
Where is this one defined? I don't see it in
include/configs/vf610twr.h.[Alison Wang]
CONFIG_IOMUX_SHARE_CONF_REGis defined inarch/arm/include/asm/arch-vf610/imx-regs.h. Because this is not a board configuration, it is related to the SOC.Please refer to Stefano's comments below which also could be found in the email on May 15th.
Review
Quoted 3 lines · Stefano
(quoted diff) +3
-0+ +/* MUX mode and PAD ctrl are in one register */ +#define CONFIG_IOMUX_SHARE_CONF_REGNAK. This is not a board configuration, it is related to the SOC. This setup should flow into the related
imx-regs.hfor this SOC. When you setCONFIG_MVF600, this value should be set automatically.Quoted 2 lines
Why not use "#ifdef
CONFIG_VF610" since this is a platform-dependent code, and not a board-specific config option?Quoted 12 lines
[Alison Wang] I use this
CONFIG_IOMUX_SHARE_CONF_REGoption, because this part of codes
not only could be used on VF610 platform, but also could be used on VF620 or other platforms.
When it is used on VF620 or others, you could just enableCONFIG_IOMUX_SHARE_CONF_REG
in the relatedimx-regs.h.
Otherwise, if "ifdefCONFIG_VF610" is used, you need to add "#ifdefined(CONFIG_VF610)||defined(CONFIG_VF620)"
When this part of codes is also used on VF620. Then when this part of codes is used on VF630 too, this line
will be very very long.
Quoted 7 lines
Agree. This is a property of the processor and should be automatically set. It should not flow into board config file, and having a family of processor we cannot use ifdef
CONFIG_VF610.IMHO the patch is ok.
Acked-by Stefano Babic <[email protected]>
I agree:
Best regards,
Beno?t
PATCH v4 1/7 arm: vf610: Add IOMUX support for Vybrid VF610
In reply to Alison WangQuoted 9 lines · Alison Wang
This patch adds the IOMUX support for Vybrid VF610 platform.
There is a little difference for IOMUXC module between VF610 and i.MX platform, the muxmode and pad configuration share one 32bit register on VF610, but they are two independent registers on I.MX platform. A
CONFIG_IOMUX_SHARE_CONFIG_REGwas introduced to fit this difference.Signed-off-by Alison Wang <[email protected]>---
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 2/7 arm: vf610: Add Vybrid VF610 CPU support
In reply to Alison WangThis patch adds generic codes to support Freescale's Vybrid VF610 CPU.
It aligns Vybrid VF610 platform with i.MX platform. As there are some differences between VF610 and i.MX platforms, the specific codes are in the arch/arm/cpu/armv7/vf610 directory.
---
Changes in v4:
- Rename mvf_pins.h to iomux-vf610.h
- Add README.vf610 about fuse assignments for MAC addresses
- Rename directory name 'mvf600' to 'vf610'
- Rename directory 'arch-mvf600' to 'arch-vf610'
Changes in v3:
- Rename the common functions and enums
- Move the structure definitions to imx-regs.h
Changes in v2:
- Remove vybrid-common directory
- Rename directory name 'vybrid' to 'mvf600'
- Add generic.c file
- Rewrite get_reset_cause() to make it readable
- Remove reset_cpu(), and use the function in imx_watchdog.c
- Rewrite timer.c file
- Use vybrid_get_clock(VYBRID_UART_CLK) instead of vybrid_get_uartclk()
- Remove lowlevel_init.S, and add clock_init() in board_early_init_f()
- Remove useless CONFIG_SYS_ defines
- Move CONFIG_MACH_TYPE to board configuration file
- Define C structures and access C structures to set/read registers
- Remove useless errata
- Remove useless macros
- Rename directory 'arch-vybrid' to 'arch-mvf600'
Makefile | 2 +- arch/arm/cpu/armv7/vf610/Makefile | 42 +++ arch/arm/cpu/armv7/vf610/generic.c | 324 ++++++++++++++++++++ arch/arm/cpu/armv7/vf610/timer.c | 103 +++++++ arch/arm/include/asm/arch-vf610/clock.h | 39 +++ arch/arm/include/asm/arch-vf610/crm_regs.h | 225 ++++++++++++++ arch/arm/include/asm/arch-vf610/imx-regs.h | 419 ++++++++++++++++++++++++++ arch/arm/include/asm/arch-vf610/iomux-vf610.h | 101 +++++++ doc/README.vf610 | 10 + 9 files changed, 1264 insertions(+), 1 deletion(-) create mode 100644 arch/arm/cpu/armv7/vf610/Makefile create mode 100644 arch/arm/cpu/armv7/vf610/generic.c create mode 100644 arch/arm/cpu/armv7/vf610/timer.c create mode 100644 arch/arm/include/asm/arch-vf610/clock.h create mode 100644 arch/arm/include/asm/arch-vf610/crm_regs.h create mode 100644 arch/arm/include/asm/arch-vf610/imx-regs.h create mode 100644 arch/arm/include/asm/arch-vf610/iomux-vf610.h create mode 100644 doc/README.vf610
Makefile +1 -1
@@ -341,7 +341,7 @@ ifneq ($(CONFIG_AM33XX)$(CONFIG_OMAP34XX)$(CONFIG_OMAP44XX)$(CONFIG_OMAP54XX)$(C LIBS-y += $(CPUDIR)/omap-common/libomap-common.o endif -ifneq (,$(filter $(SOC), mx25 mx27 mx5 mx6 mx31 mx35 mxs)) +ifneq (,$(filter $(SOC), mx25 mx27 mx5 mx6 mx31 mx35 mxs vf610)) LIBS-y += arch/$(ARCH)/imx-common/libimx-common.o endif
arch/arm/cpu/armv7/vf610/Makefile new file +42 -0
42 lines not on this page · raw message
arch/arm/cpu/armv7/vf610/generic.c new file +324 -0
324 lines not on this page · raw message
arch/arm/cpu/armv7/vf610/timer.c new file +103 -0
103 lines not on this page · raw message
arch/arm/include/asm/arch-vf610/clock.h new file +39 -0
@@ -0,0 +1,39 @@ +/* +* Copyright 2013 Freescale Semiconductor, Inc. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License as +* published by the Free Software Foundation; either version 2 of +* the License, or (at your option) any later version. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +* You should have received a copy of the GNU General Public License +* along with this program; if not, write to the Free Software +* Foundation, Inc., 59 Temple Place, Suite 330, Boston, +* MA 02111-1307 USA +*/ + +#ifndef __ASM_ARCH_CLOCK_H +#define __ASM_ARCH_CLOCK_H + +#include <common.h> + +enum mxc_clock { +MXC_ARM_CLK =0 , +MXC_BUS_CLK , +MXC_IPG_CLK , +MXC_UART_CLK , +MXC_ESDHC_CLK , +MXC_FEC_CLK , +}; + +void enable_ocotp_clk (unsigned char enable); +unsigned int mxc_get_clock (enum mxc_clock clk); + +#define imx_get_fecclk () mxc_get_clock(MXC_FEC_CLK) + +#endif /* __ASM_ARCH_CLOCK_H */
arch/arm/include/asm/arch-vf610/crm_regs.h new file +225 -0
225 lines not on this page · raw message
arch/arm/include/asm/arch-vf610/imx-regs.h new file +419 -0
419 lines not on this page · raw message
arch/arm/include/asm/arch-vf610/iomux-vf610.h new file +101 -0
101 lines not on this page · raw message
doc/README.vf610 new file +10 -0
@@ -0,0 +1,10 @@ +U-Boot for Freescale Vybrid VF610 + +This file contains information for the port of U-Boot to the Freescale Vybrid +VF610 SoC. + +1. CONVENTIONS FOR FUSE ASSIGNMENTS +----------------------------------- + +1.1 MAC Address: It is stored in fuse bank 4, with the 16 msbs in word 2 and the + 32 lsbs in word 3.
Signature · 1 line
1.8.0
PATCH v4 2/7 arm: vf610: Add Vybrid VF610 CPU support
Hi Alison,
Quoted 7 lines · Alison Wang
This patch adds generic codes to support Freescale's Vybrid VF610 CPU.
It aligns Vybrid VF610 platform with i.MX platform. As there are some differences between VF610 and i.MX platforms, the specific codes are in the
arch/arm/cpu/armv7/vf610directory.Signed-off-by Alison Wang <[email protected]>
[...]
Quoted 16 lines
doc/README.vf610 new file +3
-0@@ -0,0 +1,10 @@ +U-Boot for Freescale Vybrid VF610 + +This file contains information for the port of U-Boot to the FreescaleVybrid
doc/README.vf610 new file +6
-0+VF610 SoC. + +1. CONVENTIONS FOR FUSE ASSIGNMENTS +----------------------------------- + +1.1 MAC Address: It is stored in fuse bank 4, with the 16 msbs in word 2 and
Quoted 2 lines
the
+ 32 lsbs in word 3.
The hunk below is still missing:
doc/README.mxc_ocotp:
---
on MXC
This IP can be found on the following SoCs:
+ - Vybrid VF610,
- i.MX6.
Note that this IP is different from albeit similar to the IPs of the same name
---
Apart from that, this patch is correct.
Best regards,
Beno?t
PATCH v4 2/7 arm: vf610: Add Vybrid VF610 CPU support
Hi Alison,
Quoted 39 lines · Beno?t Th?baudeau
Hi Alison,
Quoted 7 lines · Alison Wang
This patch adds generic codes to support Freescale's Vybrid VF610 CPU.
It aligns Vybrid VF610 platform with i.MX platform. As there are some differences between VF610 and i.MX platforms, the specific codes are in the
arch/arm/cpu/armv7/vf610directory.Signed-off-by Alison Wang <[email protected]>[...]
Quoted 16 lines
doc/README.vf610 new file +3
-0@@ -0,0 +1,10 @@ +U-Boot for Freescale Vybrid VF610 + +This file contains information for the port of U-Boot to the FreescaleVybrid
doc/README.vf610 new file +6
-0+VF610 SoC. + +1. CONVENTIONS FOR FUSE ASSIGNMENTS +----------------------------------- + +1.1 MAC Address: It is stored in fuse bank 4, with the 16 msbs in word 2Quoted 3 lines
and
the
+ 32 lsbs in word 3.The hunk below is still missing:
doc/README.mxc_ocotp:
---
on MXC
Quoted 7 lines
This IP can be found on the following SoCs:
+ - Vybrid VF610,
- i.MX6.Note that this IP is different from albeit similar to the IPs of the same name
---
I have just noticed that this was actually in 6/7. Why are you putting this into a separate patch?
Best regards,
Beno?t
PATCH v4 2/7 arm: vf610: Add Vybrid VF610 CPU support
Hi, Benoit,
Quoted 31 lines
Quoted 31 lines
Quoted 17 lines
doc/README.vf610 new file mode renamed from doc/README.vf610 +0
-0100644 index 0000000..38cf5cf
doc/README.vf610 new file +4
-0@@ -0,0 +1,10 @@ +U-Boot for Freescale Vybrid VF610 + +This file contains information for the port of U-Boot to the +FreescaleVybrid
doc/README.vf610 new file +7
-0+VF610 SoC. + +1. CONVENTIONS FOR FUSE ASSIGNMENTS +----------------------------------- + +1.1 MAC Address: It is stored in fuse bank 4, with the 16 msbs in +word 2Quoted 3 lines
and
the
+ 32 lsbs in word 3.The hunk below is still missing:
doc/README.mxc_ocotp:
---
on MXCThis IP can be found on the following SoCs:
+ - Vybrid VF610,
- i.MX6.
Quoted 6 lines
Quoted 3 lines
Note that this IP is different from albeit similar to the IPs of the
same name
---I have just noticed that this was actually in 6/7. Why are you putting this into a separate patch?
[Alison Wang] Because patch 2/7 is about VF610 CPU support, and doc/README.vf610 is also a document about VF610 SoC. Doc/README.mxc_ocotp is the document about a driver (IP OCOTP), so this driver document should be separated from CPU patch 2/7.
Best Regards,
Alison Wang
PATCH v4 2/7 arm: vf610: Add Vybrid VF610 CPU support
Hi Alison,
Quoted 37 lines · On Wednesday, May 29, 2013 7:37:32 AM, Wang Huan-B18965 wrote:
Hi, Benoit,
Quoted 35 lines
Quoted 34 lines
Quoted 17 lines
doc/README.vf610 new file mode renamed from doc/README.vf610 +0
-0100644 index 0000000..38cf5cf
doc/README.vf610 new file +4
-0@@ -0,0 +1,10 @@ +U-Boot for Freescale Vybrid VF610 + +This file contains information for the port of U-Boot to the +FreescaleVybrid
doc/README.vf610 new file +7
-0+VF610 SoC. + +1. CONVENTIONS FOR FUSE ASSIGNMENTS +----------------------------------- + +1.1 MAC Address: It is stored in fuse bank 4, with the 16 msbs in +word 2Quoted 3 lines
and
the
+ 32 lsbs in word 3.The hunk below is still missing:
doc/README.mxc_ocotp:
---
on MXCThis IP can be found on the following SoCs:
+ - Vybrid VF610,
- i.MX6.Note that this IP is different from albeit similar to the IPs of the
same name
---
Quoted 7 lines
Quoted 2 lines
I have just noticed that this was actually in 6/7. Why are you putting this into a separate patch?
[Alison Wang] Because patch 2/7 is about VF610 CPU support, and doc/README.vf610 is also a document about
VF610 SoC. Doc/README.mxc_ocotp is the document about a driver (IP OCOTP), so this driver document should be
separated from CPU patch 2/7.
I don't think so: It's part of what comes with the addition of the VF610 platform, so 6/7 could be merged into 2/7. But it does not really matter. It's probably also fine if you keep what you did.
Stefano, any opinion?
Best regards,
Beno?t
--------------------------------------------------------------------------------
PATCH v4 2/7 arm: vf610: Add Vybrid VF610 CPU support
Quoted 2 lines · Beno?t Th?baudeau
Hi Alison,
Hi Benoit,
Quoted 8 lines
Quoted 7 lines
Quoted 2 lines
I have just noticed that this was actually in 6/7. Why are you putting this into a separate patch?
[Alison Wang] Because patch 2/7 is about VF610 CPU support, and doc/README.vf610 is also a document about
VF610 SoC. Doc/README.mxc_ocotp is the document about a driver (IP OCOTP), so this driver document should be
separated from CPU patch 2/7.
Quoted 5 lines
I don't think so: It's part of what comes with the addition of the VF610 platform, so 6/7 could be merged into 2/7. But it does not really matter. It's probably also fine if you keep what you did.
Stefano, any opinion?
Strictly speaking, you're right. But as you mentioned, it does not really matter. Without reposting, I can myself squash 6/7 into 2/7 by merging the patchset.
Best regards,
Stefano
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 2/7 arm: vf610: Add Vybrid VF610 CPU support
Hi Stefano,
Quoted 20 lines · Stefano Babic
Quoted 2 lines · Beno?t Th?baudeau
Hi Alison,
Hi Benoit,
Quoted 14 lines
Quoted 8 lines
Quoted 2 lines
I have just noticed that this was actually in 6/7. Why are you putting this into a separate patch?
[Alison Wang] Because patch 2/7 is about VF610 CPU support, and doc/README.vf610 is also a document about
VF610 SoC. Doc/README.mxc_ocotp is the document about a driver (IP OCOTP), so
this driver document should be
separated from CPU patch 2/7.I don't think so: It's part of what comes with the addition of the VF610 platform, so 6/7 could be merged into 2/7. But it does not really matter. It's
probably also fine if you keep what you did.
Quoted 5 lines
Quoted 1 line
Stefano, any opinion?
Strictly speaking, you're right. But as you mentioned, it does not really matter. Without reposting, I can myself squash 6/7 into 2/7 by merging the patchset.
OK.
Best regards,
Beno?t
PATCH v4 2/7 arm: vf610: Add Vybrid VF610 CPU support
In reply to Benoît ThébaudeauHi, Benoit,
Quoted 6 lines
The hunk below is still missing:
doc/README.mxc_ocotp:
---
on MXC
Quoted 6 lines
This IP can be found on the following SoCs:
+ - Vybrid VF610,
- i.MX6.Note that this IP is different from albeit similar to the IPs of the
same name
[Alison Wang] It is not missing, it is in the 6/7 patch.
Quoted 4 lines
---
Apart from that, this patch is correct.
Best Regards,
Alison Wang
PATCH v4 2/7 arm: vf610: Add Vybrid VF610 CPU support
In reply to Alison WangQuoted 8 lines · Alison Wang
This patch adds generic codes to support Freescale's Vybrid VF610 CPU.
It aligns Vybrid VF610 platform with i.MX platform. As there are some differences between VF610 and i.MX platforms, the specific codes are in the
arch/arm/cpu/armv7/vf610directory.Signed-off-by Alison Wang <[email protected]>---
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 3/7 net: fec_mxc: Add support for Vybrid VF610
In reply to Alison WangThis patch adds FEC support for Vybrid VF610 platform.
In function fec_open(), RCR register is only set as RGMII mode. But RCR register should be set as RMII mode for VF610 platform.
This configuration is already done in fec_reg_setup(), so this piece of code could just leave untouched the FEC_RCNTRL_RGMII / FEC_RCNTRL_RMII / FEC_RCNTRL_MII_MODE bits.
---
Changes in v4: None
Changes in v3:
- Remove the changes for FEC_RCNTRL_RGMII / FEC_RCNTRL_RMII / FEC_RCNTRL_MII_MODE bits, as they are already set in fec_reg_setup()
Changes in v2:
- Use common FEC driver fec_mxc.c
drivers/net/fec_mxc.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/net/fec_mxc.c +1 -3
@@ -516,9 +516,7 @@ static int fec_open(struct eth_device *edev)#ifdef FEC_QUIRK_ENET_MAC {u32 ecr =readl (&fec->eth->ecntrl) & ~FEC_ECNTRL_SPEED ; -u32 rcr = (readl (&fec->eth->r_cntrl) & - ~(FEC_RCNTRL_RMII |FEC_RCNTRL_RMII_10T )) | -FEC_RCNTRL_RGMII |FEC_RCNTRL_MII_MODE ; +u32 rcr =readl (&fec->eth->r_cntrl) & ~FEC_RCNTRL_RMII_10T ;if (speed == _1000BASET) ecr |=FEC_ECNTRL_SPEED ;else if (speed != _100BASET)
Signature · 1 line
1.8.0
PATCH v4 3/7 net: fec_mxc: Add support for Vybrid VF610
Hi Alison,
Quoted 7 lines · Alison Wang
This patch adds FEC support for Vybrid VF610 platform.
In function
fec_open(), RCR register is only set as RGMII mode. But RCR register should be set as RMII mode for VF610 platform.
This configuration is already done infec_reg_setup(), so this piece of code could just leave untouched theFEC_RCNTRL_RGMII/FEC_RCNTRL_RMII/FEC_RCNTRL_MII_MODEbits.
[...]
Best regards,
Beno?t
PATCH v4 3/7 net: fec_mxc: Add support for Vybrid VF610
In reply to Alison WangQuoted 11 lines · Alison Wang
This patch adds FEC support for Vybrid VF610 platform.
In function
fec_open(), RCR register is only set as RGMII mode. But RCR register should be set as RMII mode for VF610 platform.
This configuration is already done infec_reg_setup(), so this piece of code could just leave untouched theFEC_RCNTRL_RGMII/FEC_RCNTRL_RMII/FEC_RCNTRL_MII_MODEbits.Signed-off-by Alison Wang <[email protected]>Reviewed-by Benoit Thebaudeau <[email protected]>---
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 4/7 arm: vf610: Add watchdog support for Vybrid VF610
In reply to Alison WangThis patch adds watchdog support for Vybrid VF610 platform.
---
Changes in v4:
- Rename mvf600 to vf610
Changes in v3: None
Changes in v2:
- Add watchdog support
- Use reset_cpu() in imx_watchdog.c
drivers/watchdog/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/watchdog/Makefile +1 -1
@@ -27,7 +27,7 @@ LIB := $(obj)libwatchdog.o COBJS-$(CONFIG_AT91SAM9_WATCHDOG) += at91sam9_wdt.o COBJS-$(CONFIG_FTWDT010_WATCHDOG) += ftwdt010_wdt.o -ifneq (,$(filter $(SOC), mx31 mx35 mx5 mx6)) +ifneq (,$(filter $(SOC), mx31 mx35 mx5 mx6 vf610)) COBJS-y += imx_watchdog.o endif COBJS-$(CONFIG_TNETV107X_WATCHDOG) += tnetv107x_wdt.o
Signature · 1 line
1.8.0
PATCH v4 4/7 arm: vf610: Add watchdog support for Vybrid VF610
Quoted 4 lines · Alison Wang
This patch adds watchdog support for Vybrid VF610 platform.
Signed-off-by Alison Wang <[email protected]>---
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 5/7 arm: vf610: Add uart support for Vybrid VF610
In reply to Alison WangThis patch adds lpuart support for Vybrid VF610 platform.
---
Changes in v4: None
Changes in v3:
- Move the structure definition to imx-regs.h
Changes in v2:
- Define C structures and access C structures to set/read registers
- Change the names to reuse this driver on other platforms
drivers/serial/Makefile | 1 + drivers/serial/serial_lpuart.c | 132 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 133 insertions(+) create mode 100644 drivers/serial/serial_lpuart.c
drivers/serial/Makefile +1 -0
@@ -52,6 +52,7 @@ COBJS-$(CONFIG_XILINX_UARTLITE) += serial_xuartlite.o COBJS-$(CONFIG_SANDBOX_SERIAL) += sandbox.o COBJS-$(CONFIG_SCIF_CONSOLE) += serial_sh.o COBJS-$(CONFIG_ZYNQ_SERIAL) += serial_zynq.o +COBJS-$(CONFIG_FSL_LPUART) += serial_lpuart.o ifndef CONFIG_SPL_BUILD COBJS-$(CONFIG_USB_TTY) += usbtty.o
drivers/serial/serial_lpuart.c new file +132 -0
132 lines not on this page · raw message
Signature · 1 line
1.8.0
PATCH v4 5/7 arm: vf610: Add uart support for Vybrid VF610
Quoted 5 lines · Alison Wang
This patch adds lpuart support for Vybrid VF610 platform.
Signed-off-by TsiChung Liew <[email protected]>Signed-off-by Alison Wang <[email protected]>---
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 6/7 arm: vf610: Add Vybrid VF610 to mxc_ocotp document
In reply to Alison WangThis patch adds Vybrid VF610 to mxc_ocotp document.
---
Changes in v4: New
Changes in v3: None
Changes in v2: None
doc/README.mxc_ocotp | 1 + 1 file changed, 1 insertion(+)
doc/README.mxc_ocotp +1 -0
@@ -2,6 +2,7 @@ Driver implementing the fuse API for Freescale's On-Chip OTP Controller (OCOTP) on MXC This IP can be found on the following SoCs: + - Vybrid VF610, - i.MX6. Note that this IP is different from albeit similar to the IPs of the same name
Signature · 1 line
1.8.0
PATCH v4 6/7 arm: vf610: Add Vybrid VF610 to mxc_ocotp document
Hi Alison,
Quoted 25 lines · Alison Wang
This patch adds Vybrid VF610 to
mxc_ocotpdocument.Signed-off-by Alison Wang <[email protected]>---
Changes in v4: NewChanges in v3: None
Changes in v2: None
doc/README.mxc_ocotp | 1 + 1 file changed, 1 insertion(+)doc/README.mxc_ocotp +1
-0@@ -2,6 +2,7 @@ Driver implementing the fuse API for Freescale's On-Chip OTP Controller (OCOTP) on MXC This IP can be found on the following SoCs: + - Vybrid VF610, - i.MX6.
Quoted 2 lines
Note that this IP is different from albeit similar to the IPs of the same name
Best regards,
Beno?t
PATCH v4 6/7 arm: vf610: Add Vybrid VF610 to mxc_ocotp document
In reply to Alison WangQuoted 4 lines · Alison Wang
This patch adds Vybrid VF610 to
mxc_ocotpdocument.Signed-off-by Alison Wang <[email protected]>---
At the end, I left this patch without squashing to not drop also Benoit's reviewed-by. As we have already said, it does not really matter.
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 7/7 arm: vf610: Add basic support for Vybrid VF610TWR board
In reply to Alison WangVF610TWR is a board based on Vybrid VF610 SoC.
This patch adds basic support for Vybrid VF610TWR board.
---
Changes in v4:
- Rename directory name 'mvf600twr' to 'vf610twr'
- Rename mvf600twr.h to vf610twr.h
- Use NEW_PAD_CTRL instead of MUX_PAD_CTRL
- Remove CONFIG_ETHPRIME option
- Add CONFIG_CMD_MEMSET option
Changes in v3:
- Replace BOOT_FROM by BOOT_OFFSET
- Enable CONFIG_OF_LIBFDT option
- Add useful define instead of raw number
- Use clrsetbits_le32 to set the single bits
- Move setup_iomux_enet() to board_early_init_f and remove board_eth_init()
- Remove redundant define
- Move CONFIG_IOMUX_SHARE_CONF_REG to imx-regs.h
Changes in v2:
- Add an entry to MAINTAINERS file
- Rename directory name 'vybird' to 'mvf600twr'
- Use standard method to set gd->ram_size
- Rewrite board_mmc_getcd() function
- Remove useless undef
- Remove hardcoded IP addresses and MAC addresses
- Remove useless CONFIG_SYS_ defines
- Define C structures and access C structures to set/read registers
- Move CONFIG_MACH_TYPE to board configuration file
- Use common iomux-v3 code
MAINTAINERS | 4 + board/freescale/vf610twr/Makefile | 39 ++++ board/freescale/vf610twr/imximage.cfg | 33 +++ board/freescale/vf610twr/vf610twr.c | 410 ++++++++++++++++++++++++++++++++++ boards.cfg | 1 + include/configs/vf610twr.h | 140 ++++++++++++ 6 files changed, 627 insertions(+) create mode 100644 board/freescale/vf610twr/Makefile create mode 100644 board/freescale/vf610twr/imximage.cfg create mode 100644 board/freescale/vf610twr/vf610twr.c create mode 100644 include/configs/vf610twr.h
MAINTAINERS +4 -0
@@ -1057,6 +1057,10 @@ Eric Nelson <[email protected]> nitrogen6s i.MX6S 512MB nitrogen6s1g i.MX6S 1GB +Alison Wang <[email protected]> + + vf610twr VF610 + ------------------------------------------------------------------------- Unknown / orphaned boards:
board/freescale/vf610twr/Makefile new file +39 -0
@@ -0,0 +1,39 @@ +# +# Copyright 2013 Freescale Semiconductor, Inc. +# +# This program is free software; you can redistribute it and/or +# modify it under the terms of the GNU General Public License as +# published by the Free Software Foundation; either version 2 of +# the License, or (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, +# MA 02111-1307 USA +# + +include $(TOPDIR)/config.mk + +LIB = $(obj)lib$(BOARD).o + +COBJS := $(BOARD).o + +SRCS := $(COBJS:.o=.c) +OBJS := $(addprefix $(obj),$(COBJS)) + +$(LIB): $(obj).depend $(OBJS) + $(call cmd_link_o_target, $(OBJS)) + +######################################################################### + +# defines $(obj).depend target +include $(SRCTREE)/rules.mk + +sinclude $(obj).depend + +#########################################################################
board/freescale/vf610twr/imximage.cfg new file +33 -0
@@ -0,0 +1,33 @@ +/* + * Copyright 2013 Freescale Semiconductor, Inc. + * + * See file CREDITS for list of people who contributed to this + * project. + * + * This program is free software; you can redistribute it and/or + * modify it under the terms of the GNU General Public License as + * published by the Free Software Foundation; either version 2 of + * the License or (at your option) any later version. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not write to the Free Software + * Foundation Inc. 51 Franklin Street Fifth Floor Boston, + * MA 02110-1301 USA + * + * Refer docs/README.imxmage for more details about how-to configure + * and create imximage boot image + * + * The syntax is taken as close as possible with the kwbimage + */ +#include <asm/imx-common/imximage.cfg> + +/* image version */ +IMAGE_VERSION 2 + +/* Boot Offset 0x400, valid for both SD and NAND boot */ +BOOT_OFFSET FLASH_OFFSET_STANDARD
board/freescale/vf610twr/vf610twr.c new file +410 -0
410 lines not on this page · raw message
boards.cfg +1 -0
@@ -262,6 +262,7 @@ mx6qsabrelite arm armv7 mx6qsabrelite freesca mx6qsabresd arm armv7 mx6qsabresd freescale mx6 mx6qsabresd:IMX_CONFIG=board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg mx6slevk arm armv7 mx6slevk freescale mx6 mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL titanium arm armv7 titanium freescale mx6 titanium:IMX_CONFIG=board/freescale/titanium/imximage.cfg +vf610twr arm armv7 vf610twr freescale vf610 vf610twr:IMX_CONFIG=board/freescale/vf610twr/imximage.cfg eco5pk arm armv7 eco5pk 8dtech omap3 nitrogen6dl arm armv7 nitrogen6x boundary mx6 nitrogen6x:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6dl.cfg,MX6DL,DDR_MB=1024 nitrogen6dl2g arm armv7 nitrogen6x boundary mx6 nitrogen6x:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6dl2g.cfg,MX6DL,DDR_MB=2048
include/configs/vf610twr.h new file +140 -0
140 lines not on this page · raw message
Signature · 1 line
1.8.0
PATCH v4 7/7 arm: vf610: Add basic support for Vybrid VF610TWR board
Hi Alison,
Quoted 7 lines · Alison Wang
VF610TWR is a board based on Vybrid VF610 SoC.
This patch adds basic support for Vybrid VF610TWR board.
Signed-off-by Alison Wang <[email protected]>Signed-off-by Jason Jin <[email protected]>Signed-off-by TsiChung Liew <[email protected]>
[...]
Quoted 76 lines
include/configs/vf610twr.h new file +70
-0@@ -0,0 +1,140 @@ +/* +* Copyright 2013 Freescale Semiconductor, Inc. +* +* Configuration settings for the Freescale Vybrid vf610twr board. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License as +* published by the Free Software Foundation; either version 2 of +* the License, or (at your option) any later version. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +* You should have received a copy of the GNU General Public License +* along with this program; if not, write to the Free Software +* Foundation, Inc., 59 Temple Place, Suite 330, Boston, +* MA 02111-1307 USA +*/ + +#ifndef __CONFIG_H +#define __CONFIG_H + +#include <asm/arch/imx-regs.h> +#include <config_cmd_default.h> + +#define CONFIG_VF610 + +#define CONFIG_DISPLAY_CPUINFO +#define CONFIG_DISPLAY_BOARDINFO + +#define CONFIG_MACH_TYPE 4146 + +#define CONFIG_SKIP_LOWLEVEL_INIT + +/* Enable passing of ATAGs */ +#define CONFIG_CMDLINE_TAG + +#define CONFIG_CMD_FUSE +#ifdef CONFIG_CMD_FUSE +#define CONFIG_MXC_OCOTP +#endif + +/* Size of malloc() pool */ +#define CONFIG_SYS_MALLOC_LEN (CONFIG_ENV_SIZE + 2 * 1024 * 1024) + +#define CONFIG_BOARD_EARLY_INIT_F + +#define CONFIG_FSL_LPUART +#define LPUART_BASE UART1_BASE + +/* Allow to overwrite serial and ethaddr */ +#define CONFIG_ENV_OVERWRITE +#define CONFIG_SYS_UART_PORT (1) +#define CONFIG_BAUDRATE 115200 + +#undef CONFIG_CMD_IMLS + +#define CONFIG_MMC +#define CONFIG_FSL_ESDHC +#define CONFIG_SYS_FSL_ESDHC_ADDR 0 +#define CONFIG_SYS_FSL_ESDHC_NUM 1 + +#define CONFIG_SYS_FSL_ERRATUM_ESDHC111 + +#define CONFIG_CMD_MMC +#define CONFIG_GENERIC_MMC +#define CONFIG_CMD_FAT +#define CONFIG_DOS_PARTITION
include/configs/vf610twr.h line 80
Quoted 10 lines
include/configs/vf610twr.h new file +10
-0+ +#define CONFIG_CMD_PING +#define CONFIG_CMD_DHCP +#define CONFIG_CMD_MII +#define CONFIG_CMD_NET +#define CONFIG_FEC_MXC +#define CONFIG_MII +#define IMX_FEC_BASE ENET_BASE_ADDR +#define CONFIG_FEC_XCV_TYPE RMII +#define CONFIG_FEC_MXC_PHYADDR 0
Why don't you add support for the 2nd FEC? Do you plan to do it later?
Quoted 12 lines
include/configs/vf610twr.h new file +12
-0+#define CONFIG_PHYLIB +#define CONFIG_PHY_MICREL + +#define CONFIG_BOOTDELAY 3 + +#define CONFIG_SYS_TEXT_BASE 0x3f008000 + +/* Miscellaneous configurable options */ +#define CONFIG_SYS_LONGHELP /* undef to save memory */ +#define CONFIG_SYS_HUSH_PARSER /* use "hush" command parser */ +#define CONFIG_SYS_PROMPT_HUSH_PS2 "> " +#define CONFIG_SYS_PROMPT "Vybrid U-Boot > "
include/configs/vf610twr.h line 102
Quoted 10 lines
include/configs/vf610twr.h new file +10
-0+#undef CONFIG_AUTO_COMPLETE +#define CONFIG_SYS_CBSIZE 256/* Console I/O Buffer Size */ +#define CONFIG_SYS_PBSIZE \ + (CONFIG_SYS_CBSIZE + sizeof(CONFIG_SYS_PROMPT) + 16) +#define CONFIG_SYS_MAXARGS 16/* max number of command args */ +#define CONFIG_SYS_BARGSIZE CONFIG_SYS_CBSIZE + +#define CONFIG_CMD_MEMTEST +#define CONFIG_SYS_MEMTEST_START 0x80010000 +#define CONFIG_SYS_MEMTEST_END 0x87C00000
Please make sure to have runtime-tested this address range with the mtest command since bad mtest addresses are the reason why CONFIG_CMD_MEMTEST has been removed from the default commands.
[...]
Best regards,
Beno?t
PATCH v4 7/7 arm: vf610: Add basic support for Vybrid VF610TWR board
Hi, Benoit,
Quoted 4 lines
Quoted 4 lines
include/configs/vf610twr.h new file +4
-0+ +#define CONFIG_CMD_PING +#define CONFIG_CMD_DHCP +#define CONFIG_CMD_MII
Quoted 8 lines
include/configs/vf610twr.h line 80
Quoted 6 lines
include/configs/vf610twr.h new file +6
-0+#define CONFIG_CMD_NET +#define CONFIG_FEC_MXC +#define CONFIG_MII +#define IMX_FEC_BASE ENET_BASE_ADDR +#define CONFIG_FEC_XCV_TYPE RMII +#define CONFIG_FEC_MXC_PHYADDR 0Why don't you add support for the 2nd FEC? Do you plan to do it later?
[Alison Wang] In u-boot, one FEC is enough for user. We do not plan to do it later.
Quoted 20 lines
include/configs/vf610twr.h
Quoted 11 lines
include/configs/vf610twr.h new file +10
-0+#define CONFIG_PHYLIB +#define CONFIG_PHY_MICREL + +#define CONFIG_BOOTDELAY 3 + +#define CONFIG_SYS_TEXT_BASE 0x3f008000 + +/* Miscellaneous configurable options */ +#define CONFIG_SYS_LONGHELP /* undef to save memory */ +#define CONFIG_SYS_HUSH_PARSER /* use "hush" command parser */
include/configs/vf610twr.h
Quoted 7 lines
include/configs/vf610twr.h new file +7
-0+#define CONFIG_SYS_PROMPT_HUSH_PS2 "> " +#define CONFIG_SYS_PROMPT "Vybrid U-Boot > " +#undef CONFIG_AUTO_COMPLETE +#define CONFIG_SYS_CBSIZE 256/* Console I/O Buffer Size */ +#define CONFIG_SYS_PBSIZE \ + (CONFIG_SYS_CBSIZE + sizeof(CONFIG_SYS_PROMPT) + 16) +#define CONFIG_SYS_MAXARGS 16/* max number of command args */
Quoted 9 lines
include/configs/vf610twr.h line 102
Quoted 5 lines
include/configs/vf610twr.h new file +5
-0+#define CONFIG_SYS_BARGSIZE CONFIG_SYS_CBSIZE + +#define CONFIG_CMD_MEMTEST +#define CONFIG_SYS_MEMTEST_START 0x80010000 +#define CONFIG_SYS_MEMTEST_END 0x87C00000Please make sure to have runtime-tested this address range with the mtest command since bad mtest addresses are the reason why
CONFIG_CMD_MEMTESThas been removed from the default commands.
[Alison Wang] Thanks for your reminder, we have tested.
Quoted 1 line
Best Regards,
Alison Wang
PATCH v4 7/7 arm: vf610: Add basic support for Vybrid VF610TWR board
Hi Alison,
Quoted 45 lines · On Wednesday, May 29, 2013 7:52:33 AM, Wang Huan-B18965 wrote:
Hi, Benoit,
Quoted 4 lines
Quoted 4 lines
include/configs/vf610twr.h new file +4
-0+ +#define CONFIG_CMD_PING +#define CONFIG_CMD_DHCP +#define CONFIG_CMD_MII Quoted 8 lines
include/configs/vf610twr.h line 80
Quoted 6 lines
include/configs/vf610twr.h new file +6
-0+#define CONFIG_CMD_NET +#define CONFIG_FEC_MXC +#define CONFIG_MII +#define IMX_FEC_BASE ENET_BASE_ADDR +#define CONFIG_FEC_XCV_TYPE RMII +#define CONFIG_FEC_MXC_PHYADDR 0Why don't you add support for the 2nd FEC? Do you plan to do it later?
[Alison Wang] In u-boot, one FEC is enough for user. We do not plan to do it later.
Quoted 20 lines
include/configs/vf610twr.h
Quoted 11 lines
include/configs/vf610twr.h new file +10
-0+#define CONFIG_PHYLIB +#define CONFIG_PHY_MICREL + +#define CONFIG_BOOTDELAY 3 + +#define CONFIG_SYS_TEXT_BASE 0x3f008000 + +/* Miscellaneous configurable options */ +#define CONFIG_SYS_LONGHELP /* undef to save memory */ +#define CONFIG_SYS_HUSH_PARSER /* use "hush" command parser */
include/configs/vf610twr.h
Quoted 7 lines
include/configs/vf610twr.h new file +7
-0+#define CONFIG_SYS_PROMPT_HUSH_PS2 "> " +#define CONFIG_SYS_PROMPT "Vybrid U-Boot > " +#undef CONFIG_AUTO_COMPLETE +#define CONFIG_SYS_CBSIZE 256/* Console I/O Buffer Size */ +#define CONFIG_SYS_PBSIZE \ + (CONFIG_SYS_CBSIZE + sizeof(CONFIG_SYS_PROMPT) + 16) +#define CONFIG_SYS_MAXARGS 16/* max number of command args */
Quoted 9 lines
include/configs/vf610twr.h line 102
Quoted 5 lines
include/configs/vf610twr.h new file +5
-0+#define CONFIG_SYS_BARGSIZE CONFIG_SYS_CBSIZE + +#define CONFIG_CMD_MEMTEST +#define CONFIG_SYS_MEMTEST_START 0x80010000 +#define CONFIG_SYS_MEMTEST_END 0x87C00000Please make sure to have runtime-tested this address range with the mtest command since bad mtest addresses are the reason why
CONFIG_CMD_MEMTESThas been removed from the default commands.
Quoted 1 line
[Alison Wang] Thanks for your reminder, we have tested.
OK, then, for this patch:
Best regards,
Beno?t
PATCH v4 7/7 arm: vf610: Add basic support for Vybrid VF610TWR board
In reply to Alison WangQuoted 8 lines · Alison Wang
VF610TWR is a board based on Vybrid VF610 SoC.
This patch adds basic support for Vybrid VF610TWR board.
Signed-off-by Alison Wang <[email protected]>Signed-off-by Jason Jin <[email protected]>Signed-off-by TsiChung Liew <[email protected]>---
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================