From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Romeo Enrico <romeo-xL9mfXOxRcg@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Omap3 : I2c Driver I2C_M_RECV_LEN support
Date: Sun, 21 Feb 2010 12:01:07 +0100 [thread overview]
Message-ID: <20100221120107.6bc57138@hyperion.delvare> (raw)
In-Reply-To: <4B7BCB20.4080008-xL9mfXOxRcg@public.gmane.org>
Hi Enrico,
On Wed, 17 Feb 2010 11:55:28 +0100, Romeo Enrico wrote:
> In Order to implement the communication between an Omap3530 configured
> as master and a custom device configured as slave, I need to be able to
> configure the size of readings dynamically according to the first byte
> sent by the slave.
> Checking kernel I found that in include/linux/i2c.h is declared the
> I2C_M_RECV_LEN flag for the "struct i2c_msg" which should be what I'm
> looking for...
This is correct. This mechanism is used for the SMBus Block Read
transaction.
> But I have not found an implementation of this feature in
> the Omap I2c driver.
>
> Can anyone confirm that the I2C_M_RECV_LEN is not actually supported by
> the Omap I2c driver ?
Looking at the source code of the i2c-omap driver in Linus' kernel, I
can confirm there is no support. You might want to check for updates in
the omap tree though, or even ask on an omap-specific list: someone
might have already implemented it but not pushed it to mainstream yet.
--
Jean Delvare
prev parent reply other threads:[~2010-02-21 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 10:55 Omap3 : I2c Driver I2C_M_RECV_LEN support Romeo Enrico
[not found] ` <4B7BCB20.4080008-xL9mfXOxRcg@public.gmane.org>
2010-02-21 11:01 ` Jean Delvare [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=20100221120107.6bc57138@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=romeo-xL9mfXOxRcg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.