drivers/gpib/agilent_82357a/agilent_82357a.h
Source file repositories/reference/linux-study-clean/drivers/gpib/agilent_82357a/agilent_82357a.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpib/agilent_82357a/agilent_82357a.h- Extension
.h- Size
- 4234 bytes
- Lines
- 183
- Domain
- Driver Families
- Bucket
- drivers/gpib
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/kernel.hlinux/mutex.hlinux/completion.hlinux/usb.hlinux/timer.hlinux/compiler_attributes.hgpibP.htms9914.h
Detected Declarations
struct agilent_82357a_urb_ctxstruct agilent_82357a_privstruct agilent_82357a_register_pairletenum usb_vendor_idsenum usb_device_idsenum endpoint_addressesenum bulk_commandsenum agilent_82357a_read_flagsenum agilent_82357a_trailing_read_flagsenum agilent_82357a_write_flagsenum agilent_82357a_interrupt_flag_bit_numbersenum agilent_82357_error_codesenum agilent_82357_control_valuesenum xfer_status_bitsenum xfer_status_completion_bitsenum xfer_abort_typeenum firmware_registersenum hardware_control_bitsenum led_control_bitsenum reset_to_powerup_bitsenum protocol_control_bits
Annotated Snippet
struct agilent_82357a_urb_ctx {
struct completion complete;
unsigned timed_out : 1;
};
// struct which defines local data for each 82357 device
struct agilent_82357a_priv {
struct usb_interface *bus_interface;
unsigned short eos_char;
unsigned short eos_mode;
unsigned short hw_control_bits;
unsigned long interrupt_flags;
struct urb *bulk_urb;
struct urb *interrupt_urb;
u8 *interrupt_buffer;
struct mutex bulk_transfer_lock; // bulk transfer lock
struct mutex bulk_alloc_lock; // bulk transfer allocation lock
struct mutex interrupt_alloc_lock; // interrupt allocation lock
struct mutex control_alloc_lock; // control message allocation lock
struct timer_list bulk_timer;
struct agilent_82357a_urb_ctx context;
unsigned int bulk_out_endpoint;
unsigned int interrupt_in_endpoint;
unsigned is_cic : 1;
unsigned ren_state : 1;
};
struct agilent_82357a_register_pairlet {
short address;
unsigned short value;
};
enum firmware_registers {
HW_CONTROL = 0xa,
LED_CONTROL = 0xb,
RESET_TO_POWERUP = 0xc,
PROTOCOL_CONTROL = 0xd,
FAST_TALKER_T1 = 0xe
};
enum hardware_control_bits {
NOT_TI_RESET = 0x1,
SYSTEM_CONTROLLER = 0x2,
NOT_PARALLEL_POLL = 0x4,
OSCILLATOR_5V_ON = 0x8,
OUTPUT_5V_ON = 0x20,
CPLD_3V_ON = 0x80,
};
enum led_control_bits {
FIRMWARE_LED_CONTROL = 0x1,
FAIL_LED_ON = 0x20,
READY_LED_ON = 0x40,
ACCESS_LED_ON = 0x80
};
enum reset_to_powerup_bits {
RESET_SPACEBALL = 0x1, // wait 2 millisec after sending
};
enum protocol_control_bits {
WRITE_COMPLETE_INTERRUPT_EN = 0x1,
};
static const int agilent_82357a_control_request = 0x4;
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/mutex.h`, `linux/completion.h`, `linux/usb.h`, `linux/timer.h`, `linux/compiler_attributes.h`, `gpibP.h`, `tms9914.h`.
- Detected declarations: `struct agilent_82357a_urb_ctx`, `struct agilent_82357a_priv`, `struct agilent_82357a_register_pairlet`, `enum usb_vendor_ids`, `enum usb_device_ids`, `enum endpoint_addresses`, `enum bulk_commands`, `enum agilent_82357a_read_flags`, `enum agilent_82357a_trailing_read_flags`, `enum agilent_82357a_write_flags`.
- Atlas domain: Driver Families / drivers/gpib.
- 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.