1. 13 Sep, 2014 1 commit
  2. 10 Sep, 2014 1 commit
    • Simon Glass's avatar
      tegra: Convert tegra GPIO driver to use driver model · 2fccd2d9
      Simon Glass authored
      This is an implementation of GPIOs for Tegra that uses driver model. It has
      been tested on trimslice and also using the new iotrace feature.
      
      The implementation uses a top-level GPIO device (which has no actual GPIOS).
      Under this all the banks are created as separate GPIO devices.
      
      The GPIOs are named as per the Tegra datasheet/header files: A0..A7, B0..B7,
      ..., Z0..Z7, AA0..AA7, etc.
      
      Since driver model is not yet available before relocation, or in SPL, a
      special function is provided for seaboard's SPL code.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      2fccd2d9
  3. 31 Aug, 2014 1 commit
  4. 19 Aug, 2014 1 commit
  5. 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
  6. 13 May, 2014 4 commits
  7. 17 Apr, 2014 8 commits
  8. 26 Mar, 2014 1 commit
  9. 20 Feb, 2014 1 commit
  10. 19 Feb, 2014 2 commits
    • Masahiro Yamada's avatar
      dts: move device tree sources to arch/$(ARCH)/dts/ · 5ab502cb
      Masahiro Yamada authored
      Unlike Linux Kernel, U-Boot historically had *.dts files under
      board/$(VENDOR)/dts/ and *.dtsi files under arch/$(ARCH)/dts/.
      
      I think arch/$(ARCH)/dts dicretory is a better location
      to store both *.dts and *.dtsi files.
      
      For example, before this commit, board/xilinx/dts directory
      had both Microblaze dts (microblaze-generic.dts) and
      ARM dts (zynq-*.dts), which are totally unrelated.
      
      This commit moves *.dts to arch/$(ARCH)/dts/ directories,
      allowing us to describe nicely mutiple DTBs generation in the next commit.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      5ab502cb
    • Masahiro Yamada's avatar
      kbuild: change out-of-tree build · 9e414032
      Masahiro Yamada authored
      This commit changes the working directory
      where the build process occurs.
      
      Before this commit, build process occurred under the source
      tree for both in-tree and out-of-tree build.
      
      That's why we needed to add $(obj) prefix to all generated
      files in makefiles like follows:
        $(obj)u-boot.bin:  $(obj)u-boot
      
      Here, $(obj) is empty for in-tree build, whereas it points
      to the output directory for out-of-tree build.
      
      And our old build system changes the current working directory
      with "make -C <sub-dir>" syntax when descending into the
      sub-directories.
      
      On the other hand, Kbuild uses a different idea
      to handle out-of-tree build and directory descending.
      
      The build process of Kbuild always occurs under the output tree.
      When "O=dir/to/store/output/files" is given, the build system
      changes the current working directory to that directory and
      restarts the make.
      
      Kbuild uses "make -f $(srctree)/scripts/Makefile.build obj=<sub-dir>"
      syntax for descending into sub-directories.
      (We can write it like "make $(obj)=<sub-dir>" with a shorthand.)
      This means the current working directory is always the top
      of the output directory.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Tested-by: default avatarGerhard Sittig <gsi@denx.de>
      9e414032
  11. 03 Feb, 2014 3 commits
  12. 24 Jan, 2014 1 commit
  13. 17 Nov, 2013 1 commit
  14. 01 Nov, 2013 2 commits
  15. 20 Oct, 2013 1 commit
  16. 24 Jul, 2013 1 commit
  17. 23 Jul, 2013 1 commit
  18. 11 Jul, 2013 4 commits
  19. 28 May, 2013 1 commit
  20. 15 Apr, 2013 2 commits
  21. 25 Mar, 2013 1 commit