[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Wang Huan-B18965]

Hi, Benoit,

On Tuesday, May 21, 2013 11:02:55 AM, Alison Wang wrote:
> This series contain the support for Freescale Vybrid MVF600 CPU and MVF600TWR
> 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, MVF600 is a dual-core eMPU combining the ARM
> Cortex A5 and Cortex M4 cores.
>
> MVF600 shares some IPs with i.MX family, such as FEC,ESDHC,WATCHDOG,I2C,ASRC
> and ESAI.
> MVF600 also shares some IPs with ColdFire family, such as eDMA and DSPI.
> MVF600 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

I have a question about the naming of this SoC. On Freescale's website, it is
VF6xx everywhere, but you add a leading M (_M_VF600). Is it because you are
using an internal SoC name known only by Freescale and different from the
marketing SoC name, or is this M from the part number, or will the marketing SoC
name change later, or some other reason? Please clarify. U-Boot users must be
able to identify a SoC and to find information about it easily.
[Alison Wang] We always use the name "MVF600" in the internal development.
We will check it with marketing team, and confirm it. Thanks.
>
> The u-boot runs on Cortex A5 core.

[...]

Best regards,
Alison Wang

[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Stefano Babic]

On 28/05/2013 10:51, Wang Huan-B18965 wrote:
> Hi, Stefano,
> 
>> On 24/05/2013 08:18, Wang Huan-B18965 wrote:
>>
>>> [Alison Wang] We usually named the Powerpc(before QorIQ) as MPC and
>> ColdFire as MCF, So we generally named the Vybrid as MVF.
>>> We had some internal discussion for this, and we think we should use
>>> VF instead of MVF, we will follow the internal suggestions to name
>> the soc as VF610. Thanks for your comments.
>>
>> It is nice if you use the same name everybody finds on Freescale's
>> Website. However, I hope you decide that the names will be consistent
>> with the kernel, and also the patches that are currently posted to
>> linux-arm will change the processor name. The worst thing is if we get
>> a name in u-boot and another one in kernel.
>>
> [Alison Wang] Thanks for your reminder, we have discussed this with the kernel maintainer and get agreement to use the SoC name vf610. We'll use the 'vf610' in both u-boot and kernel. any comments for the name? Thanks.
> 

No, you are the developer, you work in Freescale and your is the final
decision about the names.
My point of view, and maybe it is the same for most of Freescale's
customers, is to have consistent names. Everybody checking Freescale's
website knows that the SOC / board is supported in u-boot and/or kernel
if he finds the same names as on the website. But is the mx53loco the
same as mx53qsb, the official name to buy the board ? Of course, it is
the same, but not at the first glance. Or mx51evk and babbage ? Or
(following some other bad examples...) ?

Best regards,
Stefano Babic

-- 
=====================================================================
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
=====================================================================

[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Wang Huan-B18965]

Hi, benoit,

> > > > On Tuesday, May 21, 2013 11:02:55 AM, Alison Wang wrote:
> > > > > This series contain the support for Freescale Vybrid MVF600 CPU
> > > > > and MVF600TWR 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, MVF600 is a dual-core eMPU
> > > > > combining the ARM Cortex A5 and Cortex M4 cores.
> > > > >
> > > > > MVF600 shares some IPs with i.MX family, such as
> > > > > FEC,ESDHC,WATCHDOG,I2C,ASRC and ESAI.
> > > > > MVF600 also shares some IPs with ColdFire family, such as eDMA
> > and DSPI.
> > > > > MVF600 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=VF6
> > > > > xx&f
> > > > > srch=1&sr=5
> > > > >
> http://www.freescale.com/webapp/sps/site/homepage.jsp?code=VYBRI
> > > > > D
> > > >
> > > > I have a question about the naming of this SoC. On Freescale's
> > > > website, it is VF6xx everywhere, but you add a leading M
> (_M_VF600).
> > > > Is it because you are using an internal SoC name known only by
> > > > Freescale and different from the marketing SoC name, or is this M
> > > > from the part number, or will the marketing SoC name change later,
> > or some other reason? Please clarify.
> > > > U-Boot users must be able to identify a SoC and to find
> > > > information about it easily.
> > > [Alison Wang] We always use the name "MVF600" in the internal
> > > development. We will check it with marketing team, and confirm it.
> > > Thanks.
> >
> > OK. You should also check for each part of the code in this patch set
> > if it is specific to the (M)VF600 or common to all (M)VF6xx SoCs. In
> > the latter case, the names in the code should be changed to either
> > (m)vf6xx or (m)vf6, just like U-Boot uses "mx5" to mean i.MX5xx. The
> > naming for your Linux patches should also preferably be the same as
> in
> > U-Boot in order to avoid confusion for users.
> [Alison Wang] We usually named the Powerpc(before QorIQ) as MPC and
> ColdFire as MCF, So we generally named the Vybrid as MVF.
> We had some internal discussion for this, and we think we should use VF
> instead of MVF, we will follow the internal suggestions to name the soc
> as VF610. Thanks for your comments.
> We have no detail spec for other vf6xx chips so far, so from technical
> side we can only make sure current code in this patch set is work for
> VF610. So we'll use VF610 instead of vf6xx.
>
[Alison Wang] Do you have any comments about the SoC name? I'd like to send out the next version patch set based on the new SoC name vf610. Thanks.


