include/uapi/linux/misc/bcm_vk.h
Source file repositories/reference/linux-study-clean/include/uapi/linux/misc/bcm_vk.h
File Facts
- System
- Linux kernel
- Corpus path
include/uapi/linux/misc/bcm_vk.h- Extension
.h- Size
- 3007 bytes
- Lines
- 85
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/ioctl.hlinux/types.h
Detected Declarations
struct vk_imagestruct vk_reset
Annotated Snippet
struct vk_image {
__u32 type; /* Type of image */
#define VK_IMAGE_TYPE_BOOT1 1 /* 1st stage (load to SRAM) */
#define VK_IMAGE_TYPE_BOOT2 2 /* 2nd stage (load to DDR) */
__u8 filename[BCM_VK_MAX_FILENAME]; /* Filename of image */
};
struct vk_reset {
__u32 arg1;
__u32 arg2;
};
#define VK_MAGIC 0x5e
/* Load image to Valkyrie */
#define VK_IOCTL_LOAD_IMAGE _IOW(VK_MAGIC, 0x2, struct vk_image)
/* Send Reset to Valkyrie */
#define VK_IOCTL_RESET _IOW(VK_MAGIC, 0x4, struct vk_reset)
/*
* Firmware Status accessed directly via BAR space
*/
#define VK_BAR_FWSTS 0x41c
#define VK_BAR_COP_FWSTS 0x428
/* VK_FWSTS definitions */
#define VK_FWSTS_RELOCATION_ENTRY (1UL << 0)
#define VK_FWSTS_RELOCATION_EXIT (1UL << 1)
#define VK_FWSTS_INIT_START (1UL << 2)
#define VK_FWSTS_ARCH_INIT_DONE (1UL << 3)
#define VK_FWSTS_PRE_KNL1_INIT_DONE (1UL << 4)
#define VK_FWSTS_PRE_KNL2_INIT_DONE (1UL << 5)
#define VK_FWSTS_POST_KNL_INIT_DONE (1UL << 6)
#define VK_FWSTS_INIT_DONE (1UL << 7)
#define VK_FWSTS_APP_INIT_START (1UL << 8)
#define VK_FWSTS_APP_INIT_DONE (1UL << 9)
#define VK_FWSTS_MASK 0xffffffff
#define VK_FWSTS_READY (VK_FWSTS_INIT_START | \
VK_FWSTS_ARCH_INIT_DONE | \
VK_FWSTS_PRE_KNL1_INIT_DONE | \
VK_FWSTS_PRE_KNL2_INIT_DONE | \
VK_FWSTS_POST_KNL_INIT_DONE | \
VK_FWSTS_INIT_DONE | \
VK_FWSTS_APP_INIT_START | \
VK_FWSTS_APP_INIT_DONE)
/* Deinit */
#define VK_FWSTS_APP_DEINIT_START (1UL << 23)
#define VK_FWSTS_APP_DEINIT_DONE (1UL << 24)
#define VK_FWSTS_DRV_DEINIT_START (1UL << 25)
#define VK_FWSTS_DRV_DEINIT_DONE (1UL << 26)
#define VK_FWSTS_RESET_DONE (1UL << 27)
#define VK_FWSTS_DEINIT_TRIGGERED (VK_FWSTS_APP_DEINIT_START | \
VK_FWSTS_APP_DEINIT_DONE | \
VK_FWSTS_DRV_DEINIT_START | \
VK_FWSTS_DRV_DEINIT_DONE)
/* Last nibble for reboot reason */
#define VK_FWSTS_RESET_REASON_SHIFT 28
#define VK_FWSTS_RESET_REASON_MASK (0xf << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_SYS_PWRUP (0x0 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_MBOX_DB (0x1 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_M7_WDOG (0x2 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_TEMP (0x3 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_PCI_FLR (0x4 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_PCI_HOT (0x5 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_PCI_WARM (0x6 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_PCI_COLD (0x7 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_L1 (0x8 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_L0 (0x9 << VK_FWSTS_RESET_REASON_SHIFT)
#define VK_FWSTS_RESET_UNKNOWN (0xf << VK_FWSTS_RESET_REASON_SHIFT)
#endif /* __UAPI_LINUX_MISC_BCM_VK_H */
Annotation
- Immediate include surface: `linux/ioctl.h`, `linux/types.h`.
- Detected declarations: `struct vk_image`, `struct vk_reset`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.