linux-kernel - Re: I2C from interrupt context?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081106.154754.02648408.davem@davemloft.net>
Date:	Thu, 06 Nov 2008 15:47:54 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	khc@...waw.pl
Cc:	linux-kernel@...r.kernel.org, khali@...ux-fr.org,
	linux-i2c@...r.kernel.org
Subject: Re: I2C from interrupt context?

From: Krzysztof Halasa <khc@...waw.pl>
Date: Fri, 07 Nov 2008 00:44:48 +0100

[ Fixed i2c list address, it's now hosted at vger ]

> I'm updating my EEPROM console logger and have encountered a problem
> - the logger (as any console) can be called with hardware interrupts
> disabled and/or from interrupt context. It needs to write to I^2C
> (using ARM (Xscale) GPIO) and possibly SMBUS-only EEPROM chip. Is it
> at all supposed to be possible?

Not really.  The I2C operations need to be able to sleep and that's
not allowed in interrupt context.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/