From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [PATCH v2 0/4] gpio: fix an incorrect lockdep warning Date: Sat, 17 Sep 2016 03:19:52 +0200 Message-ID: <20160917011952.GK5016@twins.programming.kicks-ass.net> References: <1474041765-17818-1-git-send-email-bgolaszewski@baylibre.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1474041765-17818-1-git-send-email-bgolaszewski@baylibre.com> Sender: linux-gpio-owner@vger.kernel.org To: Bartosz Golaszewski Cc: Linus Walleij , Alexandre Courbot , Andy Shevchenko , Vignesh R , Yong Li , Geert Uytterhoeven , Ingo Molnar , Wolfram Sang , Peter Rosin , linux-i2c , linux-gpio , LKML List-Id: linux-i2c@vger.kernel.org On Fri, Sep 16, 2016 at 06:02:41PM +0200, Bartosz Golaszewski wrote: > If an I2C GPIO multiplexer is driven by a GPIO provided by an expander > when there's a second expander using the same device driver on one of > the I2C bus segments, lockdep prints a deadlock warning when trying to > set the direction or the value of the GPIOs provided by the second > expander. > > This series exports an already existing function from i2c-core as > public API and reuses it in pca953x to pass a correct lock subclass > to lockdep. Acked-by: Peter Zijlstra (Intel) > Note: if this series gets merged, I'll prepare follow-up patches for > other expanders for which a similar problem could potentially occur. We can't push this annotation into the i2c core, can we? Since the mutex is in driver specific code, not more generic...