1. 04 6月, 2016 1 次提交
    • M
      usb: move CONFIG_USB_XHCI to Kconfig with renaming · 0a8cc1a3
      Masahiro Yamada 提交于
      Move CONFIG_USB_XHCI to defconfig files for all boards, renaming it
      into CONFIG_USB_XHCI_HCD.
      
      As commented in the help of "config USB_XHCI" entry, this has been
      a TODO for a long time; now CONFIG_USB_XHCI_HCD and CONFIG_USB_XHCI
      have been unified in favor of the former.
      
      Note:
      Some boards define CONFIG_USB_XHCI in their headers without
      CONFIG_USB, which does not meet the "depends on" in Kconfig.
      I added CONFIG_USB=y for those boards when converting.
      Otherwise, they would fail to build.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      0a8cc1a3
  2. 26 4月, 2016 3 次提交
  3. 19 4月, 2016 1 次提交
  4. 15 3月, 2016 1 次提交
  5. 22 11月, 2015 1 次提交
  6. 19 11月, 2015 1 次提交
  7. 18 11月, 2015 1 次提交
    • K
      board: ti: beagle_x15: Rename to indicate support for TI am57xx evms · 74cc8b09
      Kipisz, Steven 提交于
      BeagleBoard X15 (http://beagleboard.org/x15) support in u-boot does
      actually support two different platform configuration offered by
      TI. In addition to BeagleBoard X15, it also supports the TMDXEVM5728
      (or more commonly known as AM5728-evm).
      
      Information about the TI AM57xx EVM can be found here
      http://www.ti.com/tool/tmdxevm5728
      
      The EVM configuration is 1-1 compatible with BeagleBoard X15 with the
      additional support for mPCIe, mSATA, LCD, touchscreen, Camera, push
      button and TI's wlink8 offering.
      
      Hence, we rename the beagle_x15 directory to am57xx to support TI
      EVMs that use the AM57xx processor. By doing this we have common code
      reuse. This sets the stage to have a common u-boot image solution for
      multiple TI EVMs such as that already done for am335x and am437x. This
      sets the stage for upcoming multiple TI EVMs that share the same code
      base.
      
      NOTE: Commit eae7ae18 ("am437x: Add am57xx_evm_defconfig using
      CONFIG_DM") introduced DT support for beagle_x15 under am57xx_evm
      platform name. However, this ignored the potential confusion arising for
      users as a result. To prevent this, existing beagle_x15_defconfig is
      renamed as am57xx_evm_nodt_defconfig to denote that this is the "non
      device tree" configuration for the same platform. We still retain
      am57xx-beagle-x15.dts at this point, since we just require the common
      minimum dts.
      
      As a result of this change, users should expect changes in build
      procedures('make am57xx_evm_nodt_defconfig' instead of 'make
      beagle_x15_defconfig'). Hopefully, this would be a one-time change.
      Signed-off-by: NSteve Kipisz <s-kipisz2@ti.com>
      Signed-off-by: NSchuyler Patton <spatton@ti.com>
      Acked-by: NNishanth Menon <nm@ti.com>
      Acked-by: NLokesh Vutla <lokeshvutla@ti.com>
      74cc8b09
  8. 26 6月, 2015 1 次提交
  9. 01 6月, 2015 1 次提交
  10. 13 5月, 2015 1 次提交
  11. 16 3月, 2015 1 次提交
  12. 05 12月, 2014 1 次提交