[U-Boot] [PATCH 0/3] Share header files of Faraday controllers from a320 SoC.

macpaul at andestech.com macpaul at andestech.com
Mon Nov 15 11:35:28 CET 2010


> The following three device controller inside a320 SoC are Soft IP which are
> also used by other SoC products. Here we suggest to move those header files
> out from a320 SoC folder into drivers folder. This change should provide
> header file sharing with multiple SoC.
> 
> Macpaul Lin (3):
>   ftpmu010: move ftpmu010 power controller to drivers/power folder
>   fttmr010: move fttmr010 controller to drivers/timer folder
>   ftsdmc020: move ftsdmc020 sdram controller to driver/misc folder

Some of these hardware function blocks in a SoC also used by another SoC may have only header files in U-boot. Some of these header files were used only in assembly such as lowlevel_init.S. Some of these hardware drivers provide both C level functions and assembly definitions which could be organized as drivers or could be used directly as assembly commands.

However, if U-boot could access "drivers" folder as another "include PATH" just like "include" might be a good solution to avoid writing something like the following line.
#include "../../../../drivers/timer/fttmr010.h"

The other solution is to collect these kind of source codes into a specific folder in "include", such as "include/faraday". But I think this method cannot help people to recognize the difference class of the devices.

I'm not sure if add 
CPPFLAGS += -I$(TOPDIR)/drivers
into "$(TOPDIR)/config.mk" is reasonable.

Just trying to give some suggestion.

Best regards,
Macpaul Lin


More information about the U-Boot mailing list