public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Cc: linux-i2c@vger.kernel.org, Richard Weinberger <richard@sigma-star.at>
Subject: Re: Sensor with 7 bit address above 0x77
Date: Mon, 27 Jun 2016 14:13:20 +0200	[thread overview]
Message-ID: <20160627121319.GA1648@katana> (raw)
In-Reply-To: <17002e23-eaf4-125c-9402-4def2bf13e51@sigma-star.at>

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


> Both programs mention the limitations in their manpages but give *no explanation* on why they
> exist or where those special values came from.

That could be added to them. But the first thing to look for such
information is still the I2C specification which has a section about
reserved addresses.

> The comment above the line states that addresses 0x78-0x7b are used for 10-bit slave
> addressing. The documentation on 10-bit slave addressing (Documentation/i2c/ten-bit-addresses)
> says "...The leading 0xa (= 10) represents the 10 bit mode...". Wouldn't such an address
> on the bus be quite problematic as 0xA has a leading 1 bit (read/write select?).

Please read the above specification to understand how 10 bit addresses
are transferred over the wire. I think reading it will answer most of
your questions.

> Is there a specific reason I can override i2cdetect but not i2cdump?

Probably not. More likely, nobody needed it until now. Which is
understandable since the device you have has to be considered broken
regarding the I2C standard. But I think patches adding that could be
acceptable. Jean has the last word on this.


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

  reply	other threads:[~2016-06-27 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 11:39 Sensor with 7 bit address above 0x77 David Oberhollenzer
2016-06-27 12:13 ` Wolfram Sang [this message]
2016-06-27 13:38   ` David Oberhollenzer
2016-06-27 15:46     ` 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=20160627121319.GA1648@katana \
    --to=wsa@the-dreams.de \
    --cc=david.oberhollenzer@sigma-star.at \
    --cc=linux-i2c@vger.kernel.org \
    --cc=richard@sigma-star.at \
    /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