linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Flugstad <pete.flugstad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: exclusive access to I2C device
Date: Thu, 4 Mar 2010 12:06:23 -0600	[thread overview]
Message-ID: <84d4a6d51003041006i1b619d2l942d21ce1a9a069e@mail.gmail.com> (raw)

Hi!  We're running Linux 2.6.27 with i2c tools 3.0.2.

We have a number of userspace program using the raw i2c_smbus interface
to talk to a variety of devices. Right now, it seems like every program can open
up the device and issue commands, which interferes with an already running
command.

I see the code in open_i2c_bus using:

    	sprintf(filename, "/dev/i2c/%d", i2cbus);
	file = open(filename, O_RDWR);

Would adding O_EXCL to this open help to make things exclusive?  Or is there a
better way to do what I want.

Right now we're going to set up a daemon to arbitrate access to the I2C bus,
but it would be nice if we had something simpler, since now all apps have to
talk to the daemon.  I was thinking something along the lines of just telling
userspace to loop opening the device exclusively until that succeeds, run the
command,  then close the device.

Thanks,
Pete

             reply	other threads:[~2010-03-04 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 18:06 Pete Flugstad [this message]
     [not found] ` <84d4a6d51003041006i1b619d2l942d21ce1a9a069e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-10 11:03   ` exclusive access to I2C device Jean Delvare

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=84d4a6d51003041006i1b619d2l942d21ce1a9a069e@mail.gmail.com \
    --to=pete.flugstad-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-i2c-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 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 NNTP newsgroup(s).