From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Does i2c module work in RedBoot?
Date: Mon, 12 Feb 2007 16:30:00 -0000 [thread overview]
Message-ID: <eqq4mm$4b0$1@sea.gmane.org> (raw)
In-Reply-To: <pn64a7cpfc.fsf@delenn.bartv.net>
On 2007-02-12, Bart Veer <bartv@ecoscentric.com> wrote:
> Grant> Thanks. I've heard from a couple others who also use the
> Grant> i2c module in RedBoot.
>
> Grant> I glanced at the souce code and noticed calls to mutex
> Grant> routines and wasn't sure if that would cause problems or
> Grant> not.
>
> Those calls involve the driver API rather than the kernel API,
> allowing the generic I2C code to work correctly in both a
> multi-threaded kernel configuration and in a polled-only
> configuration like RedBoot. However note that it is not just
> the generic I2C support CYGPKG_IO_I2C you need to worry about.
> Typically there will also be a hardware-specific device driver
> and that needs to do the right thing as well. Usually that is
> not hard - in the tx and rx routines check whether or not
> interrupts are enabled and then either poll or wait for the
> interrupt - but some device drivers may not bother.
>
> If instead of a driver for some I2C bus master hardware you
> are using the bitbanging support in the generic package, that
> is usable in both interrupt-driven and polled environments.
Yes, I'm planning on using the bit-banging driver (I should
have mentioned that), so it sounds like there shouldn't be any
problems.
--
Grant Edwards grante Yow! Now my EMOTIONAL
at RESOURCES are heavily
visi.com committed to 23
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-02-12 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 2:51 [ECOS] " Grant Edwards
2007-02-12 4:17 ` wang cui
2007-02-12 15:25 ` [ECOS] " Grant Edwards
2007-02-12 16:27 ` Bart Veer
2007-02-12 16:30 ` Grant Edwards [this message]
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='eqq4mm$4b0$1@sea.gmane.org' \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).