From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH 03/28] nvmem: add a notifier chain Date: Wed, 8 Aug 2018 18:13:53 +0200 Message-ID: <20180808161353.GF7275@lunn.ch> References: <20180808153150.23444-1-brgl@bgdev.pl> <20180808153150.23444-4-brgl@bgdev.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20180808153150.23444-4-brgl@bgdev.pl> Sender: linux-kernel-owner@vger.kernel.org To: Bartosz Golaszewski Cc: Jonathan Corbet , Sekhar Nori , Kevin Hilman , Russell King , Arnd Bergmann , Greg Kroah-Hartman , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Richard Weinberger , Grygorii Strashko , "David S . Miller" , Srinivas Kandagatla , Naren , Mauro Carvalho Chehab , Andrew Morton , Lukas Wunner , Dan Carpenter List-Id: linux-omap@vger.kernel.org On Wed, Aug 08, 2018 at 05:31:25PM +0200, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Add a blocking notifier chain with two events (add and remove) so that > users can get notified about the addition of nvmem devices they're > waiting for. > > We'll use this instead of the at24 setup callback in the mityomapl138 > board file. Hi Bartosz What context is this notifier chain called in? I did something similar using the i2c notifier to try to work around the impending disappearing of the setup callback. But i got lockdep splats, because the notifier was called while some locks were being held, so it was not possible to register other i2c devices. The at24 setup callback is done as part of probe, so no important locks are held. Are any locks held when this notifier chain is called? Thanks Andrew