Hi,
I'm facing a deadlock regarding a timer callback which is only calling
i2c_transfer(), and I wonder if this comes from that call: I first
googled and found that i2c_transfer() may sleep (which is forbidden in
my timer callback) but when I have a look the beginning of the function,
it starts to check if it is in any atomic context, before trying to
acquire a lock...
So I'm afraid I'm lost and I hope someone will be able to understand to
that question: might i2c_transfer() be used in a timer callback or
should I handle my periodic call to i2c_tranfer() by means of a delayed
work?
Thanks for your reply,
Regards,
Stéphane
--
PEAK-System Technik GmbH, Otto-Roehm-Strasse 69, D-64293 Darmstadt
Geschaeftsleitung: A.Gach/U.Wilhelm,St.Nr.:007/241/13586 FA Darmstadt
HRB-9183 Darmstadt, Ust.IdNr.:DE 202220078, WEE-Reg.-Nr.: DE39305391
Tel.+49 (0)6151-817320 / Fax:+49 (0)6151-817329, info@xxxxxxxxxxxxxxx
----
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
