From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753714AbbHGONM (ORCPT ); Fri, 7 Aug 2015 10:13:12 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:33127 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753323AbbHGONL (ORCPT ); Fri, 7 Aug 2015 10:13:11 -0400 Date: Fri, 7 Aug 2015 15:12:58 +0100 From: Mark Brown To: Srinivas Kandagatla Cc: Liam Girdwood , linux-kernel@vger.kernel.org Message-ID: <20150807141258.GH10301@sirena.org.uk> References: <1438790528-4435-1-git-send-email-srinivas.kandagatla@linaro.org> <20150806094329.GQ20873@sirena.org.uk> <55C33E89.2060501@linaro.org> <20150806114025.GW20873@sirena.org.uk> <55C349C2.1020009@linaro.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="uAgJxtfIS94j9H4T" Content-Disposition: inline In-Reply-To: <55C349C2.1020009@linaro.org> X-Cookie: Biggest security gap -- an open mouth. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 146.198.193.35 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [RFC PATCH] regulator: Fix recursive mutex lockdep warning X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --uAgJxtfIS94j9H4T Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Aug 06, 2015 at 12:49:22PM +0100, Srinivas Kandagatla wrote: > On 06/08/15 12:40, Mark Brown wrote: > >>lock_class per regulator makes more sense, I will try to cookup an RFC > >>patch. > >There's an issue there with all lock classes needing to be statically > >allocated which makes things a bit tricky. > Yes, just realized it with "BUG: key edadc07c not in .data!" Yeah, it's a bit nasty. We went round this a bit with regmap and unfortunately didn't manage to come up with any great ideas. The regmap workaround just landed in my tree, I'm not sure it's really great for regulator though. --uAgJxtfIS94j9H4T Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVxLzpAAoJECTWi3JdVIfQCiwH/iniHAcAzgcXVe0p9ELbOo13 dIQOh9VDYofSjTegu0zOTkP9X9xlOafay+F04T+zgDyPoYXc/KWTQCM6c4uijRIL NVbJRCvFBrNgjYZmeE9tMg3Sil/+c0R/sClED3j1D5y0aG/o96N6JK9qMw4CUzEY OM8wo0WidYsS2e4s+Pu6dBNsAhqtBVRxHkLvo7hNy3MVeyy97xRNw40wnBARgUUo Q0YIzaNVkAnfDSmFwDyCqXOhGmAs9HE22VA0RfrIMde4ovhR++RFR/ifLXJbLOB3 THvgfpib/ZdFp7fFEmS104PRWM8P6ONyxAZOKO+uo4sWSDbP4u6o5a3sbmQRUhA= =2xne -----END PGP SIGNATURE----- --uAgJxtfIS94j9H4T--