STRUCT OCS_ECC_DEV(9)

🌸 NAME 🌸

okay bestie, this is struct ocs_ecc_dev(9) from the Kernel API Manual — the page for struct ocs_ecc_dev, aka ECC device context. It’s a struct, it’s iconic, and we’re about to meet every member like it’s a group-chat roll call. 💅

✨ SYNOPSIS ✨

struct ocs_ecc_dev {
    struct list_head list;
    struct device *dev;
    void __iomem *base_reg;
    struct crypto_engine *engine;
    struct completion irq_done;
    int irq;
};

🎀 Members 🎀

• list — List of device contexts. The device-context roster, no cap. 🫶
• dev — OCS ECC device. Literally the OCS ECC device itself.
• base_reg — IO base address of OCS ECC. The IO base address, right where it should be.
• engine — Crypto engine for the device. The crypto engine serving the device.
• irq_done — IRQ done completion. The IRQ done completion — period included, bestie.
• irq — IRQ number. The IRQ number, simple as that.

🔥 SEE ALSO 🔥

• Kernel file ./drivers/crypto/intel/keembay/keembay-ocs-ecc.c
• struct ocs_ecc_ctx(9)
• ocs_ecc_read_cx_out(9)
• ocs_ecc_read_cy_out(9)
• kmb_ecc_do_scalar_op(9)

okay bye bestie! This page’s source/version is ./drivers/crypto/intel/keembay, its date is October 2026, and its footer title is struct ocs_ecc_dev(9) — go forth and slay those ECC device context vibes 💖✨