0001 .. SPDX-License-Identifier: GPL-2.0
0002
0003 ====================
0004 mlx4 devlink support
0005 ====================
0006
0007 This document describes the devlink features implemented by the ``mlx4``
0008 device driver.
0009
0010 Parameters
0011 ==========
0012
0013 .. list-table:: Generic parameters implemented
0014
0015 * - Name
0016 - Mode
0017 * - ``internal_err_reset``
0018 - driverinit, runtime
0019 * - ``max_macs``
0020 - driverinit
0021 * - ``region_snapshot_enable``
0022 - driverinit, runtime
0023
0024 The ``mlx4`` driver also implements the following driver-specific
0025 parameters.
0026
0027 .. list-table:: Driver-specific parameters implemented
0028 :widths: 5 5 5 85
0029
0030 * - Name
0031 - Type
0032 - Mode
0033 - Description
0034 * - ``enable_64b_cqe_eqe``
0035 - Boolean
0036 - driverinit
0037 - Enable 64 byte CQEs/EQEs, if the FW supports it.
0038 * - ``enable_4k_uar``
0039 - Boolean
0040 - driverinit
0041 - Enable using the 4k UAR.
0042
0043 The ``mlx4`` driver supports reloading via ``DEVLINK_CMD_RELOAD``
0044
0045 Regions
0046 =======
0047
0048 The ``mlx4`` driver supports dumping the firmware PCI crspace and health
0049 buffer during a critical firmware issue.
0050
0051 In case a firmware command times out, firmware getting stuck, or a non zero
0052 value on the catastrophic buffer, a snapshot will be taken by the driver.
0053
0054 The ``cr-space`` region will contain the firmware PCI crspace contents. The
0055 ``fw-health`` region will contain the device firmware's health buffer.
0056 Snapshots for both of these regions are taken on the same event triggers.
