chosen.txt 2.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475
  1. The chosen node
  2. ---------------
  3. The chosen node does not represent a real device, but serves as a place
  4. for passing data like which serial device to used to print the logs etc
  5. stdout-path property
  6. --------------------
  7. Device trees may specify the device to be used for boot console output
  8. with a stdout-path property under /chosen.
  9. Example
  10. -------
  11. / {
  12. chosen {
  13. stdout-path = "/serial@f00:115200";
  14. };
  15. serial@f00 {
  16. compatible = "vendor,some-uart";
  17. reg = <0xf00 0x10>;
  18. };
  19. };
  20. tick-timer property
  21. -------------------
  22. In a system there are multiple timers, specify which timer to be used
  23. as the tick-timer. Earlier it was hardcoded in the timer driver now
  24. since device tree has all the timer nodes. Specify which timer to be
  25. used as tick timer.
  26. Example
  27. -------
  28. / {
  29. chosen {
  30. tick-timer = "/timer2@f00";
  31. };
  32. timer2@f00 {
  33. compatible = "vendor,some-timer";
  34. reg = <0xf00 0x10>;
  35. };
  36. };
  37. u-boot,spl-boot-order property
  38. ------------------------------
  39. In a system using an SPL stage and having multiple boot sources
  40. (e.g. SPI NOR flash, on-board eMMC and a removable SD-card), the boot
  41. device may be probed by reading the image and verifying an image
  42. signature.
  43. If the SPL is configured through the device-tree, the boot-order can
  44. be configured with the spl-boot-order property under the /chosen node.
  45. Each list element of the property should specify a device to be probed
  46. in the order they are listed: references (i.e. implicit paths), a full
  47. path or an alias is expected for each entry.
  48. A special specifier "same-as-spl" can be used at any position in the
  49. boot-order to direct U-Boot to insert the device the SPL was booted
  50. from there. Whether this is indeed inserted or silently ignored (if
  51. it is not supported on any given SoC/board or if the boot-device is
  52. not available to continue booting from) is implementation-defined.
  53. Note that if "same-as-spl" expands to an actual node for a given
  54. board, the corresponding node may appear multiple times in the
  55. boot-order (as there currently exists no mechanism to suppress
  56. duplicates from the list).
  57. Example
  58. -------
  59. / {
  60. chosen {
  61. u-boot,spl-boot-order = "same-as-spl", &sdmmc, "/sdhci@fe330000";
  62. };
  63. };