ixgbe.rst 6.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171
  1. .. SPDX-License-Identifier: GPL-2.0
  2. =====================
  3. ixgbe devlink support
  4. =====================
  5. This document describes the devlink features implemented by the ``ixgbe``
  6. device driver.
  7. Info versions
  8. =============
  9. Any of the versions dealing with the security presented by ``devlink-info``
  10. is purely informational. Devlink does not use a secure channel to communicate
  11. with the device.
  12. The ``ixgbe`` driver reports the following versions
  13. .. list-table:: devlink info versions implemented
  14. :widths: 5 5 5 90
  15. * - Name
  16. - Type
  17. - Example
  18. - Description
  19. * - ``board.id``
  20. - fixed
  21. - H49289-000
  22. - The Product Board Assembly (PBA) identifier of the board.
  23. * - ``fw.undi``
  24. - running
  25. - 1.1937.0
  26. - Version of the Option ROM containing the UEFI driver. The version is
  27. reported in ``major.minor.patch`` format. The major version is
  28. incremented whenever a major breaking change occurs, or when the
  29. minor version would overflow. The minor version is incremented for
  30. non-breaking changes and reset to 1 when the major version is
  31. incremented. The patch version is normally 0 but is incremented when
  32. a fix is delivered as a patch against an older base Option ROM.
  33. * - ``fw.undi.srev``
  34. - running
  35. - 4
  36. - Number indicating the security revision of the Option ROM.
  37. * - ``fw.bundle_id``
  38. - running
  39. - 0x80000d0d
  40. - Unique identifier of the firmware image file that was loaded onto
  41. the device. Also referred to as the EETRACK identifier of the NVM.
  42. * - ``fw.mgmt.api``
  43. - running
  44. - 1.5.1
  45. - 3-digit version number (major.minor.patch) of the API exported over
  46. the AdminQ by the management firmware. Used by the driver to
  47. identify what commands are supported. Historical versions of the
  48. kernel only displayed a 2-digit version number (major.minor).
  49. * - ``fw.mgmt.build``
  50. - running
  51. - 0x305d955f
  52. - Unique identifier of the source for the management firmware.
  53. * - ``fw.mgmt.srev``
  54. - running
  55. - 3
  56. - Number indicating the security revision of the firmware.
  57. * - ``fw.psid.api``
  58. - running
  59. - 0.80
  60. - Version defining the format of the flash contents.
  61. * - ``fw.netlist``
  62. - running
  63. - 1.1.2000-6.7.0
  64. - The version of the netlist module. This module defines the device's
  65. Ethernet capabilities and default settings, and is used by the
  66. management firmware as part of managing link and device
  67. connectivity.
  68. * - ``fw.netlist.build``
  69. - running
  70. - 0xee16ced7
  71. - The first 4 bytes of the hash of the netlist module contents.
  72. Flash Update
  73. ============
  74. The ``ixgbe`` driver implements support for flash update using the
  75. ``devlink-flash`` interface. It supports updating the device flash using a
  76. combined flash image that contains the ``fw.mgmt``, ``fw.undi``, and
  77. ``fw.netlist`` components.
  78. .. list-table:: List of supported overwrite modes
  79. :widths: 5 95
  80. * - Bits
  81. - Behavior
  82. * - ``DEVLINK_FLASH_OVERWRITE_SETTINGS``
  83. - Do not preserve settings stored in the flash components being
  84. updated. This includes overwriting the port configuration that
  85. determines the number of physical functions the device will
  86. initialize with.
  87. * - ``DEVLINK_FLASH_OVERWRITE_SETTINGS`` and ``DEVLINK_FLASH_OVERWRITE_IDENTIFIERS``
  88. - Do not preserve either settings or identifiers. Overwrite everything
  89. in the flash with the contents from the provided image, without
  90. performing any preservation. This includes overwriting device
  91. identifying fields such as the MAC address, Vital product Data (VPD) area,
  92. and device serial number. It is expected that this combination be used with an
  93. image customized for the specific device.
  94. Reload
  95. ======
  96. The ``ixgbe`` driver supports activating new firmware after a flash update
  97. using ``DEVLINK_CMD_RELOAD`` with the ``DEVLINK_RELOAD_ACTION_FW_ACTIVATE``
  98. action.
  99. .. code:: shell
  100. $ devlink dev reload pci/0000:01:00.0 reload action fw_activate
  101. The new firmware is activated by issuing a device specific Embedded
  102. Management Processor reset which requests the device to reset and reload the
  103. EMP firmware image.
  104. The driver does not currently support reloading the driver via
  105. ``DEVLINK_RELOAD_ACTION_DRIVER_REINIT``.
  106. Regions
  107. =======
  108. The ``ixgbe`` driver implements the following regions for accessing internal
  109. device data.
  110. .. list-table:: regions implemented
  111. :widths: 15 85
  112. * - Name
  113. - Description
  114. * - ``nvm-flash``
  115. - The contents of the entire flash chip, sometimes referred to as
  116. the device's Non Volatile Memory.
  117. * - ``shadow-ram``
  118. - The contents of the Shadow RAM, which is loaded from the beginning
  119. of the flash. Although the contents are primarily from the flash,
  120. this area also contains data generated during device boot which is
  121. not stored in flash.
  122. * - ``device-caps``
  123. - The contents of the device firmware's capabilities buffer. Useful to
  124. determine the current state and configuration of the device.
  125. Both the ``nvm-flash`` and ``shadow-ram`` regions can be accessed without a
  126. snapshot. The ``device-caps`` region requires a snapshot as the contents are
  127. sent by firmware and can't be split into separate reads.
  128. Users can request an immediate capture of a snapshot for all three regions
  129. via the ``DEVLINK_CMD_REGION_NEW`` command.
  130. .. code:: shell
  131. $ devlink region show
  132. pci/0000:01:00.0/nvm-flash: size 10485760 snapshot [] max 1
  133. pci/0000:01:00.0/device-caps: size 4096 snapshot [] max 10
  134. $ devlink region new pci/0000:01:00.0/nvm-flash snapshot 1
  135. $ devlink region dump pci/0000:01:00.0/nvm-flash snapshot 1
  136. 0000000000000000 0014 95dc 0014 9514 0035 1670 0034 db30
  137. 0000000000000010 0000 0000 ffff ff04 0029 8c00 0028 8cc8
  138. 0000000000000020 0016 0bb8 0016 1720 0000 0000 c00f 3ffc
  139. 0000000000000030 bada cce5 bada cce5 bada cce5 bada cce5
  140. $ devlink region read pci/0000:01:00.0/nvm-flash snapshot 1 address 0 length 16
  141. 0000000000000000 0014 95dc 0014 9514 0035 1670 0034 db30
  142. $ devlink region delete pci/0000:01:00.0/device-caps snapshot 1