1. 31 Aug, 2014 1 commit
  2. 30 Jul, 2014 2 commits
    • Masahiro Yamada's avatar
      Add board MAINTAINERS files · 93d4334f
      Masahiro Yamada authored
      We have switched to Kconfig and the boards.cfg file is going to
      be removed. We have to retrieve the board status and maintainers
      information from it.
      
      The MAINTAINERS format as in Linux Kernel would be nice
      because we can crib the scripts/get_maintainer.pl script.
      
      After some discussion, we chose to put a MAINTAINERS file under each
      board directory, not the top-level one because we want to collect
      relevant information for a board into a single place.
      
      TODO:
      Modify get_maintainer.pl to scan multiple MAINTAINERS files.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Suggested-by: default avatarTom Rini <trini@ti.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      93d4334f
    • Masahiro Yamada's avatar
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada authored
      This commit adds:
       - arch/${ARCH}/Kconfig
          provide a menu to select target boards
       - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
          set CONFIG macros to the appropriate values for each board
       - configs/${TARGET_BOARD}_defconfig
          default setting of each board
      
      (This commit was automatically generated by a conversion script
      based on boards.cfg)
      
      In Linux Kernel, defconfig files are located under
      arch/${ARCH}/configs/ directory.
      It works in Linux Kernel since ARCH is always given from the
      command line for cross compile.
      
      But in U-Boot, ARCH is not given from the command line.
      Which means we cannot know ARCH until the board configuration is done.
      That is why all the "*_defconfig" files should be gathered into a
      single directory ./configs/.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      dd84058d
  3. 23 Jul, 2014 1 commit
    • Masahiro Yamada's avatar
      zynq: disable -Wstrict-prototypes option for ps7_init.c · 32747491
      Masahiro Yamada authored
      The files ps7_init.c and ps7_init.h are supposed to be generated by
      hw projects such as Vivado, PlanAhead and then to be copied into
      board/xilinx/zynq directory.
      
      But some prototypes in them cause annoying warning messages:
      
        CC      spl/board/xilinx/zynq/ps7_init.o
      In file included from board/xilinx/zynq/ps7_init.c:50:0:
      board/xilinx/zynq/ps7_init.h:137:1: warning: function declaration isn't a prototype [-Wstrict-prototypes]
      board/xilinx/zynq/ps7_init.h:138:1: warning: function declaration isn't a prototype [-Wstrict-prototypes]
      board/xilinx/zynq/ps7_init.h:139:1: warning: function declaration isn't a prototype [-Wstrict-prototypes]
      board/xilinx/zynq/ps7_init.h:145:1: warning: function declaration isn't a prototype [-Wstrict-prototypes]
      board/xilinx/zynq/ps7_init.c:12602:1: warning: function declaration isn't a prototype [-Wstrict-prototypes]
      board/xilinx/zynq/ps7_init.c:12723:1: warning: function declaration isn't a prototype [-Wstrict-prototypes]
      board/xilinx/zynq/ps7_init.c:12742:1: warning: function declaration isn't a prototype [-Wstrict-prototypes]
      board/xilinx/zynq/ps7_init.c:12761:1: warning: function declaration isn't a prototype [-Wstrict-prototypes]
      board/xilinx/zynq/ps7_init.c:12854:6: warning: function declaration isn't a prototype [-Wstrict-prototypes]
      
      The prototypes should be
      
        int ps7_init(void);
        int ps7_post_config(void);
        int ps7_debug(void);
      
      rather than
      
        int ps7_init();
        int ps7_post_config();
        int ps7_debug();
      
      We do not want to be bothered because of automatically generated files.
      But we cannot touch the external projects for now.
      What we can do is to disable -Wstrict-prototypes for ps7_init.c
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Michal Simek <michal.simek@xilinx.com>
      Tested-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      32747491
  4. 14 May, 2014 4 commits
    • Masahiro Yamada's avatar
      zynq: treat ps7_init.c/h as external files to ignore them · 66e6715c
      Masahiro Yamada authored
      ps7_init.c and ps7_init.h are supposed to be exported by hw project
      and copied to board/xilinx/zynq/ directory.
      
      We want them to be ignored by git.
      So what we should do is to always treat them as external files
      rather than replacing ps7_init.c
      
      This commit does:
      
       - Move a weak function ps7_init() to arch/arm/cpu/armv7/zynq/spl.c
         and delete board/xilinx/zynq/ps7_init.c
      
       - Compile board/xilinx/zynq/ps7_init.c only when it exists
      
       - Add .gitignore to ignore ps7_init.c/h
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      66e6715c
    • Masahiro Yamada's avatar
      zynq: add empty xil_io.h to avoid compile error · f05862d7
      Masahiro Yamada authored
      ps7_init.c exported by hw project has #include "xil_io.h" line
      but U-Boot does not have "xil_io.h".
      
      So we get an error on SPL build:
        ps7_init.c:12581:20: fatal error: xil_io.h: No such file or directory
      
      We can delete the include directive in ps7_init.c to avoid this error.
      But it is painful to do this every time we export ps7_init.c file.
      
      Instead, we can put an empty xil_io.h in the same directory
      so we can directly copy ps7_init.c as is.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: default avatarTom Rini <trini@ti.com>
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      f05862d7
    • Michal Simek's avatar
      ARM: zynq: Fix building SPL without FPGA support · 0b680206
      Michal Simek authored
      When CONFIG_FPGA is defined but CONFIG_SPL_FPGA is not, the build fails:
      board.c: In function 'board_init':
      board.c:41:3: error: 'fpga' undeclared (first use in this function)
         fpga = fpga010;
      
      Fix this by expanding the "#if.." around this block to match the other
      FPGA checks and don't compile this block when buildign for SPL without
      FPGA support.
      
      Tested a bootloader that had CONFIG_FPGA defined without CONFIG_SPL_FPGA,
      this now compiles without errors and loading FPGA from u-boot works.
      Signed-off-by: default avatarMike Looijmans <mike.looijmans@topic.nl>
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      0b680206
    • Michal Simek's avatar
      ARM: zynq: Remove sparse warnings · 5b73caff
      Michal Simek authored
      Warnings:
      board/xilinx/zynq/board.c:17:13: warning: symbol 'fpga' was not declared. Should it be static?
      board/xilinx/zynq/board.c:20:13: warning: symbol 'fpga010' was not declared. Should it be static?
      board/xilinx/zynq/board.c:21:13: warning: symbol 'fpga015' was not declared. Should it be static?
      board/xilinx/zynq/board.c:22:13: warning: symbol 'fpga020' was not declared. Should it be static?
      board/xilinx/zynq/board.c:23:13: warning: symbol 'fpga030' was not declared. Should it be static?
      board/xilinx/zynq/board.c:24:13: warning: symbol 'fpga045' was not declared. Should it be static?
      board/xilinx/zynq/board.c:25:13: warning: symbol 'fpga100' was not declared. Should it be static?
      board/xilinx/zynq/board.c:120:5: warning: symbol 'board_mmc_init' was not declared. Should it be static?
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      5b73caff
  5. 13 May, 2014 1 commit
  6. 12 Mar, 2014 1 commit
    • Masahiro Yamada's avatar
      kbuild: rename SRCTREE to srctree · 01286329
      Masahiro Yamada authored
      Prior to Kbuild, $(TOPDIR) or $(SRCTREE) was used for
      pointing to the top of source directory.
      (No difference between the two.)
      
      In Kbuild style, $(srctree) is used for instead.
      This commit renames SRCTREE to srctree and deletes the
      defition of SRCTREE.
      
      Note that SRCTREE in scripts/kernel-doc, scripts/docproc.c,
      doc/DocBook/Makefile should be keep.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      01286329
  7. 07 Mar, 2014 1 commit
  8. 04 Mar, 2014 1 commit
  9. 19 Feb, 2014 5 commits
  10. 06 Feb, 2014 1 commit
  11. 10 Jan, 2014 3 commits
  12. 17 Nov, 2013 1 commit
  13. 01 Nov, 2013 2 commits
  14. 31 Oct, 2013 1 commit
  15. 14 Oct, 2013 1 commit
  16. 12 Aug, 2013 3 commits
  17. 02 Aug, 2013 1 commit
  18. 24 Jul, 2013 1 commit
  19. 09 May, 2013 1 commit
    • Michal Simek's avatar
      gpio: Add support for microblaze xilinx GPIO · 4e779ad2
      Michal Simek authored
      Microblaze uses gpio which is connected to the system reset.
      Currently gpio subsystem wasn't used for it.
      
      Add gpio driver and change Microblaze reset logic to be done
      via gpio subsystem.
      
      There are various configurations which Microblaze can have
      that's why gpio_alloc/gpio_alloc_dual(for dual channel)
      function has been introduced and gpio can be allocated
      dynamically.
      
      Adding several gpios IP is also possible and supported.
      
      For listing gpio configuration please use "gpio status" command
      
      This patch also remove one compilation warning:
      microblaze-generic.c: In function 'do_reset':
      microblaze-generic.c:38:47: warning: operation on '*1073741824u'
       may be undefined [-Wsequence-point]
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      4e779ad2
  20. 06 May, 2013 1 commit
  21. 30 Apr, 2013 7 commits