Lines Matching defs:firmware

13 #include <linux/firmware.h>
180 /* Broadcom BCM2033 without firmware */
186 /* Atheros 3011 with sflash firmware */
195 /* Atheros AR9285 Malbec with sflash firmware */
198 /* Atheros 3012 with sflash firmware */
250 /* Atheros AR5BBU12 with sflash firmware */
253 /* Atheros AR5BBU12 with sflash firmware */
1350 /* Patching USB firmware files prior to starting any URBs of HCI path
1870 * HCI rev values always match. As they both store the firmware number.
1876 /* Known legit CSR firmware build numbers and their supported BT versions:
1936 static const struct firmware *btusb_setup_intel_get_fw(struct hci_dev *hdev,
1939 const struct firmware *fw;
1952 bt_dev_err(hdev, "Intel firmware file request failed (%d)",
1957 bt_dev_err(hdev, "failed to open Intel firmware file: %s (%d)",
1960 /* If the correct firmware patch file is not found, use the
1961 * default firmware patch file instead
1972 bt_dev_info(hdev, "Intel Bluetooth firmware file: %s", fwname);
1978 const struct firmware *fw,
1990 * in the current firmware buffer doesn't start with 0x01 or
1992 * the firmware file is corrupted and it should stop the patching
2006 /* Ensure that the remain firmware data is long enough than the length
2007 * of command parameter. If not, the firmware file is corrupted.
2014 /* If there is a command that loads a patch in the firmware
2017 * is not required when the default firmware patch file is used
2052 /* Every HCI commands in the firmware file has its correspond event.
2053 * If event is not found or remain is smaller than zero, the firmware
2070 * the firmware file. At fist, it checks the length and then
2094 const struct firmware *fw;
2118 * which firmware file to load.
2121 * firmware variant, revision and build number.
2142 /* Opens the firmware patch file based on the firmware version read
2143 * from the controller. If it fails to open the matching firmware
2144 * patch file, it tries to open the default firmware patch file.
2155 * firmware patch data and configuration parameters.
2165 /* The firmware data file consists of list of Intel specific HCI
2169 * It reads the command and its expected event from the firmware file,
2171 * the returned event is compared with the event read from the firmware
2175 * Once the firmware patching is completed successfully,
2179 * If the firmware patching fails, the manufacturer mode is
2200 * with reset and activate the downloaded firmware patches.
2223 bt_dev_info(hdev, "Intel firmware patch completed");
2231 * deactivate the downloaded firmware patches.
2237 bt_dev_info(hdev, "Intel firmware patch completed and deactivated");
2329 /* When switching to the operational firmware
2336 /* When the firmware loading completes the
2338 * indicating the result of the firmware
2373 * the operational firmware, it will actually not
2445 const struct firmware *fw;
2462 /* Check for supported iBT hardware variants of this firmware
2484 /* The firmware variant determines if the device is in bootloader
2485 * mode or is running operational firmware. The value 0x06 identifies
2487 * firmware.
2489 * When the operational firmware is already present, then only
2507 bt_dev_err(hdev, "Unsupported Intel firmware variant (%u)",
2519 /* It is required that every single firmware fragment is acknowledged
2524 bt_dev_err(hdev, "Unsupported Intel firmware loading method (%u)",
2530 * also be no valid address for the operational firmware.
2538 * revision information are used to select the right firmware for SfP
2541 * The firmware filename is ibt-<hw_variant>-<dev_revid>.sfi.
2554 * The firmware file name for these will be
2561 bt_dev_err(hdev, "Unsupported Intel firmware naming");
2567 bt_dev_err(hdev, "Failed to load Intel firmware file (%d)", err);
2571 bt_dev_info(hdev, "Found device firmware: %s", fwname);
2574 bt_dev_err(hdev, "Invalid size of firmware file (%zu)",
2582 /* Start firmware downloading and get boot parameter */
2593 bt_dev_info(hdev, "Waiting for firmware download to complete");
2596 * booting the loaded firmware, wait for the bootloader notification
2602 * The firmware loading should not take longer than 5 seconds
2648 * command while downloading the firmware.
2655 * is in bootloader mode or if it already has operational firmware
2669 /* controller is already having an operational firmware */
2691 * is done by the operational firmware sending bootup notification.
2693 * Booting into operational firmware should not take longer than
2726 bt_dev_err(hdev, "Unsupported Intel firmware naming");
3154 const struct firmware *fw;
3162 bt_dev_err(hdev, "Failed to load firmware file (%d)", err);
3166 /* Power on data RAM the firmware relies on. */
3226 /* Activate funciton the firmware providing to */
3233 /* Wait a few moments for firmware activation done */
3328 /* Query whether the firmware is already download */
3337 bt_dev_err(hdev, "Failed to query firmware status (%d)", err);
3342 bt_dev_info(hdev, "firmware already downloaded");
3346 /* Setup a firmware which the device definitely requires */
3617 const struct firmware *firmware,
3630 count = firmware->size;
3633 memcpy(buf, firmware->data, size);
3659 memcpy(buf, firmware->data + sent, size);
3666 sent, firmware->size, err);
3690 const struct firmware *fw;
3722 "firmware rome 0x%x build 0x%x",
3726 bt_dev_err(hdev, "rampatch file version did not match with firmware");
3743 const struct firmware *fw;
3807 bt_dev_err(hdev, "don't support firmware rome 0x%x", ver_rom);
4033 /* Old firmware would otherwise let ath3k driver load
4258 /* Realtek devices lose their updated firmware over global
4292 /* Old firmware would otherwise execute USB reset */
4308 /* New sniffer firmware has crippled HCI interface */
4434 * in them. But for autosuspend, firmware should remain.