From: "Dan Mor" <dmor-ukWli4Tkv9rQT0dZR+AlfA@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: ds1682
Date: Tue, 15 Sep 2009 21:05:01 +0300 [thread overview]
Message-ID: <000001ca362f$0ef74790$2ce5d6b0$@com> (raw)
Hi Guys,
I am trying to use ds1682 Linux driver under 2.6.27.30 Fedora Core 10
Kernel.
I am new to sysfs driver approach. I successfully compiled the module and
loaded it.
The device doesn't recognized by default and no sub directories created.
I add insmode parameters to the driver and loading it with force=i2c_bus,
i2c_address parameters.
In this case, it works.
I can read/write from/to devices by: cat /sys/..../elapsed_time, etc.
My question is, how can I read/write from/to sysfs from the C test
application?
I am trying to: "open" "/sys/..../elapsed_time" and "read" from it but
apparently I am doing something wrong.
Do you have some C code examples of how to communicate with sysfs devices?
Regards,
Dan
reply other threads:[~2009-09-15 18:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000001ca362f$0ef74790$2ce5d6b0$@com' \
--to=dmor-ukwli4tkv9rqt0dzr+alfa@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).