diff options
author | Robert Schwebel <r.schwebel@pengutronix.de> | 2010-10-22 18:45:06 +0200 |
---|---|---|
committer | Sascha Hauer <s.hauer@pengutronix.de> | 2010-10-22 20:47:03 +0200 |
commit | b99f850bc764e21683ecec9a6d44a8de4c358e7f (patch) | |
tree | 0de5ed8954e8160ff347624ac8e354c61d8dac44 /arch | |
parent | 66b6037f2e4a5635b2680d12e6ac416c02eddfac (diff) | |
download | barebox-b99f850bc764e21683ecec9a6d44a8de4c358e7f.tar.gz barebox-b99f850bc764e21683ecec9a6d44a8de4c358e7f.tar.xz |
doc: mark code explicitely
Silence this warning:
arch/arm/mach-omap/arch-omap.dox:51: Warning: explicit link request to 'define' could not be resolved
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'arch')
-rw-r--r-- | arch/arm/mach-omap/arch-omap.dox | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/arch/arm/mach-omap/arch-omap.dox b/arch/arm/mach-omap/arch-omap.dox index df16b7be96..9c90b4fb16 100644 --- a/arch/arm/mach-omap/arch-omap.dox +++ b/arch/arm/mach-omap/arch-omap.dox @@ -50,7 +50,11 @@ All basic devices you'd like to register should be put here with postcore_initca All OMAP common headers are located here. Where we have to incorporate a OMAP variant specific header, add a omapX_function_name.h. @warning Do not add board specific header files/information here. Put them in mach-omap. -include/asm-arm/arch-omap/silicon.h contains includes for omapX-silicon.h which defines the base addresses for the peripherals on that platform. the usual convention is to use #define OMAP_SOMETHING_BASE to allow re-use. +include/asm-arm/arch-omap/silicon.h contains includes for omapX-silicon.h which defines the base addresses for the peripherals on that platform. the usual convention is to use +@code +#define OMAP_SOMETHING_BASE +@endcode +to allow re-use. @section board_omap arch/arm/boards/omap directory guidelines All Board specific files go here. In u-boot, we always had to use common config file which is shared by other drivers to get serial, ethernet baseaddress etc.. we can easily use the device_d structure to handle it with @a barebox. This is more like programming for Linux kernel - it is pretty easy. |