drivers/hid/amd-sfh-hid/amd_sfh_pcie.h

File Facts

System

Linux kernel

Corpus path

drivers/hid/amd-sfh-hid/amd_sfh_pcie.h

Extension

.h

Size

2055 bytes

Lines

109

Domain

Driver Families

Bucket

drivers/hid

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

• amd_sfh_common.h

Detected Declarations

• struct sfh_cmd_reg
• struct hpd_status
• enum sensor_idx
• enum mem_use_type

Annotated Snippet

struct sfh_cmd_reg {
	union sfh_cmd_base cmd_base;
	union sfh_cmd_param cmd_param;
	phys_addr_t phys_addr;
};

enum sensor_idx {
	accel_idx = 0,
	gyro_idx = 1,
	mag_idx = 2,
	op_idx = 15,
	als_idx = 19
};

enum mem_use_type {
	USE_DRAM,
	USE_C2P_REG,
};

struct hpd_status {
	union {
		struct {
			u32 object_distance       : 16;
			u32 probablity		  : 8;
			u32 human_presence_actual : 4;
			u32 human_presence_report : 4;
		} shpd;
		u32 val;
	};
};

int amd_mp2_get_sensor_num(struct amd_mp2_dev *privdata, u8 *sensor_id);
int amd_sfh_hid_client_init(struct amd_mp2_dev *privdata);
int amd_sfh_hid_client_deinit(struct amd_mp2_dev *privdata);
void amd_sfh_set_desc_ops(struct amd_mp2_ops *mp2_ops);

#endif

Annotation

• Immediate include surface: `amd_sfh_common.h`.
• Detected declarations: `struct sfh_cmd_reg`, `struct hpd_status`, `enum sensor_idx`, `enum mem_use_type`.
• Atlas domain: Driver Families / drivers/hid.
• 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.