drivers/soundwire/irq.h

File Facts

System

Linux kernel

Corpus path

drivers/soundwire/irq.h

Extension

.h

Size

794 bytes

Lines

39

Domain

Driver Families

Bucket

drivers/soundwire

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/soundwire/sdw.h
• linux/fwnode.h

Detected Declarations

• function sdw_irq_create
• function sdw_irq_delete

Annotated Snippet

#ifndef __SDW_IRQ_H
#define __SDW_IRQ_H

#include <linux/soundwire/sdw.h>
#include <linux/fwnode.h>

#if IS_ENABLED(CONFIG_IRQ_DOMAIN)

int sdw_irq_create(struct sdw_bus *bus,
		   struct fwnode_handle *fwnode);
void sdw_irq_delete(struct sdw_bus *bus);
void sdw_irq_create_mapping(struct sdw_slave *slave);

#else /* CONFIG_IRQ_DOMAIN */

static inline int sdw_irq_create(struct sdw_bus *bus,
				 struct fwnode_handle *fwnode)
{
	return 0;
}

static inline void sdw_irq_delete(struct sdw_bus *bus)
{
}

static inline void sdw_irq_create_mapping(struct sdw_slave *slave)
{
}

#endif /* CONFIG_IRQ_DOMAIN */

#endif /* __SDW_IRQ_H */

Annotation

• Immediate include surface: `linux/soundwire/sdw.h`, `linux/fwnode.h`.
• Detected declarations: `function sdw_irq_create`, `function sdw_irq_delete`.
• Atlas domain: Driver Families / drivers/soundwire.
• 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.