diff options
| author | Andrew F. Davis <[email protected]> | 2017-06-13 18:45:13 -0500 |
|---|---|---|
| committer | Bjorn Andersson <[email protected]> | 2017-06-26 13:02:44 -0700 |
| commit | 11d2a2ffa881c971bab065d6e38c33849f35e7bc (patch) | |
| tree | dc1ed878faff73e803b2139ad6d1156f867a5872 | |
| parent | e88bb8f7a12c1325e312c214f157109d56b06f76 (diff) | |
remoteproc/keystone: Ensure the DSPs are in reset in probe
The DSPs are expected to be in reset when the driver probes a device.
If the DSPs are out of reset in probe, the system may crash when the
firmware is being loaded. So, add a check to make sure the DSP resets
are asserted, and if not, throw a eye-catchy warning and assert the
resets specifically.
Signed-off-by: Andrew F. Davis <[email protected]>
[[email protected]: replace warning with a WARN]
Signed-off-by: Suman Anna <[email protected]>
Acked-by: Santosh Shilimkar <[email protected]>
Signed-off-by: Bjorn Andersson <[email protected]>
| -rw-r--r-- | drivers/remoteproc/keystone_remoteproc.c | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/drivers/remoteproc/keystone_remoteproc.c b/drivers/remoteproc/keystone_remoteproc.c index 6e09ef76f7c7..5f776bfd674a 100644 --- a/drivers/remoteproc/keystone_remoteproc.c +++ b/drivers/remoteproc/keystone_remoteproc.c @@ -456,6 +456,16 @@ static int keystone_rproc_probe(struct platform_device *pdev) if (of_reserved_mem_device_init(dev)) dev_warn(dev, "device does not have specific CMA pool\n"); + /* ensure the DSP is in reset before loading firmware */ + ret = reset_control_status(ksproc->reset); + if (ret < 0) { + dev_err(dev, "failed to get reset status, status = %d\n", ret); + goto release_mem; + } else if (ret == 0) { + WARN(1, "device is not in reset\n"); + keystone_rproc_dsp_reset(ksproc); + } + ret = rproc_add(rproc); if (ret) { dev_err(dev, "failed to add register device with remoteproc core, status = %d\n", |