Comment 42 for bug 790183

> Could you implement some check too see if initialization was completed
> earlier? Maybe some register value changes after init, etc?

Unfortunately I don't know how to query registers on this device. During initialization I'm sending some blobs and occasionally read something back, but I have no idea what it all means :-/

But it does not harm to do this initialization many times. It would not harm to do it every time dev_activate is called – the hardware seems to be fine with that.

The only problem is how to handle the delay which happens during this initialization properly, so that it won't disappoint the user.

> Library doesn't expect any device init in dev_open, so it's not a good idea.

But is there some technical reason why it should not be there right now? I mean, can this (doing device initialization in dev_open) break things, cause incorrect behavior in some situations?

By the way, I also have an unrelated question. If an application opens the device and then enrolls/verifies/identifies fingers a few times, will dev_activate be called every time when the finger needs to be scanned, or just once?

Sorry, I cannot chat now, I don't have more time today.