drivers/staging/most/Documentation/ABI/sysfs-class-most.txt
Source file repositories/reference/linux-study-clean/drivers/staging/most/Documentation/ABI/sysfs-class-most.txt
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/most/Documentation/ABI/sysfs-class-most.txt- Extension
.txt- Size
- 9364 bytes
- Lines
- 316
- Domain
- Driver Families
- Bucket
- drivers/staging
- Inferred role
- Driver Families: documentation
- Status
- atlas-only
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
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/most/mostcore/aims
Date: June 2015
KernelVersion: 4.3
Contact: Christian Gromm <christian.gromm@microchip.com>
Description:
List of AIMs that have been loaded.
Users:
What: /sys/class/most/mostcore/aims/<aim>/add_link
Date: June 2015
KernelVersion: 4.3
Contact: Christian Gromm <christian.gromm@microchip.com>
Description:
This is used to establish a connection of a channel and the
current AIM.
Users:
What: /sys/class/most/mostcore/aims/<aim>/remove_link
Date: June 2015
KernelVersion: 4.3
Contact: Christian Gromm <christian.gromm@microchip.com>
Description:
This is used to remove a connected channel from the
current AIM.
Users:
What: /sys/class/most/mostcore/devices
Date: June 2015
KernelVersion: 4.3
Contact: Christian Gromm <christian.gromm@microchip.com>
Description:
List of attached MOST interfaces.
Users:
What: /sys/class/most/mostcore/devices/<mdev>/description
Date: June 2015
KernelVersion: 4.3
Contact: Christian Gromm <christian.gromm@microchip.com>
Description:
Provides information about the interface type and the physical
location of the device. Hardware attached via USB, for instance,
might return <usb_device 1-1.1:1.0>
Users:
What: /sys/class/most/mostcore/devices/<mdev>/interface
Date: June 2015
KernelVersion: 4.3
Contact: Christian Gromm <christian.gromm@microchip.com>
Description:
Indicates the type of peripheral interface the current device
uses.
Users:
What: /sys/class/most/mostcore/devices/<mdev>/dci
Date: June 2016
KernelVersion: 4.9
Contact: Christian Gromm <christian.gromm@microchip.com>
Description:
If the network interface controller is attached via USB, a dci
directory is created that allows applications to use the
controller's direct communication interface (DCI) to exchange
information.
Users:
What: /sys/class/most/mostcore/devices/<mdev>/dci/arb_address
Date: June 2016
KernelVersion: 4.9
Contact: Christian Gromm <christian.gromm@microchip.com>
Description:
This is used to set an arbitrary DCI register address an
Annotation
- Atlas domain: Driver Families / drivers/staging.
- 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.