diff options
| author | Lokesh Vutla <lokeshvutla@ti.com> | 2019-05-02 15:35:52 +0530 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2019-05-09 20:22:05 -0400 |
| commit | 0d7b6cffa532eecfdc7cb87c2c65cd311344981f (patch) | |
| tree | 0afab773bb17cb8f33ab6e2e2b969423ec36140b /drivers/remoteproc | |
| parent | a325796da48c3623b9e572dc329f97b83ec2a01c (diff) | |
| download | u-boot-0d7b6cffa532eecfdc7cb87c2c65cd311344981f.tar.gz u-boot-0d7b6cffa532eecfdc7cb87c2c65cd311344981f.tar.bz2 u-boot-0d7b6cffa532eecfdc7cb87c2c65cd311344981f.zip | |
remoteproc: k3_system_controller: Increase rx timeout
There is one case where 400ms is not sufficient for loading the
system firmware:
- System firmware is not signed with rsa degenerate key.
- ROM loading the sysfw directly from SPI flash which is in memory
mapped mode.
The above scenario is definitely not desired in production use cases
as it effects boot time. But still keeping this support as this is
a valid boot scenario.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Diffstat (limited to 'drivers/remoteproc')
| -rw-r--r-- | drivers/remoteproc/k3_system_controller.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/remoteproc/k3_system_controller.c b/drivers/remoteproc/k3_system_controller.c index 214ea18d8a..44e56c759f 100644 --- a/drivers/remoteproc/k3_system_controller.c +++ b/drivers/remoteproc/k3_system_controller.c @@ -301,7 +301,7 @@ static int k3_sysctrler_probe(struct udevice *dev) static const struct k3_sysctrler_desc k3_sysctrler_am654_desc = { .host_id = 4, /* HOST_ID_R5_1 */ - .max_rx_timeout_us = 400000, + .max_rx_timeout_us = 800000, .max_msg_size = 60, }; |