drivers/base/firmware_loader/fallback.h
Source file repositories/reference/linux-study-clean/drivers/base/firmware_loader/fallback.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/base/firmware_loader/fallback.h- Extension
.h- Size
- 1221 bytes
- Lines
- 46
- Domain
- Driver Families
- Bucket
- drivers/base
- 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/firmware.hlinux/device.hfirmware.hsysfs.h
Detected Declarations
function firmware_fallback_sysfsfunction kill_pending_fw_fallback_reqsfunction firmware_fallback_platform
Annotated Snippet
static inline void kill_pending_fw_fallback_reqs(bool kill_all) { }
static inline void fw_fallback_set_cache_timeout(void) { }
static inline void fw_fallback_set_default_timeout(void) { }
#endif /* CONFIG_FW_LOADER_USER_HELPER */
#ifdef CONFIG_EFI_EMBEDDED_FIRMWARE
int firmware_fallback_platform(struct fw_priv *fw_priv);
#else
static inline int firmware_fallback_platform(struct fw_priv *fw_priv)
{
return -ENOENT;
}
#endif
#endif /* __FIRMWARE_FALLBACK_H */
Annotation
- Immediate include surface: `linux/firmware.h`, `linux/device.h`, `firmware.h`, `sysfs.h`.
- Detected declarations: `function firmware_fallback_sysfs`, `function kill_pending_fw_fallback_reqs`, `function firmware_fallback_platform`.
- Atlas domain: Driver Families / drivers/base.
- 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.