diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2015-07-25 21:52:34 +0900 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2015-08-06 07:44:29 -0600 |
commit | aed1a4dd88e94001b811b297c1ff734c3f8d22d9 (patch) | |
tree | de57a73634e7d1b673be8379d6893eaf62d03ee6 /include/dm | |
parent | f33017716e5c430d84366ecc4476ba2b655f3fef (diff) | |
download | u-boot-imx-aed1a4dd88e94001b811b297c1ff734c3f8d22d9.zip u-boot-imx-aed1a4dd88e94001b811b297c1ff734c3f8d22d9.tar.gz u-boot-imx-aed1a4dd88e94001b811b297c1ff734c3f8d22d9.tar.bz2 |
dm: add DM_FLAG_BOUND flag
Currently, we only have DM_FLAG_ACTIVATED to indicate the device
status, but we still cannot know in which stage is in progress,
binding or probing.
This commit introduces a new flag, DM_FLAG_BOUND, which is set when
the device is really bound, and cleared when it is unbound.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'include/dm')
-rw-r--r-- | include/dm/device.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/include/dm/device.h b/include/dm/device.h index 12fd02d..4cd7ba3 100644 --- a/include/dm/device.h +++ b/include/dm/device.h @@ -36,6 +36,9 @@ struct driver_info; /* Allocate driver private data on a DMA boundary */ #define DM_FLAG_ALLOC_PRIV_DMA (1 << 5) +/* Device is bound */ +#define DM_FLAG_BOUND (1 << 6) + /** * struct udevice - An instance of a driver * |