diff options
author | Dmitry Pervushin <dpervushin@embeddedalley.com> | 2009-04-29 19:29:38 +0400 |
---|---|---|
committer | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2009-06-02 13:53:35 +0300 |
commit | 0e0ee1cc33de8f0cc603269b354085dee340afa0 (patch) | |
tree | 5dfd658b85eabadfbf0c94bee94d46f8d74b839b /crypto/rmd160.c | |
parent | b86a2c56e512f46d140a4bcb4e35e8a7d4a99a4b (diff) | |
download | blackbird-obmc-linux-0e0ee1cc33de8f0cc603269b354085dee340afa0.tar.gz blackbird-obmc-linux-0e0ee1cc33de8f0cc603269b354085dee340afa0.zip |
UBI: add notification API
UBI volume notifications are intended to create the API to get clients
notified about volume creation/deletion, renaming and re-sizing. A
client can subscribe to these notifications using 'ubi_volume_register()'
and cancel the subscription using 'ubi_volume_unregister()'. When UBI
volumes change, a blocking notifier is called. Clients also can request
"added" events on all volumes that existed before client subscribed
to the notifications.
If we use notifications instead of calling functions like 'ubi_gluebi_xxx()',
we can make the MTD emulation layer to be more flexible: build it as a
separate module and load/unload it on demand.
[Artem: many cleanups, rework locking, add "updated" event, provide
device/volume info in notifiers]
Signed-off-by: Dmitry Pervushin <dpervushin@embeddedalley.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'crypto/rmd160.c')
0 files changed, 0 insertions, 0 deletions