All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: Adrian Fiergolski <adrian.fiergolski@cern.ch>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] i2c: add i2c_get_device_id() to get the standard i2c device id
Date: Mon, 5 Mar 2018 17:27:38 +0100	[thread overview]
Message-ID: <20180305162738.kkbe3qlt2xbzabl6@ninjato> (raw)
In-Reply-To: <b624a0c7-ffe2-245b-ff9e-ca9d10063715@axentia.se>

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


> ..._TEN should definitely be cleared.
> ..._SLAVE will probably be cleared anyway.
> ..._HOST_NOTIFY, ..._WAKE and ..._SCCB I don't know about?

Not relevant for device_id reading.

> Are there others? The bits aren't that densely populated which makes
> me worry that I'm missing something...

Historic reasons, there are no more.


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

  reply	other threads:[~2018-03-05 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 11:36 [RFC PATCH 0/2] check I2C device id for pca984x chips Peter Rosin
2018-01-22 11:36 ` [RFC PATCH 1/2] i2c: add i2c_get_device_id() to get the standard i2c device id Peter Rosin
2018-03-04 21:47   ` Peter Rosin
2018-03-05 15:51   ` Wolfram Sang
2018-03-05 16:06     ` Peter Rosin
2018-03-05 16:27       ` Wolfram Sang [this message]
2018-01-22 11:36 ` [RFC PATCH 2/2] i2c: mux: pca954x: verify the device id of the pca984x chips Peter Rosin
2018-03-05 15:53   ` Wolfram Sang
2018-03-05 15:55     ` Peter Rosin
2018-03-05 16:29       ` Wolfram Sang
2018-01-26 16:33 ` [RFC PATCH 0/2] check I2C device id for " Adrian Fiergolski
2018-01-26 16:33   ` Adrian Fiergolski
2018-01-27  8:37   ` Peter Rosin
2018-01-29 17:38     ` Adrian Fiergolski
2018-01-29 17:38       ` Adrian Fiergolski
2018-02-01 14:41       ` Peter Rosin

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=20180305162738.kkbe3qlt2xbzabl6@ninjato \
    --to=wsa@the-dreams.de \
    --cc=adrian.fiergolski@cern.ch \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    /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.