Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753304AbaAPRUx (ORCPT ); Thu, 16 Jan 2014 12:20:53 -0500 Received: from fw-tnat.austin.arm.com ([217.140.110.23]:45336 "EHLO collaborate-mta1.arm.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753153AbaAPRUP (ORCPT ); Thu, 16 Jan 2014 12:20:15 -0500 Message-ID: <1389892813.3496.82.camel@hornet> Subject: Re: [RFC 06/18] regmap: Formalise use of non-bus context From: Pawel Moll To: Grant Likely Cc: Mark Brown , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Samuel Ortiz , Arnd Bergmann , Jon Medhurst , "arm@kernel.org" , Olof Johansson , Greg Kroah-Hartman Date: Thu, 16 Jan 2014 17:20:13 +0000 In-Reply-To: <20140116170954.C3CBCC40973@trevor.secretlab.ca> References: <1387815830-8794-1-git-send-email-pawel.moll@arm.com> < 1387815830-8794-7-git-send-email-pawel.moll@arm.com> <20131224124538. GZ30815@sirena.org.uk> <1389272911.23721.49.camel@hornet> <20140116170954.C3CBCC40973@trevor.secretlab.ca> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2014-01-16 at 17:09 +0000, Grant Likely wrote: > > First of all, it's just a generalization of the free_context already > > existing in regmap_bus (and used by regmap-mmio). And in case of this > > series it is being used to release extra resource added allocated for a > > "busless" regmap_config. Briefly, I'm using devm_regmap_init() to > > "attach" a custom regmap configuration to a device when it is being > > created (which is then dev_get_regmap()-ed in the driver, as you saw in > > the regulator patch) and its context is a pointer to kzallocated data. > > free_context is used to release it when devm resource is being removed. > > Have you thought through all the implications here? What you've > described effectively changes the devm model. devm operates under the > assumption that devm data only exists between probe() and remove() time. > If you 'preload' devm data then the preloaded data will get discarded at > remove() time which breaks if the driver is remove and probed again at > runtime. Uh. Right, you're correct, I've missed that (obvious) fact :-( I will get the drivers back to "vexpress_regmap_init()" model or try to find a way of "attaching" a regmap pointer(s?) to a struct device. If it makes sense at all... Paweł -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/