drivers/accel/amdxdna/amdxdna_pm.h

File Facts

System

Linux kernel

Corpus path

drivers/accel/amdxdna/amdxdna_pm.h

Extension

.h

Size

698 bytes

Lines

30

Domain

Driver Families

Bucket

drivers/accel

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• amdxdna_pci_drv.h

Detected Declarations

• function amdxdna_pm_resume_get_locked

Annotated Snippet

#ifndef _AMDXDNA_PM_H_
#define _AMDXDNA_PM_H_

#include "amdxdna_pci_drv.h"

int amdxdna_pm_suspend(struct device *dev);
int amdxdna_pm_resume(struct device  *dev);
int amdxdna_pm_resume_get(struct amdxdna_dev *xdna);
void amdxdna_pm_suspend_put(struct amdxdna_dev *xdna);
void amdxdna_pm_init(struct amdxdna_dev *xdna);
void amdxdna_pm_fini(struct amdxdna_dev *xdna);

static inline int amdxdna_pm_resume_get_locked(struct amdxdna_dev *xdna)
{
	int ret;

	mutex_unlock(&xdna->dev_lock);
	ret = amdxdna_pm_resume_get(xdna);
	mutex_lock(&xdna->dev_lock);

	return ret;
}

#endif /* _AMDXDNA_PM_H_ */

Annotation

• Immediate include surface: `amdxdna_pci_drv.h`.
• Detected declarations: `function amdxdna_pm_resume_get_locked`.
• Atlas domain: Driver Families / drivers/accel.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.