Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753461AbYKFXo7 (ORCPT ); Thu, 6 Nov 2008 18:44:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751391AbYKFXou (ORCPT ); Thu, 6 Nov 2008 18:44:50 -0500 Received: from khc.piap.pl ([195.187.100.11]:57645 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751293AbYKFXou (ORCPT ); Thu, 6 Nov 2008 18:44:50 -0500 To: Cc: khali@linux-fr.org, i2c@lm-sensors.org Subject: I2C from interrupt context? From: Krzysztof Halasa Date: Fri, 07 Nov 2008 00:44:48 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 576 Lines: 14 Hi, 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? -- Krzysztof Halasa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/