| author | jiamin ma <jiamin.ma@amlogic.com> | 2018-07-31 10:11:54 (GMT) |
|---|---|---|
| committer | Jianxin Pan <jianxin.pan@amlogic.com> | 2018-08-01 02:25:50 (GMT) |
| commit | 7d5c6af845563a828f382167dfd6a1d6c1efb78e (patch) | |
| tree | cb1ebc331cd76064ec7a843cb9970579fba7a4f0 | |
| parent | b9d6392bd9b34cc143149f6826f385f1e7d03f82 (diff) | |
| download | common-7d5c6af845563a828f382167dfd6a1d6c1efb78e.zip common-7d5c6af845563a828f382167dfd6a1d6c1efb78e.tar.gz common-7d5c6af845563a828f382167dfd6a1d6c1efb78e.tar.bz2 | |
unifykey: switch init order of unifykey and securitykey
PD#170850: unifykey: wrong unifykey driver init status
The linux driver init order depends on init func level and
position in Makefile. Securitykey and unifykey are both
necessary for unifykey driver to work normal. Currently
securitykey is always initialized before unifykey, and the
unifykey init status checking API only checkes whether the
probe process of unifykey is done.So there is a chance when
LCD driver get unifykey probing process done status, while
securitykey is still under probing, which means unifykey
still cannot work normal
We should switch the init order of these two module to
solve this issue
Change-Id: I8c4471d3689cff4356645fdc45df735be625baa2
Signed-off-by: jiamin ma <jiamin.ma@amlogic.com>
| -rw-r--r-- | drivers/amlogic/unifykey/Makefile | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/amlogic/unifykey/Makefile b/drivers/amlogic/unifykey/Makefile index 84dea1372..6f51526 100644 --- a/drivers/amlogic/unifykey/Makefile +++ b/drivers/amlogic/unifykey/Makefile @@ -1,8 +1,8 @@ # # Makefile for unifykey # -obj-$(CONFIG_AMLOGIC_UNIFYKEY) += unifykey.o unifykey_dts.o storagekey.o - obj-$(CONFIG_AMLOGIC_V8_UNIFYKEY) += v8/ obj-$(CONFIG_AMLOGIC_V7_UNIFYKEY) += v7/ + +obj-$(CONFIG_AMLOGIC_UNIFYKEY) += unifykey.o unifykey_dts.o storagekey.o |