Dan Murphy 7d47d1caa0 arm: omap4: panda: Add reading of the board revision ... Detect if we are running on a panda revision A1-A6, or an ES panda board. This can be done by reading the level of GPIOs and checking the processor revisions. This should result in: Panda 4430: GPIO171, GPIO101, GPIO182: 0 1 1 => A1-A5 GPIO171, GPIO101, GPIO182: 1 0 1 => A6 Panda ES: GPIO2, GPIO3, GPIO171, GPIO48, GPIO182: 0 0 0 1 1 => B1/B2 GPIO2, GPIO3, GPIO171, GPIO48, GPIO182: 0 0 1 1 1 => B3 Set the board name appropriately for the board revision that is detected. Update the findfdt macro to load the a4 device tree binary. Signed-off-by: Dan Murphy <dmurphy@ti.com> [trini: %s/CONTROL_PADCONF_CORE/(*ctrl)->control_padconf_core_base/ and formatting for that] Signed-off-by: Tom Rini <trini@ti.com>		2013-06-18 10:43:30 -04:00
..
am335x	arm, am33xx: move uart soft reset code to common place	2013-06-18 10:40:06 -04:00
am3517crane	omap_hsmmc: add driver check for write protection	2013-03-08 16:41:13 -05:00
beagle	beagleboard: Update comment in get_board_rev()	2013-05-10 08:25:55 -04:00
dra7xx	ARM: DRA7xx: Update pinmux data	2013-06-10 08:43:10 -04:00
evm	omap_hsmmc: add driver check for write protection	2013-03-08 16:41:13 -05:00
omap5_uevm	ARM: OMAP4+: Cleanup header files	2013-06-10 08:43:09 -04:00
omap730p2	doc: cleanup - move board READMEs into respective board directories	2012-07-29 15:42:02 +02:00
omap1510inn	punt unused clean/distclean targets	2011-10-15 22:20:36 +02:00
omap5912osk	omap5912-osk: Fix device initialisation	2013-04-10 16:03:01 -04:00
panda	arm: omap4: panda: Add reading of the board revision	2013-06-18 10:43:30 -04:00
sdp3430	omap_hsmmc: add driver check for write protection	2013-03-08 16:41:13 -05:00
sdp4430	ARM: OMAP4+: Cleanup header files	2013-06-10 08:43:09 -04:00
ti814x	arm, am33xx: move uart soft reset code to common place	2013-06-18 10:40:06 -04:00
tnetv107xevm	punt unused clean/distclean targets	2011-10-15 22:20:36 +02:00