stm32/(o|q)spi: command naming convention fix

The naming convention is to prefix blocking functions with blocking. As
both command implementations are blocking the async for the ospi
implementation should also be dropped.
This commit is contained in:
Piotr Esden-Tempski 2024-12-17 14:45:52 -08:00
parent 0c245892c6
commit b2e8268470
2 changed files with 2 additions and 2 deletions

View File

@ -520,7 +520,7 @@ impl<'d, T: Instance, M: PeriMode> Ospi<'d, T, M> {
}
/// Function used to control or configure the target device without data transfer
pub async fn command(&mut self, command: &TransferConfig) -> Result<(), OspiError> {
pub fn blocking_command(&mut self, command: &TransferConfig) -> Result<(), OspiError> {
// Wait for peripheral to be free
while T::REGS.sr().read().busy() {}

View File

@ -148,7 +148,7 @@ impl<'d, T: Instance, M: PeriMode> Qspi<'d, T, M> {
}
/// Do a QSPI command.
pub fn command(&mut self, transaction: TransferConfig) {
pub fn blocking_command(&mut self, transaction: TransferConfig) {
#[cfg(not(stm32h7))]
T::REGS.cr().modify(|v| v.set_dmaen(false));
self.setup_transaction(QspiMode::IndirectWrite, &transaction, None);