From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: vidhumouli hunsigida <hv_mouli-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: IOCTL implementation in i2c Hostt/master controllers
Date: Tue, 2 Sep 2008 09:02:18 +0200 [thread overview]
Message-ID: <20080902090218.2604df0d@hyperion.delvare> (raw)
In-Reply-To: <463640.33128.qm-tLTVmYjyaXCB9c0Qi4KiSs0jms80CZx+QQ4Iyu8u01E@public.gmane.org>
Hi Vidhumouli,
On Mon, 1 Sep 2008 22:30:10 -0700 (PDT), vidhumouli hunsigida wrote:
> I forgot to ask the question.....
>
> Can any one give me a poointer to any link/document from where
> I can understand the flow correctly?
The only document we have is Documentation/i2c/dev-interface in the
kernel source tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/i2c/dev-interface
However it describes the API to /dev/i2c-N, not the flow from your
application to the I2C bus driver. For that, maybe the best we have is
this picture:
http://www.lm-sensors.org/attachment/wiki/Documentation/layers.gif
But it's not necessarily very clear.
(And it shouldn't be on the lm-sensors.org wiki, but that's another
story.)
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-09-02 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 5:30 IOCTL implementation in i2c Hostt/master controllers vidhumouli hunsigida
[not found] ` <463640.33128.qm-tLTVmYjyaXCB9c0Qi4KiSs0jms80CZx+QQ4Iyu8u01E@public.gmane.org>
2008-09-02 7:02 ` Jean Delvare [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-02 5:21 vidhumouli hunsigida
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=20080902090218.2604df0d@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=hv_mouli-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@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