Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stm32h7: merge GPIO MPU regions. #1577

Merged
merged 1 commit into from
Dec 12, 2023
Merged

stm32h7: merge GPIO MPU regions. #1577

merged 1 commit into from
Dec 12, 2023

Conversation

cbiffle
Copy link
Collaborator

@cbiffle cbiffle commented Dec 11, 2023

We were being careful and tiling three MPU regions to the exact boundaries of the implemented GPIO blocks on STM32H7. However, this also meant we were out of MPU slots. I need to map a region into sys for the external interrupt work.

Here I've merged the regions into a single, slightly larger region. This technically exposes some undefined address space to the sys task. However, it sure looks like the remaining space is reserved by ST for the addition of more GPIO blocks, since they've been stuffing more ports in here in past models. Since we won't be touching that address space -- and we can be fairly certain of that thanks to mostly-safe code -- I'd argue that this doesn't increase our risk.

@cbiffle cbiffle requested a review from mkeeter December 11, 2023 20:58
Copy link
Collaborator

@labbott labbott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@cbiffle cbiffle enabled auto-merge (rebase) December 12, 2023 18:31
We were being careful and tiling three MPU regions to the exact
boundaries of the implemented GPIO blocks on STM32H7. However, this also
meant we were out of MPU slots. I need to map a region into sys for the
external interrupt work.

Here I've merged the regions into a single, slightly larger region. This
technically exposes some undefined address space to the sys task.
However, it _sure looks_ like the remaining space is reserved by ST for
the addition of more GPIO blocks, since they've been stuffing more ports
in here in past models. Since we won't be touching that address space --
and we can be fairly certain of that thanks to mostly-safe code -- I'd
argue that this doesn't increase our risk.
@cbiffle cbiffle merged commit 8e3caaa into master Dec 12, 2023
71 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants