u-boot.git/arch/arm/include/asm/imx-common, branch v2013.07

arm: vf610: Add IOMUX support for Vybrid VF610

2013-06-03T08:56:53Z

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. Signed-off-by: Alison Wang Acked-by: Stefano Babic Reviewed-by: Benoît Thébaudeau

tools: arm: imx: Implement BOOT_OFFSET command for imximage

2013-04-28T09:18:03Z

Implement BOOT_OFFSET command for imximage. This command is parallel to current BOOT_FROM command, but allows more flexibility in configuring arbitrary image header offset. Also add an imximage.cfg with default offset values into arm/arch/imx-common/ so the board-specific imximage.cfg can include this file to avoid magic constants. The syntax of BOOT_OFFSET command is "BOOT_OFFSET ". Signed-off-by: Marek Vasut Cc: Albert ARIBAUD Cc: Benoît Thébaudeau Cc: Fabio Estevam Cc: Scott Wood Cc: Stefano Babic Cc: Tom Rini Acked-by: Stefano Babic Acked-by: Stefan Roese

imx: iomux-v3: Include PKE and PUE to pad control pull definitions

2013-04-28T09:15:07Z

PUE requires PKE to mean something, as do pull values with PUE, so do not compell users to explicitly use PKE and PUE everywhere. This is also what is done on Linux and what has already been done for i.MX51. By the way, remove some unused pad control definitions. There is no change of behavior. Note that SPI_PAD_CTRL was defined by several boards with a pull value, but without PKE or PUE, which means that no pull was actually enabled in the pad. This might be a bug in those boards, but this patch does not change the behavior, so it just removes the meaningless pull value from those definitions. Signed-off-by: Benoît Thébaudeau

imx: iomux-v3: Restore Linux's NEW_PAD_CTRL() macro

2013-04-28T09:15:07Z

This macro will be useful for future changes. Signed-off-by: Benoît Thébaudeau

imx: iomux-v3: cosmetic: Reorganize definitions

2013-04-28T09:15:06Z

Keep pad control definitions together, and organize definitions in a more legible way. Signed-off-by: Benoît Thébaudeau

imx: iomux-v3: Fix common pad control definitions

2013-04-28T09:15:06Z

Commit dc88403 "iomux-v3: Place pad control definitions into common file" broke mx51_efikamx because it made i.MX6's pad control definitions conflict with i.MX51's. i.MX51's pad control definitions are actually common to some other i.MX (25/35/53), so move them to the common iomux-v3.h (just like what is done in Linux's), and select the correct definitions depending on whether CONFIG_MX6 is defined or not. Signed-off-by: Benoît Thébaudeau

mtd: mxs_nand: Add support for i.MX6

2013-04-22T08:26:36Z

Signed-off-by: Stefan Roese Acked-by: Scott Wood Cc: Stefano Babic Cc: Marek Vasut Cc: Fabio Estevam

dma: Add i.MX6 support to drivers/dma/apbh_dma.c

2013-04-22T08:26:13Z

This will be used by the i.MX6 NAND support. Signed-off-by: Stefan Roese Cc: Stefano Babic Cc: Marek Vasut Cc: Fabio Estevam

imx: Move some header files from arch-mxs to imx-common

2013-04-22T08:22:22Z

The following headers are moved to a i.MX common location: - regs-common.h - regs-apbh.h - regs-bch.h - regs-gpmi.h - dma.h This way this header can be re-used also by other i.MX platforms. For example the i.MX6 which will need it for the upcoming NAND support. Signed-off-by: Stefan Roese Cc: Stefano Babic Cc: Marek Vasut Cc: Fabio Estevam

iomux-v3: Place pad control definitions into common file

2013-04-22T07:56:20Z

Instead of having the same PAD control definition in each MX6 variant pin file, place it into a common location. Signed-off-by: Fabio Estevam