linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org,
	Magnus Damm <magnus.damm@gmail.com>,
	Simon Horman <horms@verge.net.au>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] i2c-tools: i2ctransfer: add new tool
Date: Fri, 8 May 2015 16:38:26 +0200	[thread overview]
Message-ID: <20150508143826.GA1513@katana> (raw)
In-Reply-To: <20150508105401.223a8598@endymion.delvare>

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]


> Having slept over it, I came up with a 3rd proposal:
> 
> # i2ctransfer 0 w0x11@0x50 0xc0 0xbd= r1@0x51
> 
> That is, combining the slave address, direction and length into a
> single parameter. The advantage is that this is all more explicit and
> the risk of mixing up values is close to zero. Whether it is more or
> less readable than the previous proposals is probably a matter of
> taste. Also I suspect it would make the parsing and state machine more
> simple, but that's only a nice side effect.
> 
> Wolfram (and others), please tell me what you think. I am not trying to
> force my views here, just suggesting alternatives for your
> consideration.

I liked your proposal, so thanks for this input. I agree that the risk
of mixing something up is high, I was okay with the printout of the
messages to be sent, but a better syntax is very welcome, too. I need to
think about the flags a little bit, though. Although this isn't
implemented yet, PEC and 10-bit flags might be added in the future?
Handling R/W as "just another" flag made this option extremly simple.
But we probably can work something out.

So much for the quick response, I'll have a closer look later.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-05-08 14:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 16:16 [RFC] i2c-tools: i2ctransfer: add new tool Wolfram Sang
     [not found] ` <1425053816-19804-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-04-20 17:36   ` Wolfram Sang
2015-04-21  5:25     ` Jean Delvare
     [not found]       ` <20150421072551.326bb4b7-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2015-04-21  7:06         ` Wolfram Sang
2015-05-07 20:08 ` Jean Delvare
2015-05-08  8:54   ` Jean Delvare
2015-05-08 14:38     ` Wolfram Sang [this message]
2015-05-08 21:40       ` Jean Delvare
2015-05-09  6:50         ` Wolfram Sang
     [not found]     ` <20150508105401.223a8598-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2015-05-08 15:28       ` Randy Grunwell
2015-05-08 18:28         ` Uwe Kleine-König
2015-05-08 20:58         ` Jean Delvare
     [not found]   ` <20150507220812.3776bb83-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2015-05-09  7:09     ` Wolfram Sang

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=20150508143826.GA1513@katana \
    --to=wsa@the-dreams.de \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=jdelvare@suse.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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).