[Letux-kernel] ov9655 madness in 4.20

H. Nikolaus Schaller hns at goldelico.com
Sat Jan 5 19:01:16 CET 2019


Hi Andreas,

> Am 05.01.2019 um 18:58 schrieb Andreas Kemnade <andreas at kemnade.info>:
> 
> On Sat, 5 Jan 2019 15:49:28 +0100
> Andreas Kemnade <andreas at kemnade.info> wrote:
> 
> [...]
>> [  290.168395] ov9655 1-0030: __ov9655_set_power on=1
>> [  290.223907] ov9655 1-0030: Failed to enable clock (-6)
>> <-- probably the interesting root cause for further problems.
>> 
> ok, found out what seems to happen here:
> If I rmmod omap3_isp, the ov9655 driver keeps a reference to the clock
> of that now unregistered module and continues to work with that
> reference.

Ok, I see.

> So the workaround is easily rmmod both omap3_isp and ov9655
> and this is nothing with high priority to fix.

Well, should it be locked somehow? Other modules seems to be able
to describe dependencies and then you can't even rmmod them.

> Neither it is a symptome
> of more severe problems.
> 
> This does not recover the device from non-working states. So
> starting camera-demo, then rmmod ; inmod ; starting camera-demo again
> does not work.

Ok, good research!

Unfortunately it does not reveal anything about the "starting camera-demo again does not work" problem.

BR and thanks,
Nikolaus

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.goldelico.com/pipermail/letux-kernel/attachments/20190105/978d5ff0/attachment.asc>


More information about the Letux-kernel mailing list