Skip to content
Snippets Groups Projects
  1. Feb 20, 2020
  2. Feb 07, 2020
    • Simon Glass's avatar
      dm: irq: Add support for interrupt controller types · ba876079
      Simon Glass authored
      
      There can be different types of interrupt controllers in a system and some
      drivers may need to distinguish between these. In general this can be
      handled using the device tree by adding the interrupt information to
      device nodes.
      
      However on x86 devices we have interrupt controllers which are not tied
      to any particular device and not really used in U-Boot. These still need
      to be inited, so a convenient method is to give each controller a type
      and allow a particular controller type to be probed.
      
      Add support for this in sandbox along with a test.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarBin Meng <bmeng.cn@gmail.com>
      [bmeng: remove the new bland line at EOF of test/dm/irq.c]
      Signed-off-by: default avatarBin Meng <bmeng.cn@gmail.com>
      ba876079
  3. Feb 06, 2020
  4. Dec 17, 2019
  5. Dec 15, 2019
  6. Oct 27, 2019
  7. Oct 22, 2019
  8. Oct 15, 2019
  9. Oct 08, 2019
  10. Jul 29, 2019
  11. Jul 11, 2019
  12. Jul 10, 2019
  13. Apr 24, 2019
    • Simon Glass's avatar
      sandbox: Improve debugging in initcall_run_list() · 001d1885
      Simon Glass authored
      
      At present if one of the initcalls fails on sandbox the address printing
      is not help, e.g.:
      
        initcall sequence 0000557678967c80 failed at call 00005576709dfe1f (err=-96)
      
      This is because U-Boot gets relocated high into memory and the relocation
      offset (gd->reloc_off) does not work correctly for sandbox.
      
      Add support for finding the base address of the text region (at least on
      Linux) and use that to set the relocation offset. This makes the output
      better:
      
        initcall sequence 0000560775957c80 failed at call 0000000000048134 (err=-96)
      
      Then you use can use grep to see which init call failed, e.g.:
      
         $ grep 0000000000048134 u-boot.map
         stdio_add_devices
      
      Of course another option is to run it with a debugger such as gdb:
      
         $ gdb u-boot
         ...
         (gdb) br initcall.h:41
         Breakpoint 1 at 0x4db9d: initcall.h:41. (2 locations)
      
      Note that two locations are reported, since this function is used in both
      board_init_f() and board_init_r().
      
         (gdb) r
         Starting program: /tmp/b/sandbox/u-boot
         [Thread debugging using libthread_db enabled]
         Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
      
         U-Boot 2018.09-00264-ge0c2ba9814-dirty (Sep 22 2018 - 12:21:46 -0600)
      
         DRAM:  128 MiB
         MMC:
      
      Breakpoint 1, initcall_run_list (init_sequence=0x5555559619e0 <init_sequence_f>)
          at /scratch/sglass/cosarm/src/third_party/u-boot/files/include/initcall.h:41
      41				printf("initcall sequence %p failed at call %p (err=%d)\n",
         (gdb) print *init_fnc_ptr
         $1 = (const init_fnc_t) 0x55555559c114 <stdio_add_devices>
         (gdb)
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      001d1885
  14. Apr 23, 2019
    • Neil Armstrong's avatar
      regmap: fix regmap_read_poll_timeout warning about sandbox_timer_add_offset · d0a9b82b
      Neil Armstrong authored
      
      When fixing sandbox test for regmap_read_poll_timeout(), the
      sandbox_timer_add_offset was introduced but only defined in sandbox code
      thus generating warnings when used out of sandbox :
      
      include/regmap.h:289:2: note: in expansion of macro 'regmap_read_poll_timeout_test'
      regmap_read_poll_timeout_test(map, addr, val, cond, sleep_us, \
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      drivers/spi/meson_spifc.c:169:8: note: in expansion of macro 'regmap_read_poll_timeout'
      ret = regmap_read_poll_timeout(spifc->regmap, REG_SLAVE, data,
              ^~~~~~~~~~~~~~~~~~~~~~~~
      drivers/spi/meson_spifc.c: In function 'meson_spifc_txrx':
      include/regmap.h:277:4: warning: implicit declaration of function 'sandbox_timer_add_offset' [-Wimplicit-function-declaration]
      
      This fix adds a timer_test_add_offset() only defined in sandbox, and
      renames the previous sandbox_timer_add_offset() to it.
      
      Cc: Simon Glass <sjg@chromium.org>
      Reported-by: default avatarTom Rini <trini@konsulko.com>
      Fixes: df9cf1cc ("test: dm: regmap: Fix the long test delay")
      Signed-off-by: default avatarNeil Armstrong <narmstrong@baylibre.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      d0a9b82b
  15. Apr 12, 2019
    • Christian Gmeiner's avatar
      dm: sound: make all functions static inline · 6539700d
      Christian Gmeiner authored
      
      Fixes following compile problem:
      ➜  u-boot-mainline git:(master) ✗ make sandbox_defconfig all NO_SDL=1
      scripts/kconfig/conf  --syncconfig Kconfig
        CHK     include/config.h
        CFG     u-boot.cfg
        GEN     include/autoconf.mk
        GEN     include/autoconf.mk.dep
        CHK     include/config/uboot.release
        CHK     include/generated/version_autogenerated.h
        CHK     include/generated/timestamp_autogenerated.h
        UPD     include/generated/timestamp_autogenerated.h
        CHK     include/generated/generic-asm-offsets.h
        HOSTCC  tools/mkenvimage.o
        HOSTLD  tools/mkenvimage
        HOSTCC  tools/fit_image.o
        HOSTCC  tools/image-host.o
        HOSTCC  tools/dumpimage.o
        HOSTLD  tools/dumpimage
        HOSTCC  tools/mkimage.o
        HOSTLD  tools/mkimage
        HOSTLD  tools/fit_info
        HOSTLD  tools/fit_check_sign
        CC      cmd/version.o
        GZIP    cmd/config_data.gz
        CHK     cmd/config_data_gz.h
        CHK     cmd/config_data_size.h
        CHK     cmd/license_data_gz.h
        CHK     cmd/license_data_size.h
        LD      cmd/built-in.o
        CC      common/main.o
        LD      common/built-in.o
        CC      drivers/fastboot/fb_getvar.o
        LD      drivers/fastboot/built-in.o
        LD      drivers/video/built-in.o
      ld.bfd: drivers/video/sandbox_sdl.o: in function `sandbox_sdl_sound_play':
      /home/christian/projects/u-boot-mainline/./arch/sandbox/include/asm/sdl.h:110: multiple definition of `sandbox_sdl_sound_play'; drivers/video/video-uclass.o:/home/christian/projects/u-boot-mainline/./arch/sandbox/include/asm/sdl.h:110: first defined here
      ld.bfd: drivers/video/sandbox_sdl.o: in function `sandbox_sdl_sound_init':
      /home/christian/projects/u-boot-mainline/./arch/sandbox/include/asm/sdl.h:120: multiple definition of `sandbox_sdl_sound_init'; drivers/video/video-uclass.o:/home/christian/projects/u-boot-mainline/./arch/sandbox/include/asm/sdl.h:120: first defined here
      make[3]: *** [scripts/Makefile.build:355: drivers/video/built-in.o] Fehler 1
      make[2]: *** [scripts/Makefile.build:432: drivers/video] Fehler 2
      make[1]: *** [Makefile:1531: drivers] Fehler 2
      make: *** [Makefile:485: __build_one_by_one] Fehler 2
      
      Fixes: f2b25c9b ("dm: sound: Complete migration to driver model")
      Signed-off-by: default avatarChristian Gmeiner <christian.gmeiner@gmail.com>
      6539700d
    • Thierry Reding's avatar
      sandbox: Use correct phys_{addr, size}_t for PHYS_64BIT=y · 0c425ae4
      Thierry Reding authored
      
      If 64-bit physical addresses support is enabled, make sure the sandox
      defines the correct types for phys_addr_t and phys_size_t.
      
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      0c425ae4
  16. Feb 20, 2019
  17. Jan 15, 2019
  18. Dec 13, 2018
  19. Dec 07, 2018
  20. Dec 05, 2018
  21. Nov 26, 2018
  22. Nov 21, 2018
Loading