drivers/staging/vme_user/vme_tsi148.h
Source file repositories/reference/linux-study-clean/drivers/staging/vme_user/vme_tsi148.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/vme_user/vme_tsi148.h- Extension
.h- Size
- 55580 bytes
- Lines
- 1393
- Domain
- Driver Families
- Bucket
- drivers/staging
- 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.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
struct tsi148_driverstruct tsi148_dma_descriptorstruct tsi148_dma_entry
Annotated Snippet
struct tsi148_driver {
void __iomem *base; /* Base Address of device registers */
wait_queue_head_t dma_queue[2];
wait_queue_head_t iack_queue;
void (*lm_callback[4])(void *); /* Called in interrupt handler */
void *lm_data[4];
void *crcsr_kernel;
dma_addr_t crcsr_bus;
struct vme_master_resource *flush_image;
struct mutex vme_rmw; /* Only one RMW cycle at a time */
struct mutex vme_int; /*
* Only one VME interrupt can be
* generated at a time, provide locking
*/
};
/*
* Layout of a DMAC Linked-List Descriptor
*
* Note: This structure is accessed via the chip and therefore must be
* correctly laid out - It must also be aligned on 64-bit boundaries.
*/
struct tsi148_dma_descriptor {
__be32 dsau; /* Source Address */
__be32 dsal;
__be32 ddau; /* Destination Address */
__be32 ddal;
__be32 dsat; /* Source attributes */
__be32 ddat; /* Destination attributes */
__be32 dnlau; /* Next link address */
__be32 dnlal;
__be32 dcnt; /* Byte count */
__be32 ddbs; /* 2eSST Broadcast select */
};
struct tsi148_dma_entry {
/*
* The descriptor needs to be aligned on a 64-bit boundary, we increase
* the chance of this by putting it first in the structure.
*/
struct tsi148_dma_descriptor descriptor;
struct list_head list;
dma_addr_t dma_handle;
};
/*
* TSI148 ASIC register structure overlays and bit field definitions.
*
* Note: Tsi148 Register Group (CRG) consists of the following
* combination of registers:
* PCFS - PCI Configuration Space Registers
* LCSR - Local Control and Status Registers
* GCSR - Global Control and Status Registers
* CR/CSR - Subset of Configuration ROM /
* Control and Status Registers
*/
/*
* Command/Status Registers (CRG + $004)
*/
#define TSI148_PCFS_ID 0x0
#define TSI148_PCFS_CSR 0x4
#define TSI148_PCFS_CLASS 0x8
#define TSI148_PCFS_MISC0 0xC
#define TSI148_PCFS_MBARL 0x10
#define TSI148_PCFS_MBARU 0x14
#define TSI148_PCFS_SUBID 0x28
#define TSI148_PCFS_CAPP 0x34
#define TSI148_PCFS_MISC1 0x3C
#define TSI148_PCFS_XCAPP 0x40
#define TSI148_PCFS_XSTAT 0x44
/*
* LCSR definitions
*/
/*
* Outbound Translations
*/
#define TSI148_LCSR_OT0_OTSAU 0x100
#define TSI148_LCSR_OT0_OTSAL 0x104
#define TSI148_LCSR_OT0_OTEAU 0x108
#define TSI148_LCSR_OT0_OTEAL 0x10C
#define TSI148_LCSR_OT0_OTOFU 0x110
#define TSI148_LCSR_OT0_OTOFL 0x114
#define TSI148_LCSR_OT0_OTBS 0x118
#define TSI148_LCSR_OT0_OTAT 0x11C
#define TSI148_LCSR_OT1_OTSAU 0x120
#define TSI148_LCSR_OT1_OTSAL 0x124
Annotation
- Detected declarations: `struct tsi148_driver`, `struct tsi148_dma_descriptor`, `struct tsi148_dma_entry`.
- Atlas domain: Driver Families / drivers/staging.
- Implementation status: source implementation candidate.
- 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.