diff options
| author | Brian Norris <computersforpeace@gmail.com> | 2016-01-29 11:25:30 -0800 |
|---|---|---|
| committer | Brian Norris <computersforpeace@gmail.com> | 2016-03-07 18:01:50 -0800 |
| commit | edf891ef9ab773363f8e58022a26d7d31604aed6 (patch) | |
| tree | 8ca9c77d6cb09b14dcdd4744726f0f865acc6f13 /kernel/memremap.c | |
| parent | a8c65d504e0b2256f7672506ae6ea68d88ef020a (diff) | |
| download | op-kernel-dev-edf891ef9ab773363f8e58022a26d7d31604aed6.zip op-kernel-dev-edf891ef9ab773363f8e58022a26d7d31604aed6.tar.gz | |
mtd: spi-nor: wait for SR_WIP to clear on initial unlock
Fixup a piece leftover by commit 32321e950d8a ("mtd: spi-nor: wait until
lock/unlock operations are ready"). That commit made us wait for the WIP
bit to settle after lock/unlock operations, but it missed the open-coded
"unlock" that happens at probe() time.
We should probably have this code utilize the unlock() routines in the
future, to avoid duplication, but unfortunately, flash which need to be
unlocked don't all have a proper ->flash_unlock() callback.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Cc: Stas Sergeev <stsp@users.sourceforge.net>
Reviewed-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Tested-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Diffstat (limited to 'kernel/memremap.c')
0 files changed, 0 insertions, 0 deletions
