From: krzaq <krzakers@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: open() and read() a file from sysfs
Date: Mon, 28 Feb 2005 15:18:44 +0100 [thread overview]
Message-ID: <2ab8d39a050228061825dda7fe@mail.gmail.com> (raw)
Hi all!
I have a basic question with file opening.
I would like to make use of the data accessed from i2c sensors through sysfs.
Here's the code:
fd = open(/sys/bus/i2c/.../temp2_input,O_RDONLY);
while(1) {
char[64] buf;
read(fd,buf,siezof(buf));
...
do_something
...
sleep(5);
}
The thing is I always get the same reading in each read() :(.
When I do:
# cat /sys/bus/i2c.../temp2_input
I see that the temperature is changing, but my code still displays the
same reading.
So what's the deal? Why is it cached?
Am I supposed to open() and close() the file inside 'while' loop??
What's the proper way to do it?
--
Regards
Karol Krzak
next reply other threads:[~2005-02-28 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 14:18 krzaq [this message]
2005-03-01 1:17 ` open() and read() a file from sysfs simon
2005-03-01 8:58 ` krzaq
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=2ab8d39a050228061825dda7fe@mail.gmail.com \
--to=krzakers@gmail.com \
--cc=linux-c-programming@vger.kernel.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).