From: Svein Seldal <sveinse@seldal.com>
To: linux-i2c@vger.kernel.org
Subject: i2c-tools userspace tools
Date: Thu, 14 Apr 2016 23:55:22 +0200 [thread overview]
Message-ID: <571011CA.7090307@seldal.com> (raw)
Hi
Is this the right list to discuss the i2c-tools user space software? If
not, please disregard this email.
I have noticed that I can't seem to be able to use these tools out of
box for very many i2c devices, as the i2cget/i2cset isn't using a very
common protocol that these chips use.
E.g. the protocol for byte/word read (which is also found in the SMBUS
spec) is:
START - WR:SLAVE - DADR - START - RD:SLAVE - DATA - STOP
From what I have tested, it seems "i2cget BUS SLAVE DADR" does the
following
START - WR:SLAVE - DADR - START - RD:SLAVE - DADR - DATA - STOP
It contains an extra read DADR byte, which is the slot where the actual
data is being returned.
(My workaround is to run "i2cset BUS SLAVE CMD; i2cget BUS SLAVE")
Is this something that patches will be accepted for?
Best regards,
sveinse
reply other threads:[~2016-04-14 21:55 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=571011CA.7090307@seldal.com \
--to=sveinse@seldal.com \
--cc=linux-i2c@vger.kernel.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).