From mboxrd@z Thu Jan  1 00:00:00 1970
From: john@jjdev.com (John de la Garza)
Date: Wed, 19 Aug 2015 23:17:01 -0700
Subject: msleep() in interrupt handler?
In-Reply-To: <CAAsE_uct0qR_nb2WbQD6qpNEsWdwuRB9xVeU85A0uiBbkqgGpA@mail.gmail.com>
References: <CAAsE_uf_Hf2FHyaR=7kZXVMmiXLYPJ-cvS59UcGDAxAfjq40GA@mail.gmail.com>
	<4E5779AD88B2F040B8A7E83ECF544D1A615876@SJCPEX01CL03.citrite.net>
	<CAAsE_uct0qR_nb2WbQD6qpNEsWdwuRB9xVeU85A0uiBbkqgGpA@mail.gmail.com>
Message-ID: <20150820061700.GA7731@crux>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Thu, Aug 20, 2015 at 01:45:34PM +0800, Woody Wu wrote:
> I did not see the message.  Actually my interrupt handler is calling
> i2c_transfer which in turn used msleep() somewhere in its code.  Is this
> normal or dangerous?

Can you have the interrupt handler put the work on a workqueue
and quickly return?