[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAVjN7edpkXYMHBm+wLegA_pc0hnm_YZf_z=Ni3h=EbDTmfegQ@mail.gmail.com>
Date: Wed, 1 Oct 2014 11:44:59 -0700
From: Danielle Costantino <danielle.costantino@...il.com>
To: Guenter Roeck <groeck@...iper.net>
Cc: linux-i2c <linux-i2c@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Jiri Kosina <jkosina@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
Rajat Jain <rajatjain@...iper.net>
Subject: Re: Fwd: [Proposal] PM sleep children of inactive I2C bus segments
off Masters in multi-master systems
Re-sending Proposal:
Currently I2C mux devices that support multiple master arbitration are
the i2c-mux-pca9541 and i2c-arb-gpio-challenge drivers. I propose to
add the ability to configure an interrupt pin from the Master Selector
device to indicate that bus ownership has been lost. Once the device
loses ownership, all of its children should enter a pm sleep mode (as
you can't talk to them at this point) until master-ship has been
reacquired.
This has come up as an issue when the master loses control over a bus
the return code of all transactions to its lave devices is EIO (not
very helpful).
Any comments would be appreciated, I am just looking if there is
interest in this.
Thanks,
On Wed, Oct 1, 2014 at 11:43 AM, Guenter Roeck <groeck@...iper.net> wrote:
> On Wed, Oct 01, 2014 at 11:39:49AM -0700, Danielle Costantino wrote:
>> added proper mailing lists...I hope
>>
>
> Hi Danielle,
>
> I don't see the actual proposal, and I don't find anything on the web
> either when looking for the headline :-(.
>
> Guenter
--
- Danielle Costantino
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists