Re: [U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support
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@advansee.com] Sent: Wednesday, May 22, 2013 12:28 AM To: Wang Huan-B18965 Cc: sbabic@denx.de; u-boot@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
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@advansee.com] Sent: Wednesday, May 22, 2013 12:28 AM To: Wang Huan-B18965 Cc: sbabic@denx.de; u-boot@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
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
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
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
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
participants (3)
-
Benoît Thébaudeau -
Stefano Babic -
Wang Huan-B18965