sound/aoa/soundbus/i2sbus/i2sbus.h
Source file repositories/reference/linux-study-clean/sound/aoa/soundbus/i2sbus/i2sbus.h
File Facts
- System
- Linux kernel
- Corpus path
sound/aoa/soundbus/i2sbus/i2sbus.h- Extension
.h- Size
- 3231 bytes
- Lines
- 125
- Domain
- Driver Families
- Bucket
- sound/aoa
- 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
linux/interrupt.hlinux/spinlock.hlinux/mutex.hlinux/completion.hsound/pcm.hasm/pmac_feature.hasm/dbdma.hinterface.h../soundbus.h
Detected Declarations
struct i2sbus_controlstruct dbdma_command_memstruct pcm_infostruct i2sbus_dev
Annotated Snippet
struct i2sbus_control {
struct list_head list;
struct macio_chip *macio;
};
#define MAX_DBDMA_COMMANDS 32
struct dbdma_command_mem {
dma_addr_t bus_addr;
dma_addr_t bus_cmd_start;
struct dbdma_cmd *cmds;
void *space;
int size;
u32 running:1;
u32 stopping:1;
};
struct pcm_info {
u32 created:1, /* has this direction been created with alsa? */
active:1; /* is this stream active? */
/* runtime information */
struct snd_pcm_substream *substream;
int current_period;
u32 frame_count;
struct dbdma_command_mem dbdma_ring;
volatile struct dbdma_regs __iomem *dbdma;
struct completion *stop_completion;
};
enum {
aoa_resource_i2smmio = 0,
aoa_resource_txdbdma,
aoa_resource_rxdbdma,
};
struct i2sbus_dev {
struct soundbus_dev sound;
struct macio_dev *macio;
struct i2sbus_control *control;
volatile struct i2s_interface_regs __iomem *intfregs;
struct resource resources[3];
struct resource *allocated_resource[3];
int interrupts[3];
char rnames[3][32];
/* info about currently active substreams */
struct pcm_info out, in;
snd_pcm_format_t format;
unsigned int rate;
/* list for a single controller */
struct list_head item;
/* number of bus on controller */
int bus_number;
/* for use by control layer */
struct pmf_function *enable,
*cell_enable,
*cell_disable,
*clock_enable,
*clock_disable;
/* locks */
/* spinlock for low-level interrupt locking */
spinlock_t low_lock;
/* mutex for high-level consistency */
struct mutex lock;
};
#define soundbus_dev_to_i2sbus_dev(sdev) \
container_of(sdev, struct i2sbus_dev, sound)
/* pcm specific functions */
extern int
i2sbus_attach_codec(struct soundbus_dev *dev, struct snd_card *card,
struct codec_info *ci, void *data);
extern void
i2sbus_detach_codec(struct soundbus_dev *dev, void *data);
extern irqreturn_t
i2sbus_tx_intr(int irq, void *devid);
extern irqreturn_t
i2sbus_rx_intr(int irq, void *devid);
extern void i2sbus_wait_for_stop_both(struct i2sbus_dev *i2sdev);
extern void i2sbus_pcm_prepare_both(struct i2sbus_dev *i2sdev);
/* control specific functions */
extern int i2sbus_control_init(struct macio_dev* dev,
struct i2sbus_control **c);
extern void i2sbus_control_destroy(struct i2sbus_control *c);
Annotation
- Immediate include surface: `linux/interrupt.h`, `linux/spinlock.h`, `linux/mutex.h`, `linux/completion.h`, `sound/pcm.h`, `asm/pmac_feature.h`, `asm/dbdma.h`, `interface.h`.
- Detected declarations: `struct i2sbus_control`, `struct dbdma_command_mem`, `struct pcm_info`, `struct i2sbus_dev`.
- Atlas domain: Driver Families / sound/aoa.
- 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.