All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Porte <romain.porte@nokia.com>
To: wsa@the-dreams.de
Cc: jdelvare@suse.de, linux-i2c@vger.kernel.org,
	Romain Porte <romain.porte@nokia.com>
Subject: [PATCH v2 3/3] Update man pages for risky_addr
Date: Mon, 29 Jan 2018 13:40:10 +0100	[thread overview]
Message-ID: <20180129124010.4044-4-romain.porte@nokia.com> (raw)
In-Reply-To: <20180129124010.4044-1-romain.porte@nokia.com>

Describe the new -a option in man pages of modified tools.

Signed-off-by: Romain Porte <romain.porte@nokia.com>
---
 tools/i2cdump.8     | 4 ++++
 tools/i2cget.8      | 4 ++++
 tools/i2cset.8      | 4 ++++
 tools/i2ctransfer.8 | 4 ++++
 4 files changed, 16 insertions(+)

diff --git a/tools/i2cdump.8 b/tools/i2cdump.8
index fb7217e..1b98b64 100644
--- a/tools/i2cdump.8
+++ b/tools/i2cdump.8
@@ -7,6 +7,7 @@ i2cdump \- examine I2C registers
 .RB [ -f ]
 .RB [ "-r first-last" ]
 .RB [ -y ]
+.RB [ -a ]
 .I i2cbus
 .I address
 .RI [ "mode " [ "bank " [ bankreg ]]]
@@ -40,6 +41,9 @@ Disable interactive mode. By default, i2cdump will wait for a confirmation
 from the user before messing with the I2C bus. When this flag is used, it
 will perform the operation directly. This is mainly meant to be used in
 scripts.
+.TP
+.B -a
+Allow using risky addresses between 0x00 - 0x02 and 0x78 - 0x7f. Not recommended.
 .PP
 At least two options must be provided to i2cdump. \fIi2cbus\fR indicates the
 number or name of the I2C bus to be scanned. This number should correspond to one
diff --git a/tools/i2cget.8 b/tools/i2cget.8
index a1a1276..26a0ea0 100644
--- a/tools/i2cget.8
+++ b/tools/i2cget.8
@@ -6,6 +6,7 @@ i2cget \- read from I2C/SMBus chip registers
 .B i2cget
 .RB [ -f ]
 .RB [ -y ]
+.RB [ -a ]
 .I i2cbus
 .I chip-address
 .RI [ "data-address " [ mode ]]
@@ -34,6 +35,9 @@ Disable interactive mode. By default, i2cget will wait for a confirmation
 from the user before messing with the I2C bus. When this flag is used, it
 will perform the operation directly. This is mainly meant to be used in
 scripts. Use with caution.
+.TP
+.B -a
+Allow using risky addresses between 0x00 - 0x02 and 0x78 - 0x7f. Not recommended.
 .PP
 There are two required options to i2cget. \fIi2cbus\fR indicates the number
 or name of the I2C bus to be scanned.  This number should correspond to one of
diff --git a/tools/i2cset.8 b/tools/i2cset.8
index 19887bd..4faa061 100644
--- a/tools/i2cset.8
+++ b/tools/i2cset.8
@@ -8,6 +8,7 @@ i2cset \- set I2C registers
 .RB [ -y ]
 .RB [ "-m mask" ]
 .RB [ -r ]
+.RB [ -a ]
 .I i2cbus
 .I chip-address
 .I data-address
@@ -54,6 +55,9 @@ be the case, as neither I2C nor SMBus guarantees this.
 Read back the value right after writing it, and compare the result with the
 value written. This used to be the default behavior. The same limitations
 apply as those of option \fB-m\fR.
+.TP
+.B -a
+Allow using risky addresses between 0x00 - 0x02 and 0x78 - 0x7f. Not recommended.
 .PP
 There are three required options to i2cset. \fIi2cbus\fR indicates the number
 or name of the I2C bus to be scanned.  This number should correspond to one of
diff --git a/tools/i2ctransfer.8 b/tools/i2ctransfer.8
index 0dd43c9..cf8dae7 100644
--- a/tools/i2ctransfer.8
+++ b/tools/i2ctransfer.8
@@ -7,6 +7,7 @@ i2ctransfer \- send user-defined I2C messages in one transfer
 .RB [ -f ]
 .RB [ -y ]
 .RB [ -v ]
+.RB [ -a ]
 .I i2cbus desc
 .RI [ data ]
 .RI [ desc
@@ -61,6 +62,9 @@ It will print infos about all messages sent, i.e. not only for read messages but
 .TP
 .B -V
 Display the version and exit.
+.TP
+.B -a
+Allow using risky addresses between 0x00 - 0x02 and 0x78 - 0x7f. Not recommended.
 
 .SH ARGUMENTS
 .PP
-- 
2.11.0

  parent reply	other threads:[~2018-01-29 12:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 15:02 Patch proposal for risky i2c addresses in i2c-tools Romain Porte
2018-01-05 15:02 ` [PATCH 1/3] Add risky_addr option for i2c tools Romain Porte
2018-01-05 15:02 ` [PATCH 2/3] Update help message for risky_addr option Romain Porte
2018-01-05 15:02 ` [PATCH 3/3] Update man pages for risky_addr Romain Porte
2018-01-26 18:03 ` Patch proposal for risky i2c addresses in i2c-tools Wolfram Sang
2018-01-29 12:26   ` Romain Porte
2018-01-29 13:39     ` Peter Rosin
2018-01-29 12:40 ` New patchset for risky addr, with lower bound support Romain Porte
2018-01-29 12:40   ` [PATCH v2 1/3] Add risky_addr option for i2c tools Romain Porte
2018-01-29 12:40   ` [PATCH v2 2/3] Update help message for risky_addr option Romain Porte
2018-01-29 13:45     ` Peter Rosin
2018-01-29 12:40   ` Romain Porte [this message]
2018-01-29 13:57 ` Patch proposal for risky addr, with updated help messages Romain Porte
2018-01-29 13:57   ` [PATCH v3 1/3] Add risky_addr option for i2c tools Romain Porte
2018-01-29 13:57   ` [PATCH v3 2/3] Update help message for risky_addr option Romain Porte
2018-01-29 13:57   ` [PATCH v3 3/3] Update man pages for risky_addr Romain Porte
2018-02-02 12:45 ` Patch proposal for using all addresses in i2c-tools Romain Porte
2018-02-02 12:45   ` [PATCH v4 1/3] Add all_addrs option for i2c tools Romain Porte
2018-02-02 12:45   ` [PATCH v4 2/3] Update help message for all_addrs option Romain Porte
2018-02-02 12:45   ` [PATCH v4 3/3] Update man pages for all_addrs Romain Porte

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=20180129124010.4044-4-romain.porte@nokia.com \
    --to=romain.porte@nokia.com \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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.