-
Notifications
You must be signed in to change notification settings - Fork 65
Additional LPM documentation updates #259
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
Conversation
@akashdeep-ti I do not really understand your comment here: #245 (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.
I feel like the note is a little redundant considering the sysfs entry is suffixed with _us
but this is fine.
Also, thanks for using the proper tags for these commits. In the future you can shorten this by just saying something like:
Which now that I'm typing this out, there's a typo in that subject. |
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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
@akashdeep-ti to re-review |
Documentation updates to address comments from Akash's comments from this PR #245
Updates include: