drivers/crypto/hisilicon/zip/zip_main.c
Source file repositories/reference/linux-study-clean/drivers/crypto/hisilicon/zip/zip_main.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/crypto/hisilicon/zip/zip_main.c- Extension
.c- Size
- 47536 bytes
- Lines
- 1681
- Domain
- Driver Families
- Bucket
- drivers/crypto
- Inferred role
- Driver Families: operation-table or driver-model contract
- Status
- pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/acpi.hlinux/bitops.hlinux/debugfs.hlinux/init.hlinux/io.hlinux/kernel.hlinux/module.hlinux/pci.hlinux/pm_runtime.hlinux/seq_file.hlinux/topology.hlinux/uacce.hzip.h
Detected Declarations
struct hisi_zip_hw_errorstruct zip_dfx_itemstruct ctrl_debug_filestruct hisi_zip_ctrlenum ctrl_debug_file_indexenum zip_cap_typefunction hzip_diff_regs_showfunction perf_mode_setfunction pf_q_num_setfunction zip_create_qpsfunction hisi_zip_alg_supportfunction hisi_zip_literal_setfunction hisi_zip_set_high_perffunction hisi_zip_wait_sva_readyfunction hisi_zip_close_sva_prefetchfunction hisi_zip_open_sva_prefetchfunction hisi_zip_enable_clock_gatefunction hisi_zip_set_user_domain_and_cachefunction hisi_zip_master_ooo_ctrlfunction hisi_zip_hw_error_enablefunction hisi_zip_hw_error_disablefunction clear_enable_readfunction clear_enable_writefunction hisi_zip_ctrl_debug_readfunction hisi_zip_ctrl_debug_writefunction zip_debugfs_atomic64_setfunction zip_debugfs_atomic64_getfunction hisi_zip_regs_showfunction hisi_zip_core_debug_initfunction zip_cap_regs_showfunction hisi_zip_dfx_debug_initfunction hisi_zip_ctrl_debug_initfunction hisi_zip_debugfs_initfunction hisi_zip_debug_regs_clearfunction hisi_zip_debugfs_exitfunction hisi_zip_show_last_regs_initfunction hisi_zip_show_last_regs_uninitfunction hisi_zip_show_last_dfx_regsfunction hisi_zip_log_hw_errorfunction hisi_zip_get_hw_err_statusfunction hisi_zip_clear_hw_err_statusfunction hisi_zip_disable_error_reportfunction hisi_zip_enable_error_reportfunction hisi_zip_open_axi_master_ooofunction hisi_zip_close_axi_master_ooofunction hisi_zip_get_err_resultfunction hisi_zip_dev_is_abnormalfunction hisi_zip_set_priv_status
Annotated Snippet
static const struct file_operations ctrl_debug_fops = {
.owner = THIS_MODULE,
.open = simple_open,
.read = hisi_zip_ctrl_debug_read,
.write = hisi_zip_ctrl_debug_write,
};
static int zip_debugfs_atomic64_set(void *data, u64 val)
{
if (val)
return -EINVAL;
atomic64_set((atomic64_t *)data, 0);
return 0;
}
static int zip_debugfs_atomic64_get(void *data, u64 *val)
{
*val = atomic64_read((atomic64_t *)data);
return 0;
}
DEFINE_DEBUGFS_ATTRIBUTE(zip_atomic64_ops, zip_debugfs_atomic64_get,
zip_debugfs_atomic64_set, "%llu\n");
static int hisi_zip_regs_show(struct seq_file *s, void *unused)
{
hisi_qm_regs_dump(s, s->private);
return 0;
}
DEFINE_SHOW_ATTRIBUTE(hisi_zip_regs);
static void __iomem *get_zip_core_addr(struct hisi_qm *qm, int core_num)
{
u8 zip_comp_core_num;
u32 zip_core_info;
zip_core_info = qm->cap_tables.dev_cap_table[ZIP_CORE_INFO].cap_val;
zip_comp_core_num = (zip_core_info >> zip_basic_cap_info[ZIP_CLUSTER_COMP_NUM_CAP].shift) &
zip_basic_cap_info[ZIP_CLUSTER_COMP_NUM_CAP].mask;
if (core_num < zip_comp_core_num)
return qm->io_base + HZIP_CORE_DFX_BASE +
(core_num + 1) * HZIP_CORE_ADDR_INTRVL;
return qm->io_base + HZIP_CORE_DFX_DECOMP_BASE +
(core_num - zip_comp_core_num) * HZIP_CORE_ADDR_INTRVL;
}
static int hisi_zip_core_debug_init(struct hisi_qm *qm)
{
u32 zip_core_num, zip_comp_core_num;
struct device *dev = &qm->pdev->dev;
struct debugfs_regset32 *regset;
u32 zip_core_info;
struct dentry *tmp_d;
char buf[HZIP_BUF_SIZE];
int i;
zip_core_info = qm->cap_tables.dev_cap_table[ZIP_CORE_INFO].cap_val;
zip_core_num = (zip_core_info >> zip_basic_cap_info[ZIP_CORE_NUM_CAP].shift) &
zip_basic_cap_info[ZIP_CORE_NUM_CAP].mask;
zip_comp_core_num = (zip_core_info >> zip_basic_cap_info[ZIP_CLUSTER_COMP_NUM_CAP].shift) &
zip_basic_cap_info[ZIP_CLUSTER_COMP_NUM_CAP].mask;
for (i = 0; i < zip_core_num; i++) {
if (i < zip_comp_core_num)
scnprintf(buf, sizeof(buf), "comp_core%d", i);
else
scnprintf(buf, sizeof(buf), "decomp_core%d",
i - zip_comp_core_num);
regset = devm_kzalloc(dev, sizeof(*regset), GFP_KERNEL);
if (!regset)
return -ENOENT;
regset->regs = hzip_dfx_regs;
regset->nregs = ARRAY_SIZE(hzip_dfx_regs);
regset->base = get_zip_core_addr(qm, i);
regset->dev = dev;
tmp_d = debugfs_create_dir(buf, qm->debug.debug_root);
debugfs_create_file("regs", 0444, tmp_d, regset,
&hisi_zip_regs_fops);
}
Annotation
- Immediate include surface: `linux/acpi.h`, `linux/bitops.h`, `linux/debugfs.h`, `linux/init.h`, `linux/io.h`, `linux/kernel.h`, `linux/module.h`, `linux/pci.h`.
- Detected declarations: `struct hisi_zip_hw_error`, `struct zip_dfx_item`, `struct ctrl_debug_file`, `struct hisi_zip_ctrl`, `enum ctrl_debug_file_index`, `enum zip_cap_type`, `function hzip_diff_regs_show`, `function perf_mode_set`, `function pf_q_num_set`, `function zip_create_qps`.
- Atlas domain: Driver Families / drivers/crypto.
- Implementation status: pattern 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.