From: Guenter Roeck <groeck@juniper.net>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Danielle Costantino <danielle.costantino@gmail.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Jiri Kosina <jkosina@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Rajat Jain <rajatjain@juniper.net>
Subject: Re: Fwd: [Proposal] PM sleep children of inactive I2C bus segments off Masters in multi-master systems
Date: Wed, 1 Oct 2014 14:16:57 -0700 [thread overview]
Message-ID: <20141001211657.GA7904@svl-evodev-groeck.juniper.net> (raw)
In-Reply-To: <20141001211046.GA2368@katana>
On Wed, Oct 01, 2014 at 11:10:47PM +0200, Wolfram Sang wrote:
>
> > Maybe you can find an error code which with some level of confidence
> > reflects "lost mastership". Then you can implement whatever makes sense
> > for your use case in your user space application(s).
>
> We have a documented fault code for ArbitrationLost and that is -EAGAIN
> (see Documentation/i2c/fault-codes). If a driver does use something
> else, patches are very welcome.
>
> Other than that, I find this thread very confusing. Of course can
> another master modify the clients, this is what multi-master is all
> about, no?
>
That is the point I was trying to make in one of my earlier replies.
Guenter
next prev parent reply other threads:[~2014-10-01 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAVjN7dwS62EKMnuZc_P1UjkbRVk6RXqJ91GwWZ96bbY5Ct-rg@mail.gmail.com>
2014-10-01 18:39 ` Fwd: [Proposal] PM sleep children of inactive I2C bus segments off Masters in multi-master systems Danielle Costantino
2014-10-01 18:43 ` Guenter Roeck
2014-10-01 18:44 ` Danielle Costantino
2014-10-01 19:41 ` Guenter Roeck
2014-10-01 20:03 ` Danielle Costantino
2014-10-01 20:20 ` Guenter Roeck
2014-10-01 20:32 ` Danielle Costantino
2014-10-01 20:43 ` Guenter Roeck
2014-10-01 20:49 ` Danielle Costantino
2014-10-01 21:10 ` Wolfram Sang
2014-10-01 21:16 ` Guenter Roeck [this message]
2014-10-01 21:21 ` 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=20141001211657.GA7904@svl-evodev-groeck.juniper.net \
--to=groeck@juniper.net \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=danielle.costantino@gmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rajatjain@juniper.net \
--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 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).