Documentation/ABI/testing/sysfs-class-net-peak_usb

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-class-net-peak_usb

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-class-net-peak_usb
Extension: [no extension]
Size: 850 bytes
Lines: 20
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

What:		/sys/class/net/<iface>/peak_usb/can_channel_id
Date:		November 2022
KernelVersion:	6.2
Contact:	Stephane Grosjean <s.grosjean@peak-system.com>
Description:
		PEAK PCAN-USB devices support user-configurable CAN channel
		identifiers. Contrary to a USB serial number, these identifiers
		are writable and can be set per CAN interface. This means that
		if a USB device exports multiple CAN interfaces, each of them
		can be assigned a unique channel ID.
		This attribute provides read-only access to the currently
		configured value of the channel identifier. Depending on the
		device type, the identifier has a length of 8 or 32 bit. The
		value read from this attribute is always an 8 digit 32 bit
		hexadecimal value in big endian format. If the device only
		supports an 8 bit identifier, the upper 24 bit of the value are
		set to zero.

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.