Documentation/networking/devlink/kvaser_usb.rst

Source file repositories/reference/linux-study-clean/Documentation/networking/devlink/kvaser_usb.rst

File Facts

System: Linux kernel
Corpus path: Documentation/networking/devlink/kvaser_usb.rst
Extension: .rst
Size: 782 bytes
Lines: 34
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

.. SPDX-License-Identifier: GPL-2.0

==========================
kvaser_usb devlink support
==========================

This document describes the devlink features implemented by the
``kvaser_usb`` device driver.

Info versions
=============

The ``kvaser_usb`` driver reports the following versions

.. list-table:: devlink info versions implemented
   :widths: 5 5 90

   * - Name
     - Type
     - Description
   * - ``fw``
     - running
     - Version of the firmware running on the device. Also available
       through ``ethtool -i`` as ``firmware-version``.
   * - ``board.rev``
     - fixed
     - The device hardware revision.
   * - ``board.id``
     - fixed
     - The device EAN (product number).
   * - ``serial_number``
     - fixed
     - The device serial number.

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.