From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: khc-9GfyWEdoJtJmR6Xm/wNWPw@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: I2C from interrupt context?
Date: Thu, 06 Nov 2008 15:47:54 -0800 (PST) [thread overview]
Message-ID: <20081106.154754.02648408.davem@davemloft.net> (raw)
In-Reply-To: <m3bpws8ln3.fsf-fiqtE+24Nu0B9AHHLWeGtNQXobZC6xk2@public.gmane.org>
From: Krzysztof Halasa <khc-9GfyWEdoJtJmR6Xm/wNWPw@public.gmane.org>
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.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: khc@pm.waw.pl
Cc: linux-kernel@vger.kernel.org, khali@linux-fr.org,
linux-i2c@vger.kernel.org
Subject: Re: I2C from interrupt context?
Date: Thu, 06 Nov 2008 15:47:54 -0800 (PST) [thread overview]
Message-ID: <20081106.154754.02648408.davem@davemloft.net> (raw)
In-Reply-To: <m3bpws8ln3.fsf@maximus.localdomain>
From: Krzysztof Halasa <khc@pm.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.
next prev parent reply other threads:[~2008-11-06 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 23:44 I2C from interrupt context? Krzysztof Halasa
[not found] ` <m3bpws8ln3.fsf-fiqtE+24Nu0B9AHHLWeGtNQXobZC6xk2@public.gmane.org>
2008-11-06 23:47 ` David Miller [this message]
2008-11-06 23:47 ` David Miller
[not found] ` <20081106.154754.02648408.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-11-07 9:11 ` Jean Delvare
2008-11-07 9:11 ` Jean Delvare
[not found] ` <20081107101118.286f3713-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-11-07 16:05 ` Krzysztof Halasa
2008-11-07 16:05 ` Krzysztof Halasa
[not found] ` <m3bpwrbjxs.fsf-fiqtE+24Nu0B9AHHLWeGtNQXobZC6xk2@public.gmane.org>
2008-11-11 7:57 ` Andrew Morton
2008-11-11 7:57 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081106.154754.02648408.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=khc-9GfyWEdoJtJmR6Xm/wNWPw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.