public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 1/6] arm: mvf600: Add Vybrid MVF600 CPU support
Date: Tue, 21 May 2013 18:57:05 +0200 (CEST)	[thread overview]
Message-ID: <815052039.1019701.1369155425121.JavaMail.root@advansee.com> (raw)
In-Reply-To: <1369126981-13970-2-git-send-email-b18965@freescale.com>

Hi Alison,

On Tuesday, May 21, 2013 11:02:56 AM, Alison Wang wrote:
> This patch adds generic codes to support Freescale's Vybrid MVF600 CPU.
> 
> It aligns Vybrid MVF600 platform with i.MX platform. As there are
> some differences between MVF600 and i.MX platforms, the specific
> codes are in the arch/arm/cpu/armv7/mvf600 directory.
> 
> Signed-off-by: Alison Wang <b18965@freescale.com>
> ---
> 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/mvf600/Makefile          |  42 +++
>  arch/arm/cpu/armv7/mvf600/generic.c         | 324 ++++++++++++++++++++++
>  arch/arm/cpu/armv7/mvf600/timer.c           | 103 +++++++
>  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 +++++++
>  8 files changed, 1237 insertions(+), 1 deletion(-)
>  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

[...]

Since this includes support for OCOTP on this SoC, the following hunks should
also be added:


doc/README.mxc_ocotp:
---
 on MXC
 
 This IP can be found on the following SoCs:
+ - Vybrid MVF600,
  - i.MX6.
 
 Note that this IP is different from albeit similar to the IPs of the same name
---


doc/README.mvf600:
---
+U-Boot for Freescale Vybrid MVF600
+
+This file contains information for the port of U-Boot to the Freescale Vybrid
+MVF600 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.
---


You can also add the definition of the fuses for UID if any, like uid_low/high
in struct fuse_bank0_regs in arch/arm/include/asm/arch-mx6/imx-regs.h.

Best regards,
Beno?t

  parent reply	other threads:[~2013-05-21 16:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  9:02 [U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support Alison Wang
2013-05-21  9:02 ` [U-Boot] [PATCH v3 1/6] arm: mvf600: Add Vybrid MVF600 CPU support Alison Wang
2013-05-21 13:48   ` Fabio Estevam
2013-05-22  2:59     ` Wang Huan-B18965
2013-05-21 16:57   ` Benoît Thébaudeau [this message]
2013-05-22  5:17     ` Wang Huan-B18965
2013-05-21 19:00   ` Benoît Thébaudeau
2013-05-22  5:30     ` Wang Huan-B18965
2013-05-21  9:02 ` [U-Boot] [PATCH v3 2/6] arm: mvf600: Add IOMUX support for Vybrid MVF600 Alison Wang
2013-05-21 17:10   ` Benoît Thébaudeau
2013-05-21  9:02 ` [U-Boot] [PATCH v3 3/6] net: fec_mxc: Add " Alison Wang
2013-05-21 17:15   ` Benoît Thébaudeau
2013-05-21  9:02 ` [U-Boot] [PATCH v3 4/6] arm: mvf600: Add watchdog " Alison Wang
2013-05-21  9:03 ` [U-Boot] [PATCH v3 5/6] arm: mvf600: Add uart " Alison Wang
2013-05-21  9:03 ` [U-Boot] [PATCH v3 6/6] arm: mvf600: Add basic support for Vybrid MVF600TWR board Alison Wang
2013-05-21 17:29   ` Benoît Thébaudeau
     [not found]     ` <81BA6E5E0BC2344391CABCEE22D1B6D8335B27@039-SN1MPN1-003.039d.mgd.msft.net>
2013-05-22 16:21       ` Benoît Thébaudeau
2013-05-23  5:44         ` Wang Huan-B18965
2013-05-21 19:19   ` Benoît Thébaudeau
2013-05-21 16:27 ` [U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support Benoît Thébaudeau
     [not found]   ` <81BA6E5E0BC2344391CABCEE22D1B6D8335A6C@039-SN1MPN1-003.039d.mgd.msft.net>
2013-05-23 17:09     ` Benoît Thébaudeau
2013-05-24  6:18       ` Wang Huan-B18965
2013-05-27  6:51         ` Stefano Babic
2013-05-28  8:51           ` Wang Huan-B18965
2013-05-28  9:03             ` Stefano Babic
2013-05-28  8:59         ` Wang Huan-B18965

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=815052039.1019701.1369155425121.JavaMail.root@advansee.com \
    --to=benoit.thebaudeau@advansee.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox