OMAP3: use a single board file for IGEP devices
Even when the IGEPv2 board and the IGEP Computer-on-Module are different from a form factor point of view, they are very similar in the fact that share many components and how they are wired. So, it is possible (and better) to have a single board file for both devices and just use the CONFIG_MACH_TYPE to make a differentiation between each board when needed. This change avoids code duplication by removing 298 lines of code and makes future maintenance easier. Signed-off-by:Javier Martinez Canillas <javier.martinez@collabora.co.uk> Acked-by:
Igor Grinberg <grinberg@compulab.co.il>
Showing
- board/isee/igep0020/igep0020.h 0 additions, 151 deletionsboard/isee/igep0020/igep0020.h
- board/isee/igep0030/Makefile 0 additions, 43 deletionsboard/isee/igep0030/Makefile
- board/isee/igep0030/igep0030.c 0 additions, 117 deletionsboard/isee/igep0030/igep0030.c
- board/isee/igep00x0/Makefile 1 addition, 1 deletionboard/isee/igep00x0/Makefile
- board/isee/igep00x0/igep00x0.c 25 additions, 13 deletionsboard/isee/igep00x0/igep00x0.c
- board/isee/igep00x0/igep00x0.h 19 additions, 8 deletionsboard/isee/igep00x0/igep00x0.h
- boards.cfg 4 additions, 4 deletionsboards.cfg
- include/configs/igep00x0.h 2 additions, 0 deletionsinclude/configs/igep00x0.h
Loading
Please register or sign in to comment