From: Nishanth Menon <menon.nishanth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Chandra shekhar <x0044955-l0cyMroinI0@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: I2C host adapter slave support
Date: Sat, 05 Jan 2008 11:41:06 -0600 [thread overview]
Message-ID: <477FC132.9070906@gmail.com> (raw)
In-Reply-To: <200801051713.m05HDElg011590-5Y3xciNRgV4YBkLn7j66hwC/G2K4zDHf@public.gmane.org>
Chandra shekhar wrote:
>
>
>> one thread of interest is:
>> http://lists.lm-sensors.org/pipermail/i2c/2007-April/001027.html
>>
>
> This is more related to opearting speed for i2c devices sitting on a common bus.
>
>
True, there is a side discussion on slave support
> Precisely, this is my question. If we were to support slave mode there should be
> Some callback or hooks to trigger upper layer app. after receive operations, which
> Ideally should be part of i2c-core I think.
> I am yet to look at i2c-pxa code.
You have not been reading too detailed in to the thread and not looked
at the code:
"http://lists.lm-sensors.org/pipermail/i2c/2007-April/001049.html:
:) this driver is compile time slave/master. Now, I have an i2c
controller which is capable of master /slave - ofcourse only one at a
time for one controller instance. But, I have n instances of the same.
Each capable of being slave or master based on board. The framework wont
let me do it unless I create two drivers - one for slave and other for
master - define separate adapters for them.. Not exactly efficient, but
could work. Can we do this with a cleaner support from i2c-core(like
able to write a single adapter driver which can be used as both
slave/master based ofcourse on board defns)? Maybe a seperate thread of
discussion?
"
So I guess this is that thread of discussion.
Gist:
a) you can implement i2c slave adapter support today with the existing
framework
b) my conjecture at the time of discussion was that "to have the same
driver to handle master and slave in a build might need further changes"
Regards,
Nishanth Menon
Regards,
Nishanth Menon
prev parent reply other threads:[~2008-01-05 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 14:55 I2C host adapter slave support Chandra shekhar
[not found] ` <200801041455.m04EtNnG003793-5Y3xciNRgV4YBkLn7j66hwC/G2K4zDHf@public.gmane.org>
2008-01-04 23:13 ` Nishanth Menon
[not found] ` <477EBD8D.9000807-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-01-05 17:13 ` Chandra shekhar
[not found] ` <200801051713.m05HDElg011590-5Y3xciNRgV4YBkLn7j66hwC/G2K4zDHf@public.gmane.org>
2008-01-05 17:41 ` Nishanth Menon [this message]
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=477FC132.9070906@gmail.com \
--to=menon.nishanth-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=x0044955-l0cyMroinI0@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