Based on kernel version
5.9. Page generated on
2020-10-14 09:35 EST.
|1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27|
============ Introduction ============ The firmware API enables kernel code to request files required for functionality from userspace, the uses vary: * Microcode for CPU errata * Device driver firmware, required to be loaded onto device microcontrollers * Device driver information data (calibration data, EEPROM overrides), some of which can be completely optional. Types of firmware requests ========================== There are two types of calls: * Synchronous * Asynchronous Which one you use vary depending on your requirements, the rule of thumb however is you should strive to use the asynchronous APIs unless you also are already using asynchronous initialization mechanisms which will not stall or delay boot. Even if loading firmware does not take a lot of time processing firmware might, and this can still delay boot or initialization, as such mechanisms such as asynchronous probe can help supplement drivers.