Lines Matching refs:RESET
318 * reply are of the same length. Some FW commands like RESET and
3398 * and the Firmware/Chip haven't yet gone through a RESET sequence. So
3434 * Firmware/Chip haven't yet gone through a RESET sequence. So it's best
7556 INIT_CMD(c, RESET, WRITE);
7562 * t4_fw_halt - issue a reset/halt to FW and put uP into RESET
7564 * @mbox: mailbox to use for the FW RESET command (if desired)
7565 * @force: force uP into RESET even if FW RESET command fails
7567 * Issues a RESET command to firmware (if desired) with a HALT indication
7568 * and then puts the microprocessor into RESET state. The RESET command
7582 * If a legitimate mailbox is provided, issue a RESET command
7589 INIT_CMD(c, RESET, WRITE);
7596 * Normally we won't complete the operation if the firmware RESET
7598 * uP into RESET. This can be useful if the firmware is hung or even
7600 * RESET without the cooperation of firmware in that case.
7603 * the firmware RESET command above or we're dealing with old firmware
7606 * rather than a RESET ... if it's new enough to understand that ...
7615 * And we always return the result of the firmware RESET command
7616 * even when we force the uP into RESET ...
7622 * t4_fw_restart - restart the firmware by taking the uP out of RESET
7647 * @mbox: mailbox to use for the FW RESET command (if desired)
7656 * (though we'll still put the adapter microprocessor into RESET in
7660 * the adapter will have been fully RESET losing all previous setup