include/linux/usb/ch9.h
Source file repositories/reference/linux-study-clean/include/linux/usb/ch9.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/usb/ch9.h- Extension
.h- Size
- 2186 bytes
- Lines
- 61
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
uapi/linux/usb/ch9.h
Detected Declarations
struct deviceenum usb_ssp_rate
Annotated Snippet
#ifndef __LINUX_USB_CH9_H
#define __LINUX_USB_CH9_H
#include <uapi/linux/usb/ch9.h>
/* USB 3.2 SuperSpeed Plus phy signaling rate generation and lane count */
enum usb_ssp_rate {
USB_SSP_GEN_UNKNOWN = 0,
USB_SSP_GEN_2x1,
USB_SSP_GEN_1x2,
USB_SSP_GEN_2x2,
};
struct device;
extern const char *usb_ep_type_string(int ep_type);
extern const char *usb_speed_string(enum usb_device_speed speed);
extern enum usb_device_speed usb_get_maximum_speed(struct device *dev);
extern enum usb_ssp_rate usb_get_maximum_ssp_rate(struct device *dev);
extern const char *usb_state_string(enum usb_device_state state);
unsigned int usb_decode_interval(const struct usb_endpoint_descriptor *epd,
enum usb_device_speed speed);
#ifdef CONFIG_TRACING
extern const char *usb_decode_ctrl(char *str, size_t size, __u8 bRequestType,
__u8 bRequest, __u16 wValue, __u16 wIndex,
__u16 wLength);
#endif
#endif /* __LINUX_USB_CH9_H */
Annotation
- Immediate include surface: `uapi/linux/usb/ch9.h`.
- Detected declarations: `struct device`, `enum usb_ssp_rate`.
- Atlas domain: Core OS / Core Kernel Interface.
- Implementation status: source implementation candidate.
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.