drivers/gpib/eastwood/fluke_gpib.c

File Facts

System

Linux kernel

Corpus path

drivers/gpib/eastwood/fluke_gpib.c

Extension

.c

Size

34849 bytes

Lines

1180

Domain

Driver Families

Bucket

drivers/gpib

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• fluke_gpib.h
• gpibP.h
• linux/dma-mapping.h
• linux/ioport.h
• linux/module.h
• linux/mod_devicetable.h
• linux/platform_device.h
• linux/slab.h

Detected Declarations

• function fluke_locking_read_byte
• function fluke_locking_write_byte
• function fluke_read
• function fluke_write
• function fluke_command
• function fluke_take_control
• function fluke_go_to_standby
• function fluke_request_system_control
• function fluke_interface_clear
• function fluke_remote_enable
• function fluke_enable_eos
• function fluke_disable_eos
• function fluke_update_status
• function fluke_primary_address
• function fluke_secondary_address
• function fluke_parallel_poll
• function fluke_parallel_poll_configure
• function fluke_parallel_poll_response
• function fluke_serial_poll_response
• function fluke_serial_poll_status
• function fluke_return_to_local
• function fluke_line_status
• function fluke_t1_delay
• function lacs_or_read_ready
• function wait_for_read
• function chip
• function source_handshake_is_sids_or_sgns
• function wait_for_data_out_ready
• function wait_for_sids_or_sgns
• function fluke_dma_callback
• function fluke_dma_write
• function test_bit
• function fluke_accel_write
• function fluke_get_dma_residue
• function fluke_dma_read
• function test_bit
• function fluke_accel_read
• function fluke_gpib_internal_interrupt
• function fluke_gpib_interrupt
• function fluke_allocate_private
• function fluke_generic_detach
• function fluke_generic_attach
• function fluke_config_dma
• function fluke_init
• function dma_request_channel
• function fluke_attach_impl
• function resource_size
• function fluke_attach_holdoff_all

Annotated Snippet

module_init(fluke_init_module);
module_exit(fluke_exit_module);

Annotation

• Immediate include surface: `fluke_gpib.h`, `gpibP.h`, `linux/dma-mapping.h`, `linux/ioport.h`, `linux/module.h`, `linux/mod_devicetable.h`, `linux/platform_device.h`, `linux/slab.h`.
• Detected declarations: `function fluke_locking_read_byte`, `function fluke_locking_write_byte`, `function fluke_read`, `function fluke_write`, `function fluke_command`, `function fluke_take_control`, `function fluke_go_to_standby`, `function fluke_request_system_control`, `function fluke_interface_clear`, `function fluke_remote_enable`.
• Atlas domain: Driver Families / drivers/gpib.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.