Why CYW43_xxxxx functions lock the other core?

[kendo55]

Why CYW43_xxxxx functions lock the other core in arch_threadsafe_background.h?

please see in the code below: .....// Lock the other core

They also stop running low_prio_irq, that's o.k.
but please keep my 2nd core running,
where I only have one time critical dedicated function ("task") with r/w GPIOs

in cyw43_ctrl.c
----------------
int cyw43_wifi_join(cyw43_t *self, size_t ssid_len, const uint8_t *ssid, size_t key_len, const uint8_t *key, uint32_t auth_type, const uint8_t *bssid, uint32_t channel) {
    CYW43_THREAD_ENTER;
    if (!CYW43_STA_IS_ACTIVE(self)) {
        CYW43_THREAD_EXIT;

...\pico-sdk\src\rp2_common\pico_cyw43_arch\include\pico\cyw43_arch\arch_threadsafe_background.h
---------------------------------------------------------------
    #define CYW43_THREAD_ENTER cyw43_thread_enter();
    #define CYW43_THREAD_EXIT cyw43_thread_exit();

    // Prevent background processing in pensv and access by the other core
    // These methods are called in pensv context and on either core
    // They can be called recursively
    void cyw43_thread_enter(void) {
        // Lock the other core and stop low_prio_irq running
        recursive_mutex_enter_blocking(&cyw43_mutex);
    }

What can I do against it?

[earlephilhower]

This does not stop the other core, it is just a mutex to make sure the 2 cores do not illegally attempt to access the CYW43 chip in parallel. So the 2nd core will run happily along as long as it doesn't make a cyw43_xxx call.

[kendo55]

thank you!