Skip to content

soc : ti: Soc layer power domain and clock nodes init#91914

Closed
Kronosblaster wants to merge 1 commit intozephyrproject-rtos:mainfrom
Kronosblaster:sysInit
Closed

soc : ti: Soc layer power domain and clock nodes init#91914
Kronosblaster wants to merge 1 commit intozephyrproject-rtos:mainfrom
Kronosblaster:sysInit

Conversation

@Kronosblaster
Copy link
Copy Markdown
Contributor

@Kronosblaster Kronosblaster commented Jun 19, 2025

Power domains are added to the device tree.
The enabled nodes with power domains assigned to them have them turn on in the SOC layer.
Init for enabled clock nodes.
This PR waits on #90216 to be merged.

@github-actions github-actions Bot added the platform: TI K3 Texas Instruments Keystone 3 Processors label Jun 19, 2025
@bjarki-andreasen
Copy link
Copy Markdown
Contributor

Using PM_DEVICE_RUNTIME, power domains are automatically resumed (pm_device_runtime_get()) when a device on the power domain is resumed, so if you pm_device_runtime_get(DEVICE_DT_GET(DT_NODELABEL(i2c0))); its power domain i2c0_pd will be resumed automatically, the SYS_INIT should not be neccesary, unless its an intermediary solution until drivers for devices like i2c0 implement PM_DEVICE maybe?

@Kronosblaster
Copy link
Copy Markdown
Contributor Author

Using PM_DEVICE_RUNTIME, power domains are automatically resumed (pm_device_runtime_get()) when a device on the power domain is resumed, so if you pm_device_runtime_get(DEVICE_DT_GET(DT_NODELABEL(i2c0))); its power domain i2c0_pd will be resumed automatically, the SYS_INIT should not be neccesary, unless its an intermediary solution until drivers for devices like i2c0 implement PM_DEVICE maybe?

Yeah. There are some drivers that are shared between vendors. This is intended such that those don't have to be modified. All the devices with status = "okay" have their power domains turned on in the SOC layer with this method.

@Kronosblaster Kronosblaster force-pushed the sysInit branch 5 times, most recently from 7207f98 to 7ba0f78 Compare June 20, 2025 06:28
Comment thread soc/ti/k3/am6x/r5/soc.c Outdated
Comment thread soc/ti/k3/am6x/r5/soc.c Outdated
Comment thread soc/ti/k3/am6x/r5/soc.c Outdated
Comment thread soc/ti/k3/am6x/r5/soc.c Outdated
@Kronosblaster Kronosblaster force-pushed the sysInit branch 11 times, most recently from aa773e5 to fb714fe Compare June 24, 2025 04:55
@sonarqubecloud
Copy link
Copy Markdown

Comment thread soc/ti/k3/am6x/r5/soc.c Outdated
@sonarqubecloud
Copy link
Copy Markdown

@Kronosblaster Kronosblaster changed the title soc : ti: Power domain support and soc layer power domain init soc : ti: Soc layer power domain and clock nodes init Aug 19, 2025
@github-actions
Copy link
Copy Markdown

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@Kronosblaster
Copy link
Copy Markdown
Contributor Author

Pls remove the stale label

Turns on all the power domains for devices with a power-domain device
tree property in the soc layer.
Sets clock frequency for enabled devices.
Supported for the R5f0_0 core on the
AM243x EVM.
Makes dmsc node in the power domain driver static.

Signed-off-by: Dave Joseph <d-joseph@ti.com>
@Kronosblaster Kronosblaster force-pushed the sysInit branch 2 times, most recently from 90fa50a to b9215fb Compare November 25, 2025 05:07
@sonarqubecloud
Copy link
Copy Markdown

@github-actions
Copy link
Copy Markdown

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions Bot added the Stale label Jan 25, 2026
@github-actions github-actions Bot closed this Feb 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants