linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CF <cfoissac-GANU6spQydw@public.gmane.org>
Cc: "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Newbie: accessing i2c features through kernel functions
Date: Fri, 31 May 2013 11:49:41 +0200	[thread overview]
Message-ID: <51A87235.2060702@free.fr> (raw)
In-Reply-To: <1369818463.42609.YahooMailNeo-KCWTPBDN160R8UyDmTZ/NZEhsgyP+Z75VpNB7YpNyf8@public.gmane.org>

Hello,

I'm requesting help. I am currently successfully using i2c-dev module.
But i'm unable to drive i2c busses from kernel space as i'd do from
userspace (with the use of open, read, write, ioctl functions). I can't
logically acces glibc.

Can somebody point me how i could do from kernel space ? Given all is
actually working (precisely, i can recompile i2c-dev, and i write an
userspace code to manage my i2c slave device).

My goal is to keep i2c-dev suitable initialisation, then wrap some i2c
commands into the module to expose userspace a simplified API, with all
my device commands. I must do this in kernel space, else i'd have done
what i'm able to do: create an userspace lib relying on /dev/i2c-x.

Thank you. Once again i apologize if this is not the place but i'm
unable to find suitable ML for this kind of request.

  parent reply	other threads:[~2013-05-31  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  9:07 License for the libi2c Mihai Buha
     [not found] ` <1369818463.42609.YahooMailNeo-KCWTPBDN160R8UyDmTZ/NZEhsgyP+Z75VpNB7YpNyf8@public.gmane.org>
2013-05-31  9:49   ` CF [this message]
     [not found]     ` <51A87235.2060702-GANU6spQydw@public.gmane.org>
2013-05-31 14:56       ` Newbie: accessing i2c features through kernel functions Anatolij Gustschin
2013-05-31 20:47         ` CF
2013-06-02 21:38         ` CF

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=51A87235.2060702@free.fr \
    --to=cfoissac-ganu6spqydw@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).