Skip to content

Additional LPM documentation updates#259

Merged
praneethbajjuri merged 3 commits intoTexasInstruments:masterfrom
kwillis01:cleanup
Apr 9, 2025
Merged

Additional LPM documentation updates#259
praneethbajjuri merged 3 commits intoTexasInstruments:masterfrom
kwillis01:cleanup

Conversation

@kwillis01
Copy link
Contributor

@kwillis01 kwillis01 commented Apr 7, 2025

Documentation updates to address comments from Akash's comments from this PR #245

Updates include:

  • Updating the confirmation of wakeup events to include the pin that caused the wakeup and the last entered low power mode.
  • Increasing readability for setting CPU resume constraints where the resume latency is referenced in ms and not us

@kwillis01
Copy link
Contributor Author

@akashdeep-ti I do not really understand your comment here: #245 (comment)
To my understanding it is still valid to keep this as an example because it is in the code for when a timeout happens with setting the completion of suspend on rproc.

StaticRocket
StaticRocket previously approved these changes Apr 7, 2025
Copy link
Member

@StaticRocket StaticRocket left a comment

Choose a reason for hiding this comment

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

I feel like the note is a little redundant considering the sysfs entry is suffixed with _us but this is fine.

@StaticRocket
Copy link
Member

Also, thanks for using the proper tags for these commits. In the future you can shorten this by just saying something like:

fix(power-management): Increase readibility for resume latency

Which now that I'm typing this out, there's a typo in that subject.

@akashdeep-ti
Copy link
Contributor

@akashdeep-ti I do not really understand your comment here: #245 (comment) To my understanding it is still valid to keep this as an example because it is in the code for when a timeout happens with setting the completion of suspend on rproc.

This is not valid as at this stage, the prepare sleep has been sent to DM and even if we set constraints, DM will not honour that

@kwillis01
Copy link
Contributor Author

@akashdeep-ti I do not really understand your comment here: #245 (comment) To my understanding it is still valid to keep this as an example because it is in the code for when a timeout happens with setting the completion of suspend on rproc.

This is not valid as at this stage, the prepare sleep has been sent to DM and even if we set constraints, DM will not honour that

ahh i see, i will take this out then

Change units from us to ms when referencing CPU resume latency in order
to increase readability from user. Referring to  resume latency in ms is
inline with the TI SCI documentation for setting resume latency.

Signed-off-by: Kendall Willis <k-willis@ti.com>
When the SoC resumes in SDK 11.00 the pin that caused the wakeup event
and the low power mode last entered are printed upon resume of the
system. Explain how to find what wakeup event is associated with the pin
printed and what low power mode was entered. Add an example of finding
this.

Signed-off-by: Kendall Willis <k-willis@ti.com>
Remove the example of how to set a device constraint that leaves the
device powered on. This example references the remoteproc driver. In
this driver, the constraint is being set during suspend_late. At that
point in the suspend sequence, no new constraints are being sent to the
DM so this code does not show a device constraint being set correctly.

Signed-off-by: Kendall Willis <k-willis@ti.com>
@cshilwant
Copy link
Member

@akashdeep-ti to re-review

@praneethbajjuri praneethbajjuri merged commit a5bec67 into TexasInstruments:master Apr 9, 2025
3 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.

10 participants