From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752732AbbF2OUO (ORCPT ); Mon, 29 Jun 2015 10:20:14 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:60616 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753114AbbF2OUI (ORCPT ); Mon, 29 Jun 2015 10:20:08 -0400 Date: Mon, 29 Jun 2015 15:19:40 +0100 From: Mark Brown To: Lars-Peter Clausen Cc: Nicolas Boichat , Arjan van de Ven , Mauro Carvalho Chehab , Antti Palosaari , Ingo Molnar , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Bard Liao , Oder Chiou , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org, Anatol Pomozov Message-ID: <20150629141940.GD11162@sirena.org.uk> References: <1435224904-35517-1-git-send-email-drinkcat@chromium.org> <558C0067.2000401@linux.intel.com> <558C1824.8020204@metafoo.de> <20150625153325.GR14071@sirena.org.uk> <558C229D.4090409@metafoo.de> <20150625160817.GT14071@sirena.org.uk> <5591414D.6080802@metafoo.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qGV0fN9tzfkG3CxV" Content-Disposition: inline In-Reply-To: <5591414D.6080802@metafoo.de> X-Cookie: Stay together, drag each other down. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [RFC PATCH 1/2] regmap: add configurable lock class key for lockdep 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 --qGV0fN9tzfkG3CxV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jun 29, 2015 at 02:59:57PM +0200, Lars-Peter Clausen wrote: > Maybe we are just over-thinking this and should just add one key to each > regmap instance. That solves the issue without requiring the any user > interaction. The only downside is that it might impact the performance of > lockdep and uses quite a few lock classes. Its probably manageable right now > but could grow into a problem as regmap adoption further progresses. But > maybe we can leave the hard work of figuring a better solution to our future > selves. I thought the issue with that was that all lockdep classes need to be allocated statically? If we can just do something that scales with regmap instances I'm not sure there's a big problem, even if adoption increases we're talking about something that scales with the number of devices in the system rather than the number of drivers using the API which should be a lot more manageable. --qGV0fN9tzfkG3CxV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVkVP8AAoJECTWi3JdVIfQP1cH/RzAfNsfVMrvAPuD8BmIxRJi 7ai6y5Ua6/FeyjWjaKOaX2YWUfQlXtxSDR+vaWOhtvgoPS8XgYp6pRfjVoMUC70B 8jybTlM3n5Ax9cK+vYsPWIfZ4pfqZ/EiAAR8Y7g4q4aHmHNISTabEtI8XZngQ9hw 33fxB3YbvLsEMX6+TVwhtV1JFMwlb4QfciNFHFqZYVy5dGzLvrxSNFgzUiqrHhij ZGH9uaRrAQHFkpBO3b/aO3yypKSJdTVy3MJNg3lLhQqrIt0Lkvi2c9xNDKzLAtMT I1V/cebF5aibvwrvG0b2NUSco0/r9ya3LKbfvCYEwRQ0DG2zOKX7ecn3j+0KVp8= =vNSx -----END PGP SIGNATURE----- --qGV0fN9tzfkG3CxV--