-
Notifications
You must be signed in to change notification settings - Fork 77
Lpm update #610
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: master
Are you sure you want to change the base?
Lpm update #610
Conversation
483ff84 to
edce1d4
Compare
| ***************** | ||
| 1. Only A core as suspend master supported and tested with Linux. | ||
| 2. The LPM feature is not supported on HS-SE variant J784S4. | ||
| 3. If PCIe is being used, the resume latency increases by 1 sec for every PCIe instance, If EP is not connected. |
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.
EP?.. Is it better to have this as Endpoint, wouldn't it be confusing EP alone ?
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.
EP is standard term
| 2. The LPM feature is not supported on HS-SE variant J784S4. | ||
| 3. If PCIe is being used, the resume latency increases by 1 sec for every PCIe instance, If EP is not connected. | ||
| 4. Remote core firmwares are getting loaded by Linux on resume. | ||
| 5. MCU domain R5 core, cannot be used in split mode. |
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.
This core cannot be used in split mode only to exercise LPM sequence correct ? So, isn't this a known issue rather than limitation.
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.
Its limitation rather than issue
| Software modifications | ||
| ---------------------- | ||
| TI’s K3 Jacinto family of SOCs have a concept of boardcfg that can be used to configure certain parameters at build time. | ||
| By default, SDK supports SOC_OFF mode. |
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.
By default, SDK supports SOC_OFF mode.
SDK supports both, but SOC_OFF is enabled/selected by default. So, may be something like below
By default, SOC_OFF mode enabled by default in SDK.
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.
will do this change . Thanks
Add flow diagram, hardware details to excercise LPM mode. Signed-off-by: Udit Kumar <u-kumar1@ti.com>
edce1d4 to
c52bd8d
Compare
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.
Nitpick: Let's use IO_RET everywhere and not IO-RET in this pic.
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.
Let's use "Decrypt"
| run application. | ||
| However, it is desired to run application use cases within 2-3 seconds of power on, for this purpose there are many custom | ||
| optimizations done, which are not scalable from platform to platform. | ||
| LPM saves partially SW state to DDR which helps in achieving faster boot. |
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.
partial
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.
thanks will reword
In LPM state, partial SW state is saved to DDR which helps in achieving faster boot
| | | I/O | | | | | ||
| +---------------------+---------------+---------------+-------------------------+-----------------------+ | ||
|
|
||
| Based upon, requirement of on power consumption and latency (the time it takes to wake-up to Active mode). |
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.
Based upon the requirement of power consumption and latency (the time it takes to wake-up to Active mode),
users can select the appropriate low power mode at build time to fit the needs of their application.
The default mode in the SDK is SOC OFF.
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.
ack
| ------------------ | ||
| LPM entry overview | ||
| ------------------ | ||
| After detecting condition to enter into standby, Application shall close all applications interacting with |
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.
This part is not clear to me. Which application is closing all applications ? Is it the kernel closing all the user space applications including the ones interacting with remote firmware ?
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.
Normally its power monitor thread, But will reword to below
After detecting the condition to enter standby, applications interacting with remote firmware shall be closed
before entering standby.
|
|
||
| In above board config file, default lpm_mode is 0x5 (SOC_OFF) and suspend_initiator is 0xA (A72_0 host). | ||
|
|
||
| To set the LPM mode as IO_RET_PLUS_DDR. Change lpm_mode to 0x2 |
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 set the LPM mode as IO_RET_PLUS_DDR, change lpm_mode to 0x2
| ----------------- | ||
| On receiving wakeup trigger, PMIC will restore power to SOC and SOC resume process will exit DDR from self-refresh mode and restore the | ||
| saved software context. | ||
| As part of resume process, firmwares of remote cores will be reloaded, Therefore application interacting with remote firmware shall be started again. |
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.
,therefore
| ----------------- | ||
| LPM exit overview | ||
| ----------------- | ||
| On receiving wakeup trigger, PMIC will restore power to SOC and SOC resume process will exit DDR from self-refresh mode and restore the |
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.
Throughout the document, I see SOC and SoC being mixed. The latter is the right one to use.
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.
Ack for this PR.
But in general this need fix in throughout whole repo
| .. ifconfig:: CONFIG_part_variant in ('J7200') | ||
|
|
||
| By default, SOC_OFF mode can be validated on J7200 EVM without any hardware changes. | ||
| In case IO_ONLY_PLUS_DDR needs to be tested user needs to do the following board modification. These modifications will not impact SOC_OFF mode. |
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 case IO_ONLY_PLUS_DDR mode needs to be tested,user needs to do the following board modification.
StaticRocket
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.
There are also vale comments and unnecessary unicode characters that need to be addressed.
| ---------------------- | ||
| Hardware modifications | ||
| ---------------------- |
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.
No description provided.