eMMC CMDQ Supported vs Enabled: Validating Host and Device Readiness
- eMMC 5.1 CMDQ support in device EXT_CSD registers does not mean command queuing is active at runtime.
- Using CMDQ requires device, host, driver and runtime support.
- Throughput and latency impacts depend strictly on host architecture and realistic I/O workload profiles.
A data sheet that says an eMMC supports Command Queuing (CMDQ) does not prove the target Linux host is using it. Capability, host implementation and runtime state are separate questions. The Linux MMC attributes documentation defines cmdq_en as “Command Queue enabled”; verify whether that attribute is available and what it reports on the target BSP.
Follow the whole chain
| Boundary | Evidence | Decision |
|---|---|---|
| Device | Exact part data sheet and reported feature data | Does this part support CMDQ? |
| SoC host | Controller manual and board support | Can the host issue queued commands? |
| Kernel/BSP | Driver version, configuration and boot logs | Is the feature initialized or deliberately disabled? |
| Runtime | cmdq_en or vendor-supported diagnostic, plus logs | Is queuing enabled in this running system? |
| Workload | Request concurrency, latency and throughput | Does this application gain anything? |
A positive card capability is insufficient if the host or driver cannot use it. Conversely, a runtime “enabled” indication does not promise a throughput gain. Micron's Linux command-queuing analysis studies particular hardware and software configurations; do not copy its performance figures to another board.
Test the reader's actual workload
Compare the exact board, eMMC revision and image under a representative application load. Record queue behavior where the host exposes it, along with completion latency, throughput and errors. If your use is serial or dominated by another layer, CMDQ may not move the application deadline. Do not force-enable an undocumented host feature as a benchmark trick. Send the host/controller, BSP and required workload with a quote request for a candidate device.
References
We publish measured usable capacity and define trial-batch verification against the quoted product and agreed test scope.