-
Notifications
You must be signed in to change notification settings - Fork 8.3k
stm32: u5: allow selection of VOS via DT #100319
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
base: main
Are you sure you want to change the base?
stm32: u5: allow selection of VOS via DT #100319
Conversation
|
@petrosyan-van could you please give some feedback on this? 🙂 |
8e74004 to
f916d18
Compare
Thanks for this PR! I will try it out in upcoming days and will let you know :) |
| +---------+----------------+-----------------------------------+ | ||
| | 3 | 55 MHz | [1] | | ||
| +---------+----------------+-----------------------------------+ | ||
| | 4 | 25 MHz | [1][2]; lowest power consumption | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in udc_stm32.c we have:
/* Check that power range is 1 or 2 */
if (LL_PWR_GetRegulVoltageScaling() < LL_PWR_REGU_VOLTAGE_SCALE2) {
LOG_ERR("Wrong Power range to use USB OTG HS");
return -EIO;
}
there is no check if it's OTG_HS or OTG_FS. Seems the requirement is to have at least scale 2 in the code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
f916d18 to
70587c3
Compare
|
Added missing |
| +---------+----------------+-----------------------------------+ | ||
| | 3 | 55 MHz | [1] | | ||
| +---------+----------------+-----------------------------------+ | ||
| | 4 | 25 MHz | [1][2]; lowest power consumption | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit:
| | 4 | 25 MHz | [1][2]; lowest power consumption | | |
| | 4 | 25 MHz | Lowest power consumption [1][2] | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done + saved a few characters at the right of table.
erwango
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Otherwise LTGM
| Controls two voltage regulators which can output one voltage | ||
| among four different ranges depending on use case. | ||
| among four different voltage scales, depending on use case. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be fixed in previous commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
|
I tried with |
Add a binding for the power controller of STM32U5 series. Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
Add the "st,stm32u5-pwr" compatible to the Power Controller node in the DTSI for STM32U5 series. Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
Add support for the new `voltage-scale` property on the STM32U5-specific Power Controller binding. Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
Add new voltage scale selection property for STM32U5 to 4.4 release notes. Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
70587c3 to
0757899
Compare
We have no plan at the moment for supporting dynamic voltage scaling on STM32 platforms. If you want such functionality, you will have to roll your own implementation (note that the LL API can be used by the application through the |
|




Allow selecting a voltage scale using Device Tree on STM32U5 series. This is notably useful when a high system clock frequency is not required, but the application still wants to use the USB IPs which are only available in certain ranges.
Fixes #98641.