stm32_firew...t_all_access(9)

💖 NAME 💖

okay so bestie, stm32_firewall_get_grant_all_access — it's giving "do everything at once" energy ✨ Allocate and get all the firewall(s) associated to the given device, then try to grant access rights for each element. Basically it's a helper function that wraps both stm32_firewall_get_firewall() and stm32_firewall_grant_access() on all firewall references of a device, plus it allocates the array for you 🎀 No cap, it's the shortcut. Realease access using stm32_firewall_release_access* APIs when done — don't leave it hanging, that's not the vibe 💅

✨ SYNOPSIS ✨

int stm32_firewall_get_grant_all_access (struct device *dev , struct
stm32_firewall **firewall , int *nb_firewall );

🌸 ARGUMENTS 🌸

• dev — the device that's performing the checks 🫶
• firewall — pointer to the array of firewall references that's gonna get allocated 🌈
• nb_firewall — number of allocated elements in firewall ⭐

🦋 DESCRIPTION 🦋

Returns 0 on success, or the appropriate errno code if an error occurred. That's it, that's the whole plot 😭 Lowkey iconic for how short it is.

fr fr though — check that return value. 0 is the slay, anything else is the error code telling you what went wrong 🙈

👑 SEE ALSO 👑

Kernel file ./include/linux/bus/stm32_firewall_device.h and struct stm32_firewall(9), plus the whole friend group:

• stm32_firewall_get_firewall(9)
• stm32_firewall_grant_access(9)
• stm32_firewall_release_access(9)
• stm32_firewall_grant_access_by_id(9)
• stm32_firewall_release_access_by_id(9)

💜 and that's the whole page, bestie! this one lives in ./include/linux/bus, dated October 2026, from the Kernel API Manual — go off, go read the other firewall pages, they ate 💅🔥🎀