linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: Kachalov Anton <mouse@mayc.ru>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: i2c: slave support framework improvements
Date: Tue, 16 Aug 2016 14:12:05 +0200	[thread overview]
Message-ID: <20160816121205.GA2846@tetsubishi> (raw)
In-Reply-To: <b2070d79-ab76-a2f5-658f-d24ad0229b04@axentia.se>

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

Hi Peter,

> If you really have a separate device on the bus with the same address
> that you want to add slave support for, then there really is a conflict,
> and the kernel knows it.

We still have a disagreement about "the kernel knows it". The kernel
knows it only in one case, i.e. when you are able to describe all
devices on the bus.

What about this compromise: We keep the current scheme, but print a
warning when the kernel notices a slave device has the same address
which is already claimed by a client driver. This will let most users
know about the conflict but it will not hurt the debugging-via-loopback
case, since people know what they are doing and will happily ignore it.

If you can agree to that, I'll cook up a patch later this week.

Thanks,

   Wolfram


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

  reply	other threads:[~2016-08-16 12:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23  6:51 i2c: slave support framework improvements Kachalov Anton
2016-07-23 19:51 ` Wolfram Sang
2016-07-25  7:02   ` Kachalov Anton
2016-07-25  7:21     ` Wolfram Sang
2016-07-25  7:47       ` Kachalov Anton
2016-07-25  8:28         ` Wolfram Sang
2016-07-25  9:11           ` Kachalov Anton
2016-07-25  9:41             ` Wolfram Sang
2016-07-25 10:00               ` Kachalov Anton
2016-07-26  9:50                 ` Peter Rosin
2016-07-26 16:51                   ` Kachalov Anton
2016-07-28  6:55                     ` Peter Rosin
2016-07-28  8:25                       ` Peter Rosin
2016-07-28 14:39                       ` Kachalov Anton
2016-07-28  7:41                     ` Wolfram Sang
2016-07-28  8:20                       ` Peter Rosin
2016-07-28  8:39                         ` Wolfram Sang
2016-07-28  8:54                           ` Peter Rosin
2016-07-28  9:15                             ` Wolfram Sang
2016-07-28  9:39                               ` Peter Rosin
2016-08-01 10:46                                 ` Wolfram Sang
2016-08-15  8:58                                 ` Peter Rosin
2016-08-16 12:12                                   ` Wolfram Sang [this message]
2016-08-16 13:33                                     ` Peter Rosin
2016-08-16 13:53                                       ` Kachalov Anton
2016-07-28 14:44                       ` Kachalov Anton

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=20160816121205.GA2846@tetsubishi \
    --to=wsa@the-dreams.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mouse@mayc.ru \
    --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 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).