Best Regards,
Alison Wang

[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Wang Huan-B18965]

Hi, Stefano,

> On 24/05/2013 08:18, Wang Huan-B18965 wrote:
> 
> > [Alison Wang] We usually named the Powerpc(before QorIQ) as MPC and
> ColdFire as MCF, So we generally named the Vybrid as MVF.
> > We had some internal discussion for this, and we think we should use
> > VF instead of MVF, we will follow the internal suggestions to name
> the soc as VF610. Thanks for your comments.
> 
> It is nice if you use the same name everybody finds on Freescale's
> Website. However, I hope you decide that the names will be consistent
> with the kernel, and also the patches that are currently posted to
> linux-arm will change the processor name. The worst thing is if we get
> a name in u-boot and another one in kernel.
> 
[Alison Wang] Thanks for your reminder, we have discussed this with the kernel maintainer and get agreement to use the SoC name vf610. We'll use the 'vf610' in both u-boot and kernel. any comments for the name? Thanks.

Best Regards,
Alison Wang

[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Stefano Babic]

On 24/05/2013 08:18, Wang Huan-B18965 wrote:

> [Alison Wang] We usually named the Powerpc(before QorIQ) as MPC and ColdFire as MCF, So we generally named the Vybrid as MVF. 
> We had some internal discussion for this, and we think we should use VF instead of MVF, we will follow the internal suggestions to 
> name the soc as VF610. Thanks for your comments.

It is nice if you use the same name everybody finds on Freescale's
Website. However, I hope you decide that the names will be consistent
with the kernel, and also the patches that are currently posted to
linux-arm will change the processor name. The worst thing is if we get a
name in u-boot and another one in kernel.

Best regards,
Stefano Babic



-- 
=====================================================================
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
=====================================================================

[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Wang Huan-B18965]

Hi, Benoit,

