linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Crestez Dan Leonard <cdleonard@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>,
	Crestez Dan Leonard <leonard.crestez@intel.com>,
	linux-i2c@vger.kernel.org
Cc: Jean Delvare <khali@linux-fr.org>
Subject: Re: [PATCH i2c-tools] i2cget: Add support for i2c block data
Date: Sat, 14 May 2016 14:30:02 +0300	[thread overview]
Message-ID: <93dcb82b-b04e-4b3c-1868-2a4fe4a086c8@gmail.com> (raw)
In-Reply-To: <5736738D.3020909@roeck-us.net>

On 05/14/2016 03:38 AM, Guenter Roeck wrote:
> On 05/13/2016 11:54 AM, Crestez Dan Leonard wrote:
>> This adds mode 'i' for I2C_SMBUS_I2C_BLOCK_DATA. This is the same mode
>> letter from i2cdump.
>>
>> Length is optional and defaults to 32 (maximum).
>>
>> The indended use is debugging i2c devices with shell commands.
>>
> How does this differ from the 'i' option of i2cdump ?

Apparently i2cdump doesn't support a range in "i" mode. I considered 
adding a range to i2cdump in all modes but:
- i2cdump code is a more complicated
- Not all devices interpret i2c bulk read as a register range. Reading X 
bytes from register Y can be different from reading registers from X to X+Y.

-- 
Regards,
Leanard

  reply	other threads:[~2016-05-14 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 18:54 [PATCH i2c-tools] i2cget: Add support for i2c block data Crestez Dan Leonard
2016-05-14  0:38 ` Guenter Roeck
2016-05-14 11:30   ` Crestez Dan Leonard [this message]
2016-05-14 15:10     ` Guenter Roeck
2016-05-16 11:39       ` Crestez Dan Leonard

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=93dcb82b-b04e-4b3c-1868-2a4fe4a086c8@gmail.com \
    --to=cdleonard@gmail.com \
    --cc=khali@linux-fr.org \
    --cc=leonard.crestez@intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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).