On Fri, Oct 07, 2016 at 02:24:59PM +0000, Winkler, Tomas wrote: > So here I'm to say I'm sorry for misleading this, after all the > doubts I got back to debugging and traces. One thing for a reason > moving the device_del, had really made the problem go away, but the > real problem was unbalance runtime_pm PUT/GET from the tpm_crb probe > function.
Oh this is very good news, I'm glad this was resolved in crb! Presumably the unbalanced put made the ref count go negative and the balanced get caused it to go to zero, so pm locking was basically totally broken? That would explain how an idle callback could run concurrently with transmit_cmd. Though a bit of a mystery why device_del had any impact? I'm still very unclear exactly how the child device effects the parent - and that seems like pretty important information going forward.. Thanks, Jason ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ tpmdd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
