On Thu, 16 May 2013 21:30:59 +0100
Russell King rmk+ker...@arm.linux.org.uk wrote:
Do not use interruptible waits in an I2C driver; if a process uses
signals (eg, Xorg uses SIGALRM and SIGPIPE) then these signals can
cause the I2C driver to abort a transaction in progress by another
driver,
On Fri, May 17, 2013 at 08:37:43AM +0200, Jean-Francois Moine wrote:
On Thu, 16 May 2013 21:30:59 +0100
Russell King rmk+ker...@arm.linux.org.uk wrote:
Do not use interruptible waits in an I2C driver; if a process uses
signals (eg, Xorg uses SIGALRM and SIGPIPE) then these signals can
On Thu, May 16, 2013 at 09:30:59PM +0100, Russell King wrote:
Do not use interruptible waits in an I2C driver; if a process uses
signals (eg, Xorg uses SIGALRM and SIGPIPE) then these signals can
cause the I2C driver to abort a transaction in progress by another
driver, which can cause that
On Thu, May 16, 2013 at 09:30:59PM +0100, Russell King wrote:
Do not use interruptible waits in an I2C driver; if a process uses
signals (eg, Xorg uses SIGALRM and SIGPIPE) then these signals can
cause the I2C driver to abort a transaction in progress by another
driver, which can cause that
Do not use interruptible waits in an I2C driver; if a process uses
signals (eg, Xorg uses SIGALRM and SIGPIPE) then these signals can
cause the I2C driver to abort a transaction in progress by another
driver, which can cause that driver to fail. I2C drivers are not
expected to abort transactions
