From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Gary Chambers <gwc-OVIABD91gjs3uPMLIKxrzw@public.gmane.org>
Cc: I2C Mailing List <i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: Re: I2C_SMBUS_WORD Definition
Date: Tue, 22 Jan 2008 15:01:15 +0100 [thread overview]
Message-ID: <20080122150115.03eed1b6@hyperion.delvare> (raw)
In-Reply-To: <Pine.LNX.4.64.0801211310050.18738-kD1P2mHmSlqz6L9v6lnKkIdd74u8MsAO@public.gmane.org>
Hi Gary,
On Mon, 21 Jan 2008 14:17:00 -0500 (EST), Gary Chambers wrote:
> > Well, reading two bytes from a device directly doesn't correspond to
> > any SMBus transaction, so if your bus controller doesn't support I2C
> > messaging, I fear that you're pretty much stuck.
>
> How authoritative is the functionality matrix? My call to it returns
> 0xcfffc006 -- no pure I2C, but it appears that I can perform I2C block
> writes and reads.
The functionality matrix can be trusted in general, but if you'd tell
me what i2c adapter driver this is, I could double-check. Also note
that "i2cdetect -F" can list the functionality in a much more
human-friendly format.
> > What adapter is this? And what chip are you trying to talk to?
>
> It's a [seemingly] simple TI DAC5571 (single-channel, 8-bit DAC) on an
> evaluation module.
Are you sure that the TI DAC5571 DAC value can be read at all? I've
downloaded the datasheet and all it mentions is writing to the DAC5571,
not reading from it.
> Thanks for your (and the list's) patience while I gain some footing with
> this.
You're welcome.
--
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-01-22 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 20:30 I2C_SMBUS_WORD Definition Gary Chambers
[not found] ` <Pine.LNX.4.64.0801181524040.14018-kD1P2mHmSlqz6L9v6lnKkIdd74u8MsAO@public.gmane.org>
2008-01-19 16:49 ` Jean Delvare
[not found] ` <20080119174950.1f12f3c0-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-01-19 20:55 ` Gary Chambers
[not found] ` <Pine.LNX.4.64.0801191539500.18738-kD1P2mHmSlqz6L9v6lnKkIdd74u8MsAO@public.gmane.org>
2008-01-20 9:23 ` Jean Delvare
[not found] ` <20080120102335.5cc6a936-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-01-21 19:17 ` Gary Chambers
[not found] ` <Pine.LNX.4.64.0801211310050.18738-kD1P2mHmSlqz6L9v6lnKkIdd74u8MsAO@public.gmane.org>
2008-01-22 14:01 ` Jean Delvare [this message]
[not found] ` <20080122150115.03eed1b6-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-01-23 20:48 ` DAC5571 Gary Chambers
[not found] ` <Pine.LNX.4.64.0801231538250.18738-kD1P2mHmSlqz6L9v6lnKkIdd74u8MsAO@public.gmane.org>
2008-01-26 9:37 ` DAC5571 Jean Delvare
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=20080122150115.03eed1b6@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=gwc-OVIABD91gjs3uPMLIKxrzw@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