boards/same54-xpro: don't source peripheral clocks from main clock#13414
Conversation
Use the dedicated 48 MHz clock as a source for the peripheral clocks. This was already done for I2C to allow it to work despite the 120 MHz main clock. Not running the peripherals off the main clock will allow for dynamic re-clocking of the main clock in the future, without affecting the operation of the peripherals. It also gives more flexibility to the main clock selection in general.
|
I'll give this PR a try ASAP on hardware. |
|
|
|
Vera is very annoying... |
|
I thought she had been neutered by #13403 |
|
@benpicco Should we ignore it and go ahead without green button ? |
|
@dylad how can we go ahead without a green merge button? What is that sorcery? |
|
Not sorcery but the button is alive but white instead of green ;) Travis doesn't seem to be that mandatory. |
|
Anarchy! |
|
Hmm now UART doesn't work when waking up from standby ( |
|
Ah looks like this is due to Errata 2.8.3 DFLLVAL.FINE Value When DFLL48M Re-enabled When I follow the work-around procedure the DFLL48 ends up at the right frequency after wake-up again and thus the UART gets the right baud rate. 9c936ae will fix this. |
Contribution description
Use the dedicated 48 MHz clock as a source for the peripheral clocks.
This was already done for I2C to allow it to work despite the 120 MHz main clock.
Not running the peripherals off the main clock will allow for dynamic re-clocking of the main clock in the future, without affecting the operation of the peripherals.
It also gives more flexibility to the main clock selection in general.
Testing procedure
SPI and UART should continue to work as before.
(Tested with ATREB215-XPRO connected to EXT3 on
same54-xpro)Issues/PRs references
none