| 73522f00 | 04-Jan-2019 |
Andrew F. Davis <afd@ti.com> |
ti: k3: drivers: ti_sci: Clear receive queue before transmitting
Send and receive currently must be be serialized, any message already in the receive queue when a new message is to be sent will caus
ti: k3: drivers: ti_sci: Clear receive queue before transmitting
Send and receive currently must be be serialized, any message already in the receive queue when a new message is to be sent will cause a mismatch with the expected response from this new message. Clear out all messages from the response queue before sending a new request.
Signed-off-by: Andrew F. Davis <afd@ti.com> Acked-by: Nishanth Menon <nm@ti.com>
show more ...
|
| ca3d3414 | 03-Jan-2019 |
Andrew F. Davis <afd@ti.com> |
ti: k3: common: Use shutdown API for PSCI core poweroff
To ensure WFI is reached before the PSC is trigger to power-down a processor, the shutdonw API must be used.
Signed-off-by: Andrew F. Davis <
ti: k3: common: Use shutdown API for PSCI core poweroff
To ensure WFI is reached before the PSC is trigger to power-down a processor, the shutdonw API must be used.
Signed-off-by: Andrew F. Davis <afd@ti.com> Acked-by: Nishanth Menon <nm@ti.com>
show more ...
|
| 72f418e0 | 03-Jan-2019 |
Andrew F. Davis <afd@ti.com> |
ti: k3: drivers: ti_sci: Add processor shutdown API
This is a pseudo-API command consisting of a wait processor status command and a set device state command queued back-to-back without waiting for
ti: k3: drivers: ti_sci: Add processor shutdown API
This is a pseudo-API command consisting of a wait processor status command and a set device state command queued back-to-back without waiting for the System Firmware to ACK either message.
This is needed as the K3 power down specification states the System Firmware must wait for a processor to be in WFI/WFE before powering it down. The current implementation of System Firmware does not provide such a command. Also given that with PSCI the core to be shutdown is the core that is processing the shutdown request, the core cannot itself wait for its own WFI/WFE status. To workaround this limitation, we submit a wait processor status command followed by the actual shutdown command. The shutdown command will not be processed until the wait command has finished. In this way we can continue to WFI before the wait command status has been met or timed-out and the shutdown command is processed.
Signed-off-by: Andrew F. Davis <afd@ti.com> Acked-by: Nishanth Menon <nm@ti.com>
show more ...
|
| 89ea53c7 | 04-May-2018 |
Andrew F. Davis <afd@ti.com> |
ti: k3: drivers: ti_sci: Add support for Processor control
TI-SCI message protocol provides support for controlling of various physical cores available in the SoC. In order to control which host is
ti: k3: drivers: ti_sci: Add support for Processor control
TI-SCI message protocol provides support for controlling of various physical cores available in the SoC. In order to control which host is capable of controlling a physical processor core, there is a processor access control list that needs to be populated as part of the board configuration data.
Introduce support for the set of TI-SCI message protocol APIs that provide us with this capability of controlling physical cores.
Signed-off-by: Andrew F. Davis <afd@ti.com> Reviewed-by: Andreas Dannenberg <dannenberg@ti.com>
show more ...
|
| 7b8f3e2d | 04-May-2018 |
Andrew F. Davis <afd@ti.com> |
ti: k3: drivers: ti_sci: Add support for Core control
Since system controller now has control over SoC power management, core operation such as reset need to be explicitly requested to reboot the So
ti: k3: drivers: ti_sci: Add support for Core control
Since system controller now has control over SoC power management, core operation such as reset need to be explicitly requested to reboot the SoC. Add support for this here.
Signed-off-by: Andrew F. Davis <afd@ti.com> Reviewed-by: Andreas Dannenberg <dannenberg@ti.com>
show more ...
|
| 6d1dfef6 | 04-May-2018 |
Andrew F. Davis <afd@ti.com> |
ti: k3: drivers: ti_sci: Add support for Clock control
TI-SCI message protocol provides support for management of various hardware entities within the SoC.
In general, we expect to function at a de
ti: k3: drivers: ti_sci: Add support for Clock control
TI-SCI message protocol provides support for management of various hardware entities within the SoC.
In general, we expect to function at a device level of abstraction, however, for proper operation of hardware blocks, many clocks directly supplying the hardware block needs to be queried or configured.
Introduce support for the set of TI-SCI message protocol support that provide us with this capability.
Signed-off-by: Andrew F. Davis <afd@ti.com> Reviewed-by: Andreas Dannenberg <dannenberg@ti.com>
show more ...
|
| 3858452d | 04-May-2018 |
Andrew F. Davis <afd@ti.com> |
ti: k3: drivers: ti_sci: Add support for Device control
TI-SCI message protocol provides support for management of various hardware entitites within the SoC.
We introduce the fundamental device man
ti: k3: drivers: ti_sci: Add support for Device control
TI-SCI message protocol provides support for management of various hardware entitites within the SoC.
We introduce the fundamental device management capability support to the driver protocol as part of this change.
Signed-off-by: Andrew F. Davis <afd@ti.com> Reviewed-by: Andreas Dannenberg <dannenberg@ti.com>
show more ...
|
| 903f13d3 | 26-Jul-2018 |
Andrew F. Davis <afd@ti.com> |
ti: k3: common: Only enable caches early
We can enter and exit coherency without any software operations, but HW_ASSISTED_COHERENCY has stronger implications that are causing issues. Until these can
ti: k3: common: Only enable caches early
We can enter and exit coherency without any software operations, but HW_ASSISTED_COHERENCY has stronger implications that are causing issues. Until these can be resolved, only use the weaker WARMBOOT_ENABLE_DCACHE_EARLY flag.
Signed-off-by: Andrew F. Davis <afd@ti.com>
show more ...
|