diff options
| author | Lokesh Vutla <lokeshvutla@ti.com> | 2019-09-27 13:48:12 +0530 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2019-10-15 08:40:03 -0600 |
| commit | af94ad418dc72957d3b7398d83bfc5a1efd415db (patch) | |
| tree | c99f1c80c70def1aca9b42cac1c0a3acffd1bc47 /drivers/core | |
| parent | d8efa2ce2abe293c97576f47ccac708e233553b6 (diff) | |
| download | u-boot-af94ad418dc72957d3b7398d83bfc5a1efd415db.zip u-boot-af94ad418dc72957d3b7398d83bfc5a1efd415db.tar.gz u-boot-af94ad418dc72957d3b7398d83bfc5a1efd415db.tar.bz2 | |
dm: core: Allow for not controlling the power-domain by DM framework
In some remoteproc cases, enabling the power domain of the core will
start running the core. In such cases image should be loaded before
enabling the power domain. But the current DM framework enables the
power-domain by default during probe. This is causing the remotecore
to start and crash as there is no valid image loaded.
In order to avoid this introduce a DM flag that doesn't allow for
enabling/disabling the power-domain by DM framework.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/core')
| -rw-r--r-- | drivers/core/device.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/core/device.c b/drivers/core/device.c index 28363ff..95f26ef 100644 --- a/drivers/core/device.c +++ b/drivers/core/device.c @@ -393,7 +393,8 @@ int device_probe(struct udevice *dev) pinctrl_select_state(dev, "default"); if (CONFIG_IS_ENABLED(POWER_DOMAIN) && dev->parent && - device_get_uclass_id(dev) != UCLASS_POWER_DOMAIN) { + (device_get_uclass_id(dev) != UCLASS_POWER_DOMAIN) && + !(drv->flags & DM_FLAG_DEFAULT_PD_CTRL_OFF)) { ret = dev_power_domain_on(dev); if (ret) goto fail; |