drivers/net/ipa/ipa_interrupt.h
Source file repositories/reference/linux-study-clean/drivers/net/ipa/ipa_interrupt.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ipa/ipa_interrupt.h- Extension
.h- Size
- 3048 bytes
- Lines
- 109
- Domain
- Driver Families
- Bucket
- drivers/net
- 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/types.h
Detected Declarations
struct platform_devicestruct ipastruct ipa_interruptenum ipa_irq_id
Annotated Snippet
#ifndef _IPA_INTERRUPT_H_
#define _IPA_INTERRUPT_H_
#include <linux/types.h>
struct platform_device;
struct ipa;
struct ipa_interrupt;
enum ipa_irq_id;
/**
* ipa_interrupt_suspend_enable - Enable TX_SUSPEND for an endpoint
* @interrupt: IPA interrupt structure
* @endpoint_id: Endpoint whose interrupt should be enabled
*
* Note: The "TX" in the name is from the perspective of the IPA hardware.
* A TX_SUSPEND interrupt arrives on an AP RX enpoint when packet data can't
* be delivered to the endpoint because it is suspended (or its underlying
* channel is stopped).
*/
void ipa_interrupt_suspend_enable(struct ipa_interrupt *interrupt,
u32 endpoint_id);
/**
* ipa_interrupt_suspend_disable - Disable TX_SUSPEND for an endpoint
* @interrupt: IPA interrupt structure
* @endpoint_id: Endpoint whose interrupt should be disabled
*/
void ipa_interrupt_suspend_disable(struct ipa_interrupt *interrupt,
u32 endpoint_id);
/**
* ipa_interrupt_simulate_suspend() - Simulate TX_SUSPEND IPA interrupt
* @interrupt: IPA interrupt structure
*
* This calls the TX_SUSPEND interrupt handler, as if such an interrupt
* had been signaled. This is needed to work around a hardware quirk
* that occurs if aggregation is active on an endpoint when its underlying
* channel is suspended.
*/
void ipa_interrupt_simulate_suspend(struct ipa_interrupt *interrupt);
/**
* ipa_interrupt_enable() - Enable an IPA interrupt type
* @ipa: IPA pointer
* @ipa_irq: IPA interrupt ID
*/
void ipa_interrupt_enable(struct ipa *ipa, enum ipa_irq_id ipa_irq);
/**
* ipa_interrupt_disable() - Disable an IPA interrupt type
* @ipa: IPA pointer
* @ipa_irq: IPA interrupt ID
*/
void ipa_interrupt_disable(struct ipa *ipa, enum ipa_irq_id ipa_irq);
/**
* ipa_interrupt_irq_enable() - Enable IPA interrupts
* @ipa: IPA pointer
*
* This enables the IPA interrupt line
*/
void ipa_interrupt_irq_enable(struct ipa *ipa);
/**
* ipa_interrupt_irq_disable() - Disable IPA interrupts
* @ipa: IPA pointer
*
* This disables the IPA interrupt line
*/
void ipa_interrupt_irq_disable(struct ipa *ipa);
/**
* ipa_interrupt_config() - Configure IPA interrupts
* @ipa: IPA pointer
*
* Return: 0 if successful, or a negative error code
*/
int ipa_interrupt_config(struct ipa *ipa);
/**
* ipa_interrupt_deconfig() - Inverse of ipa_interrupt_config()
* @ipa: IPA pointer
*/
void ipa_interrupt_deconfig(struct ipa *ipa);
/**
* ipa_interrupt_init() - Initialize the IPA interrupt structure
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct platform_device`, `struct ipa`, `struct ipa_interrupt`, `enum ipa_irq_id`.
- Atlas domain: Driver Families / drivers/net.
- 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.