During stress runs, the driver logs timestamps to /sys/kernel/debug/sec_testbd/stress_log for offline analysis. | Test | Throughput (DMA) | Latency (Crypto) | Power (mW) | |------|------------------|------------------|------------| | 1 GiB secure copy | 1.84 GB/s | – | 120 | | AES‑256‑ECB (256 MiB) | – | 3.2 µs/KB | 95 | | SHA‑256 (1 GiB) | – | 1.1 µs/KB | 88 | | Stress mode 0 (10 k iter) | 0.9 GB/s (average) | – | 130 |

/* 2. Request IRQ */ ret = devm_request_irq(&pdev->dev, platform_get_irq(pdev, 0), sec_testbd_isr, 0, dev_name(&pdev->dev), testbd); if (ret) return ret;

struct sec_testbd_crypto_req __u32 algo; /* SEC_ALGO_AES256, SEC_ALGO_SHA256, etc. */ __u32 mode; /* ENCRYPT, DECRYPT, HASH */ __u64 key_addr; /* Physical address of key material */ __u64 src_addr; /* Input data buffer */ __u64 dst_addr; /* Output buffer (or NULL for hash) */ __u32 length; /* Data length */ ; The driver programs the CE registers, starts the operation, and returns the status. The CE can process up to 64 KB per command; larger payloads are automatically split. The driver provides a special ioctl SEC_TESTBD_IOCTL_STRESS that configures the internal test logic:

| Parameter | Meaning | |-----------|---------| | mode | 0 = buffer‑overflow test, 1 = timing jitter, 2 = fault‑injection | | iterations | Number of stress cycles (max 10 000) | | seed | Pseudo‑random seed for pattern generation |

struct resource *res; int ret;