drivers/crypto/ccp/sfs.h
Source file repositories/reference/linux-study-clean/drivers/crypto/ccp/sfs.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/crypto/ccp/sfs.h- Extension
.h- Size
- 963 bytes
- Lines
- 48
- Domain
- Driver Families
- Bucket
- drivers/crypto
- 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
uapi/linux/psp-sfs.hlinux/device.hlinux/miscdevice.hlinux/psp-sev.hlinux/psp-platform-access.hlinux/set_memory.hpsp-dev.h
Detected Declarations
struct sfs_misc_devstruct sfs_commandstruct sfs_device
Annotated Snippet
struct sfs_misc_dev {
struct kref refcount;
struct miscdevice misc;
};
struct sfs_command {
struct psp_ext_req_buffer_hdr hdr;
u8 buf[PAGE_SIZE - sizeof(struct psp_ext_req_buffer_hdr)];
u8 sfs_buffer[];
} __packed;
struct sfs_device {
struct device *dev;
struct psp_device *psp;
struct page *page;
struct sfs_command *command_buf;
struct sfs_misc_dev *misc;
};
void sfs_dev_destroy(struct psp_device *psp);
int sfs_dev_init(struct psp_device *psp);
#endif /* __SFS_H__ */
Annotation
- Immediate include surface: `uapi/linux/psp-sfs.h`, `linux/device.h`, `linux/miscdevice.h`, `linux/psp-sev.h`, `linux/psp-platform-access.h`, `linux/set_memory.h`, `psp-dev.h`.
- Detected declarations: `struct sfs_misc_dev`, `struct sfs_command`, `struct sfs_device`.
- Atlas domain: Driver Families / drivers/crypto.
- 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.