Overview.txt 2.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. TI Keystone Linux Overview
  2. --------------------------
  3. Introduction
  4. ------------
  5. Keystone range of SoCs are based on ARM Cortex-A15 MPCore Processors
  6. and c66x DSP cores. This document describes essential information required
  7. for users to run Linux on Keystone based EVMs from Texas Instruments.
  8. Following SoCs & EVMs are currently supported:-
  9. ------------ K2HK SoC and EVM --------------------------------------------------
  10. a.k.a Keystone 2 Hawking/Kepler SoC
  11. TCI6636K2H & TCI6636K2K: See documentation at
  12. http://www.ti.com/product/tci6638k2k
  13. http://www.ti.com/product/tci6638k2h
  14. EVM:
  15. http://www.advantech.com/Support/TI-EVM/EVMK2HX_sd.aspx
  16. ------------ K2E SoC and EVM ---------------------------------------------------
  17. a.k.a Keystone 2 Edison SoC
  18. K2E - 66AK2E05: See documentation at
  19. http://www.ti.com/product/66AK2E05/technicaldocuments
  20. EVM:
  21. https://www.einfochips.com/index.php/partnerships/texas-instruments/k2e-evm.html
  22. ------------ K2L SoC and EVM ---------------------------------------------------
  23. a.k.a Keystone 2 Lamarr SoC
  24. K2L - TCI6630K2L: See documentation at
  25. http://www.ti.com/product/TCI6630K2L/technicaldocuments
  26. EVM:
  27. https://www.einfochips.com/index.php/partnerships/texas-instruments/k2l-evm.html
  28. Configuration
  29. -------------
  30. All of the K2 SoCs/EVMs share a common defconfig, keystone_defconfig and same
  31. image is used to boot on individual EVMs. The platform configuration is
  32. specified through DTS. Following are the DTS used:-
  33. K2HK EVM : k2hk-evm.dts
  34. K2E EVM : k2e-evm.dts
  35. K2L EVM : k2l-evm.dts
  36. The device tree documentation for the keystone machines are located at
  37. Documentation/devicetree/bindings/arm/keystone/keystone.txt
  38. Known issues & workaround
  39. -------------------------
  40. Some of the device drivers used on keystone are re-used from that from
  41. DaVinci and other TI SoCs. These device drivers may use clock APIs directly.
  42. Some of the keystone specific drivers such as netcp uses run time power
  43. management API instead to enable clock. As this API has limitations on
  44. keystone, following workaround is needed to boot Linux.
  45. Add 'clk_ignore_unused' to the bootargs env variable in u-boot. Otherwise
  46. clock frameworks will try to disable clocks that are unused and disable
  47. the hardware. This is because netcp related power domain and clock
  48. domains are enabled in u-boot as run time power management API currently
  49. doesn't enable clocks for netcp due to a limitation. This workaround is
  50. expected to be removed in the future when proper API support becomes
  51. available. Until then, this work around is needed.
  52. Document Author
  53. ---------------
  54. Murali Karicheri <m-karicheri2@ti.com>
  55. Copyright 2015 Texas Instruments