[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150114181526.GA2892@pathfinder>
Date: Wed, 14 Jan 2015 10:15:26 -0800
From: "David E. Box" <david.e.box@...ux.intel.com>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Jarkko Nikula <jarkko.nikula@...ux.intel.com>, jdelvare@...e.de,
arnd@...db.de, maxime.ripard@...e-electrons.com,
dianders@...omium.org, u.kleine-koenig@...gutronix.de,
laurent.pinchart+renesas@...asonboard.com,
boris.brezillon@...e-electrons.com, andrew@...n.ch,
sjg@...omium.org, markus.mayer@...aro.org,
jacob.jun.pan@...ux.intel.com, max.schwarz@...ine.de,
mika.westerberg@...ux.intel.com, skuribay@...ox.com,
Romain.Baeriswyl@...lis.com, wenkai.du@...el.com,
chiau.ee.chew@...el.com, alan@...ux.intel.com,
linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org
Subject: Re: [PATCH V3 1/2] i2c-designware: Add i2c bus locking support
Hi,
Expect something tonight should the latest tests run okay. I needed to include
an EPROBE_DEFER to address the unavailibity of the pci driver needed in order to
request the lock during probe of the i2c device. This due to the lock now being
requested during probe because of the hang.
Dave
On Tue, Jan 13, 2015 at 10:48:33AM +0100, Wolfram Sang wrote:
> Hi Dave,
>
> > Timely reply. Around i2c_dw_init(), yes. I just discovered this as the source
> > of a recent hang that's occuring in the loop in __i2c_dw_enable().
> > The hange occurs very infrequently and only, so far, when not built in. A
> > block around i2c_dw_disable_int() would make sense as well as a precaution.
>
> Any news on this or on a V4 of this series?
>
> Thanks,
>
> Wolfram
>
--
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