arm-boot/u-boot-imx.git - U-boot NXP imx6

	Commit message (Collapse)	Author	Age	Lines
*	Add GPL-2.0+ SPDX-License-Identifier to source files	Wolfgang Denk	2013-07-24	-13/+1
\| \| \| \| \| \|	Signed-off-by: Wolfgang Denk <wd@denx.de> [trini: Fixup common/cmd_io.c] Signed-off-by: Tom Rini <trini@ti.com>
*	arm: vf610: Add IOMUX support for Vybrid VF610	Alison Wang	2013-06-03	-0/+18
\| \| \| \| \| \| \| \| \| \| \| \| \|	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 <b18965@freescale.com> Acked-by: Stefano Babic <sbabic@denx.de> Reviewed-by: Benoît Thébaudeau <benoit.thebaudeau@advansee.com>
*	imx: iomux-v3: Include PKE and PUE to pad control pull definitions	Benoît Thébaudeau	2013-04-28	-5/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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 <benoit.thebaudeau@advansee.com>
*	imx: iomux-v3: Restore Linux's NEW_PAD_CTRL() macro	Benoît Thébaudeau	2013-04-28	-0/+3
\| \| \| \| \| \|	This macro will be useful for future changes. Signed-off-by: Benoît Thébaudeau <benoit.thebaudeau@advansee.com>
*	imx: iomux-v3: cosmetic: Reorganize definitions	Benoît Thébaudeau	2013-04-28	-14/+19
\| \| \| \| \| \| \|	Keep pad control definitions together, and organize definitions in a more legible way. Signed-off-by: Benoît Thébaudeau <benoit.thebaudeau@advansee.com>
*	imx: iomux-v3: Fix common pad control definitions	Benoît Thébaudeau	2013-04-28	-0/+28
\| \| \| \| \| \| \| \| \| \| \| \| \|	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 <benoit.thebaudeau@advansee.com>
*	iomux-v3: Place pad control definitions into common file	Fabio Estevam	2013-04-22	-1/+26
\| \| \| \| \| \| \|	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 <fabio.estevam@freescale.com>
*	arm: imx: Change iomux functions to void type	Stefan Roese	2013-04-16	-2/+2
\| \| \| \| \| \| \| \|	They never return anything also than 0, so lets change the function to void instead. Signed-off-by: Stefan Roese <sr@denx.de> Reviewed-by: Marek Vasut <marex@denx.de>
*	i.MX: iomux: input pad array can be const	Eric Nelson	2012-10-16	-1/+2
\| \| \| \| \|	Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com> Signed-off-by: Stefano Babic <sbabic@denx.de>
*	iomux: move IOMUX_GPR13_xxx defines	Troy Kisky	2012-09-01	-111/+0
\| \| \| \| \| \| \|	Move mx6 specific defines to arch-mx6 directory. Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com> Acked-by: Stefano Babic <sbabic@denx.de>
*	i.mx: iomux-v3.h: move to imx-common include directory	Troy Kisky	2012-07-31	-0/+214
	Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>