> On Wednesday, May 22, 2013 5:01:44 AM, Wang Huan-B18965 wrote:
> > Hi, Benoit,
> >
> > > -----Original Message-----
> > > From: Beno?t Th?baudeau [mailto:benoit.thebaudeau at advansee.com]
> > > Sent: Wednesday, May 22, 2013 12:28 AM
> > > To: Wang Huan-B18965
> > > Cc: sbabic at denx.de; u-boot at lists.denx.de; Estevam Fabio-R49496
> > > Subject: Re: [U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale
> > > Vybrid MVF600 CPU and MVF600TWR board support
> > >
> > > Hi Alison,
> > >
> > > On Tuesday, May 21, 2013 11:02:55 AM, Alison Wang wrote:
> > > > This series contain the support for Freescale Vybrid MVF600 CPU
> > > > and MVF600TWR 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, MVF600 is a dual-core eMPU combining
> > > > the ARM Cortex A5 and Cortex M4 cores.
> > > >
> > > > MVF600 shares some IPs with i.MX family, such as
> > > > FEC,ESDHC,WATCHDOG,I2C,ASRC and ESAI.
> > > > MVF600 also shares some IPs with ColdFire family, such as eDMA
> and DSPI.
> > > > MVF600 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=VF6
> > > > xx&f
> > > > srch=1&sr=5
> > > > http://www.freescale.com/webapp/sps/site/homepage.jsp?code=VYBRID
> > >
> > > I have a question about the naming of this SoC. On Freescale's
> > > website, it is VF6xx everywhere, but you add a leading M (_M_VF600).
> > > Is it because you are using an internal SoC name known only by
> > > Freescale and different from the marketing SoC name, or is this M
> > > from the part number, or will the marketing SoC name change later,
> or some other reason? Please clarify.
> > > U-Boot users must be able to identify a SoC and to find information
> > > about it easily.
> > [Alison Wang] We always use the name "MVF600" in the internal
> > development. We will check it with marketing team, and confirm it.
> > Thanks.
> 
> OK. You should also check for each part of the code in this patch set
> if it is specific to the (M)VF600 or common to all (M)VF6xx SoCs. In
> the latter case, the names in the code should be changed to either
> (m)vf6xx or (m)vf6, just like U-Boot uses "mx5" to mean i.MX5xx. The
> naming for your Linux patches should also preferably be the same as in
> U-Boot in order to avoid confusion for users.
[Alison Wang] We usually named the Powerpc(before QorIQ) as MPC and ColdFire as MCF, So we generally named the Vybrid as MVF. 
We had some internal discussion for this, and we think we should use VF instead of MVF, we will follow the internal suggestions to 
name the soc as VF610. Thanks for your comments.
We have no detail spec for other vf6xx chips so far, so from technical side we can only make sure current code in this patch set is work 
for VF610. So we'll use VF610 instead of vf6xx.

Best Regards,
Alison

[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Benoît Thébaudeau]

Hi Alison,

On Wednesday, May 22, 2013 5:01:44 AM, Wang Huan-B18965 wrote:
> Hi, Benoit,
> 
> > -----Original Message-----
> > From: Beno?t Th?baudeau [mailto:benoit.thebaudeau at advansee.com]
> > Sent: Wednesday, May 22, 2013 12:28 AM
> > To: Wang Huan-B18965
> > Cc: sbabic at denx.de; u-boot at lists.denx.de; Estevam Fabio-R49496
> > Subject: Re: [U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid
> > MVF600 CPU and MVF600TWR board support
> > 
> > Hi Alison,
> > 
> > On Tuesday, May 21, 2013 11:02:55 AM, Alison Wang wrote:
> > > This series contain the support for Freescale Vybrid MVF600 CPU and
> > > MVF600TWR 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, MVF600 is a dual-core eMPU combining the
> > > ARM Cortex A5 and Cortex M4 cores.
> > >
> > > MVF600 shares some IPs with i.MX family, such as
> > > FEC,ESDHC,WATCHDOG,I2C,ASRC and ESAI.
> > > MVF600 also shares some IPs with ColdFire family, such as eDMA and DSPI.
> > > MVF600 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&f
> > > srch=1&sr=5
> > > http://www.freescale.com/webapp/sps/site/homepage.jsp?code=VYBRID
> > 
> > I have a question about the naming of this SoC. On Freescale's website,
> > it is VF6xx everywhere, but you add a leading M (_M_VF600). Is it because
> > you are using an internal SoC name known only by Freescale and different
> > from the marketing SoC name, or is this M from the part number, or will
> > the marketing SoC name change later, or some other reason? Please clarify.
> > U-Boot users must be able to identify a SoC and to find information about
> > it easily.
> [Alison Wang] We always use the name "MVF600" in the internal development. We
> will
> check it with marketing team, and confirm it. Thanks.

OK. You should also check for each part of the code in this patch set if it is
specific to the (M)VF600 or common to all (M)VF6xx SoCs. In the latter case, the
names in the code should be changed to either (m)vf6xx or (m)vf6, just like
U-Boot uses "mx5" to mean i.MX5xx. The naming for your Linux patches should also
preferably be the same as in U-Boot in order to avoid confusion for users.

Best regards,
Beno?t

[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Benoît Thébaudeau]

Hi Alison,

On Tuesday, May 21, 2013 11:02:55 AM, Alison Wang wrote:
> This series contain the support for Freescale Vybrid MVF600 CPU and MVF600TWR
> 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, MVF600 is a dual-core eMPU combining the ARM
> Cortex A5 and Cortex M4 cores.
> 
> MVF600 shares some IPs with i.MX family, such as FEC,ESDHC,WATCHDOG,I2C,ASRC
> and ESAI.
> MVF600 also shares some IPs with ColdFire family, such as eDMA and DSPI.
> MVF600 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

I have a question about the naming of this SoC. On Freescale's website, it is
VF6xx everywhere, but you add a leading M (_M_VF600). Is it because you are
using an internal SoC name known only by Freescale and different from the
marketing SoC name, or is this M from the part number, or will the marketing SoC
name change later, or some other reason? Please clarify. U-Boot users must be
able to identify a SoC and to find information about it easily.

> 
> The u-boot runs on Cortex A5 core.

[...]

Best regards,
Beno?t

[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Alison Wang]

This series contain the support for Freescale Vybrid MVF600 CPU and MVF600TWR 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, MVF600 is a dual-core eMPU combining the ARM
Cortex A5 and Cortex M4 cores.

MVF600 shares some IPs with i.MX family, such as FEC,ESDHC,WATCHDOG,I2C,ASRC and ESAI.
MVF600 also shares some IPs with ColdFire family, such as eDMA and DSPI.
MVF600 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

The u-boot runs on Cortex A5 core.

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 (6):
      arm: mvf600: Add Vybrid MVF600 CPU support
      arm: mvf600: Add IOMUX support for Vybrid MVF600
      net: fec_mxc: Add support for Vybrid MVF600
      arm: mvf600: Add watchdog support for Vybrid MVF600
      arm: mvf600: Add uart support for Vybrid MVF600
      arm: mvf600: Add basic support for Vybrid MVF600TWR board

 MAINTAINERS                                 |   4 ++
 Makefile                                    |   2 +-
 arch/arm/cpu/armv7/mvf600/Makefile          |  42 +++++++++++
 arch/arm/cpu/armv7/mvf600/generic.c         | 324 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 arch/arm/cpu/armv7/mvf600/timer.c           | 103 ++++++++++++++++++++++++++
 arch/arm/imx-common/Makefile                |   2 +-
 arch/arm/imx-common/iomux-v3.c              |   6 ++
 arch/arm/include/asm/arch-mvf600/clock.h    |  39 ++++++++++
 arch/arm/include/asm/arch-mvf600/crm_regs.h | 225 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 arch/arm/include/asm/arch-mvf600/imx-regs.h | 411 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 arch/arm/include/asm/arch-mvf600/mvf_pins.h |  92 ++++++++++++++++++++++++
 arch/arm/include/asm/imx-common/iomux-v3.h  |  18 +++++
 board/freescale/mvf600twr/Makefile          |  39 ++++++++++
 board/freescale/mvf600twr/imximage.cfg      |  33 +++++++++
 board/freescale/mvf600twr/mvf600twr.c       | 413 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 boards.cfg                                  |   1 +
 drivers/net/fec_mxc.c                       |   4 +-
 drivers/serial/Makefile                     |   1 +
 drivers/serial/serial_lpuart.c              | 132 ++++++++++++++++++++++++++++++++++
 drivers/watchdog/Makefile                   |   2 +-
 include/configs/mvf600twr.h                 | 140 ++++++++++++++++++++++++++++++++++++
 21 files changed, 2027 insertions(+), 6 deletions(-)
 create mode 100644 arch/arm/cpu/armv7/mvf600/Makefile
 create mode 100644 arch/arm/cpu/armv7/mvf600/generic.c
 create mode 100644 arch/arm/cpu/armv7/mvf600/timer.c
 create mode 100644 arch/arm/include/asm/arch-mvf600/clock.h
 create mode 100644 arch/arm/include/asm/arch-mvf600/crm_regs.h
 create mode 100644 arch/arm/include/asm/arch-mvf600/imx-regs.h
 create mode 100644 arch/arm/include/asm/arch-mvf600/mvf_pins.h
 create mode 100644 board/freescale/mvf600twr/Makefile
 create mode 100644 board/freescale/mvf600twr/imximage.cfg
 create mode 100644 board/freescale/mvf600twr/mvf600twr.c
 create mode 100644 drivers/serial/serial_lpuart.c
 create mode 100644 include/configs/mvf600twr.h