include/linux/usb/ljca.h
Source file repositories/reference/linux-study-clean/include/linux/usb/ljca.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/usb/ljca.h- Extension
.h- Size
- 4296 bytes
- Lines
- 146
- 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
linux/auxiliary_bus.hlinux/list.hlinux/spinlock.hlinux/types.h
Detected Declarations
struct ljca_adapterstruct ljca_clientstruct ljca_gpio_infostruct ljca_i2c_infostruct ljca_spi_info
Annotated Snippet
struct ljca_client {
u8 type;
u8 id;
struct list_head link;
struct auxiliary_device auxdev;
struct ljca_adapter *adapter;
void *context;
ljca_event_cb_t event_cb;
/* lock to protect event_cb */
spinlock_t event_cb_lock;
};
/**
* struct ljca_gpio_info - ljca gpio client device info
*
* @num: ljca gpio client device pin number
* @valid_pin_map: ljca gpio client device valid pin mapping
*/
struct ljca_gpio_info {
unsigned int num;
DECLARE_BITMAP(valid_pin_map, LJCA_MAX_GPIO_NUM);
};
/**
* struct ljca_i2c_info - ljca i2c client device info
*
* @id: ljca i2c client device identification number
* @capacity: ljca i2c client device capacity
* @intr_pin: ljca i2c client device interrupt pin number if exists
*/
struct ljca_i2c_info {
u8 id;
u8 capacity;
u8 intr_pin;
};
/**
* struct ljca_spi_info - ljca spi client device info
*
* @id: ljca spi client device identification number
* @capacity: ljca spi client device capacity
*/
struct ljca_spi_info {
u8 id;
u8 capacity;
};
/**
* ljca_register_event_cb - register a callback function to receive events
*
* @client: ljca client device
* @event_cb: callback function
* @context: execution context of event callback
*
* Return: 0 in case of success, negative value in case of error
*/
int ljca_register_event_cb(struct ljca_client *client, ljca_event_cb_t event_cb, void *context);
/**
* ljca_unregister_event_cb - unregister the callback function for an event
*
* @client: ljca client device
*/
void ljca_unregister_event_cb(struct ljca_client *client);
/**
* ljca_transfer - issue a LJCA command and wait for a response
*
* @client: ljca client device
* @cmd: the command to be sent to the device
* @obuf: the buffer to be sent to the device; it can be NULL if the user
* doesn't need to transmit data with this command
* @obuf_len: the size of the buffer to be sent to the device; it should
* be 0 when obuf is NULL
* @ibuf: any data associated with the response will be copied here; it can be
* NULL if the user doesn't need the response data
* @ibuf_len: must be initialized to the input buffer size
*
* Return: the actual length of response data for success, negative value for errors
*/
int ljca_transfer(struct ljca_client *client, u8 cmd, const u8 *obuf,
u8 obuf_len, u8 *ibuf, u8 ibuf_len);
/**
* ljca_transfer_noack - issue a LJCA command without a response
*
* @client: ljca client device
* @cmd: the command to be sent to the device
* @obuf: the buffer to be sent to the device; it can be NULL if the user
Annotation
- Immediate include surface: `linux/auxiliary_bus.h`, `linux/list.h`, `linux/spinlock.h`, `linux/types.h`.
- Detected declarations: `struct ljca_adapter`, `struct ljca_client`, `struct ljca_gpio_info`, `struct ljca_i2c_info`, `struct ljca_spi_info`.
- 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.