1. 18 Apr, 2015 1 commit
  2. 24 Oct, 2014 1 commit
  3. 23 Jul, 2014 1 commit
    • Simon Glass's avatar
      dm: Allow drivers to be marked 'before relocation' · 00606d7e
      Simon Glass authored
      Driver model currently only operates after relocation is complete. In this
      state U-Boot typically has a small amount of memory available. In adding
      support for driver model prior to relocation we must try to use as little
      memory as possible.
      In addition, on some machines the memory has not be inited and/or the CPU
      is not running at full speed or the data cache is off. These can reduce
      execution performance, so the less initialisation that is done before
      relocation the better.
      An immediately-obvious improvement is to only initialise drivers which are
      actually going to be used before relocation. On many boards the only such
      driver is a serial UART, so this provides a very large potential benefit.
      Allow drivers to mark themselves as 'pre-reloc' which means that they will
      be initialised prior to relocation. This can be done either with a driver
      flag or with a 'dm,pre-reloc' device tree property.
      To support this, the various dm scanning function now take a 'pre_reloc_only'
      parameter which indicates that only drivers marked pre-reloc should be
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  4. 27 May, 2014 1 commit
    • Heiko Schocher's avatar
      dm: rename device struct to udevice · 54c5d08a
      Heiko Schocher authored
      using UBI and DM together leads in compiler error, as
      both define a "struct device", so rename "struct device"
      in include/dm/device.h to "struct udevice", as we use
      linux code (MTD/UBI/UBIFS some USB code,...) and cannot
      change the linux "struct device"
      Signed-off-by: default avatarHeiko Schocher <hs@denx.de>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Marek Vasut <marex@denx.de>
  5. 04 Mar, 2014 1 commit
    • Simon Glass's avatar
      dm: Add basic tests · 2e7d35d2
      Simon Glass authored
      Add some tests of driver model functionality. Coverage includes:
      - basic init
      - binding of drivers to devices using platform_data
      - automatic probing of devices when referenced
      - availability of platform data to devices
      - lifecycle from bind to probe to remove to unbind
      - renumbering within a uclass when devices are probed/removed
      - calling driver-defined operations
      - deactivation of drivers when removed
      - memory leak across creation and destruction of drivers/uclasses
      - uclass init/destroy methods
      - automatic probe/remove of children/parents when needed
      This function is enabled for sandbox, using CONFIG_DM_TEST.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>