Struct DMA_CRYPTO 

#[non_exhaustive]
pub struct DMA_CRYPTO<'a> { /* private fields */ }

Available on crate feature unstable only.

DMA_CRYPTO peripheral singleton

Stability

This API is marked as unstable and is only available when the unstable crate feature is enabled. This comes with no stability guarantees, and could be changed or removed at any time.

Implementations

impl DMA_CRYPTO<'_>

pub unsafe fn steal() -> Self

Unsafely create an instance of this peripheral out of thin air.

Safety

You must ensure that you’re only using one instance of this type at a time.

pub unsafe fn clone_unchecked(&self) -> Self

Unsafely clone this peripheral reference.

Safety

You must ensure that you’re only using one instance of this type at a time.

pub fn reborrow(&mut self) -> DMA_CRYPTO<'_>

Creates a new peripheral reference with a shorter lifetime.

Use this method if you would like to keep working with the peripheral after you dropped the driver that consumes this.

pub fn bind_dma_interrupt(&self, handler: InterruptHandler)

Binds an interrupt handler to the corresponding interrupt for this peripheral, and enables the interrupt.

This function is a very low-level way to work with interrupts. Unless you're writing drivers, this is probably not the interrupt API you want to use.

Stability

This API is marked as unstable and is only available when the unstable crate feature is enabled. This comes with no stability guarantees, and could be changed or removed at any time.

pub fn enable_dma_interrupt(&self, priority: Priority)

Enables the CRYPTO_DMA peripheral interrupt on the given priority level.

This function is a very low-level way to work with interrupts. Unless you're writing drivers, this is probably not the interrupt API you want to use.

Note that a suitable interrupt handler needs to be set up before the first interrupt is triggered, otherwise the default handler will panic. To set up an interrupt handler, use Self::bind_dma_interrupt or create a function that has the same (non-mangled) name as the interrupt you want to handle.

Examples

use esp_hal::interrupt::Priority;

#[unsafe(no_mangle)]
unsafe extern "C" fn CRYPTO_DMA() {
    // do something
}

peripherals.DMA_CRYPTO.enable_dma_interrupt(Priority::Priority1);
peripherals.DMA_CRYPTO.disable_dma_interrupt_on_all_cores();

pub fn disable_dma_interrupt(&self)

Disables the CRYPTO_DMA peripheral interrupt handler on the current CPU core.

This function is a very low-level way to work with interrupts. Unless you're writing drivers, this is probably not the interrupt API you want to use.

# Stability

This API is marked as unstable and is only available when the unstable crate feature is enabled. This comes with no stability guarantees, and could be changed or removed at any time.

pub fn disable_dma_interrupt_on_all_cores(&self)

Disables the CRYPTO_DMA peripheral interrupt handler on all cores.

This function is a very low-level way to work with interrupts. Unless you're writing drivers, this is probably not the interrupt API you want to use.

impl DMA_CRYPTO<'_>

pub const PTR: *const <CRYPTO_DMA as Deref>::Target = pac::CRYPTO_DMA::PTR

Pointer to the register block

Stability

This API is marked as unstable and is only available when the unstable crate feature is enabled. This comes with no stability guarantees, and could be changed or removed at any time.

pub const fn ptr() -> *const <CRYPTO_DMA as Deref>::Target

Return the pointer to the register block

Stability

This API is marked as unstable and is only available when the unstable crate feature is enabled. This comes with no stability guarantees, and could be changed or removed at any time.

pub fn regs<'a>() -> &'a <CRYPTO_DMA as Deref>::Target

Return a reference to the register block

Stability

This API is marked as unstable and is only available when the unstable crate feature is enabled. This comes with no stability guarantees, and could be changed or removed at any time.

pub fn register_block(&self) -> &<CRYPTO_DMA as Deref>::Target

Return a reference to the register block

Stability

This API is marked as unstable and is only available when the unstable crate feature is enabled. This comes with no stability guarantees, and could be changed or removed at any time.

Trait Implementations

impl<'a> Debug for DMA_CRYPTO<'a>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'d> DmaChannel for DMA_CRYPTO<'d>

type Rx = CryptoDmaRxChannel<'d>

A description of the RX half of a DMA Channel.

type Tx = CryptoDmaTxChannel<'d>

A description of the TX half of a DMA Channel.

unsafe fn split_internal(self, _: Internal) -> (Self::Rx, Self::Tx)

Splits the DMA channel into its RX and TX halves.

impl<'d> DmaEligiblePeripheral<DMA_CRYPTO<'d>> for AES<'d>

fn dma_peripheral(&self) -> DmaPeripheral

Returns the DmaPeripheral ID for runtime compatibility checks.

impl<'d> DmaEligiblePeripheral<DMA_CRYPTO<'d>> for SHA<'d>

fn dma_peripheral(&self) -> DmaPeripheral

Returns the DmaPeripheral ID for runtime compatibility checks.

impl<'d> From<DMA_CRYPTO<'d>> for CryptoDmaRxChannel<'d>

fn from(this: DMA_CRYPTO<'d>) -> CryptoDmaRxChannel<'d>

Converts to this type from the input type.

impl<'d> From<DMA_CRYPTO<'d>> for CryptoDmaTxChannel<'d>

fn from(this: DMA_CRYPTO<'d>) -> CryptoDmaTxChannel<'d>

Converts to this type from the input type.

impl<'d> Mem2MemCapableChannel<'d> for DMA_CRYPTO<'d>

fn mem2mem_id(&self) -> DmaPeripheral

Peripheral selector programmed for memory-to-memory on this channel.

impl<'d> AesDmaChannel<'d> for DMA_CRYPTO<'d>