From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [RFC 6/6] bus: Add support for Tegra NOR controller To: Mirza Krak References: <1468935397-11926-1-git-send-email-mirza.krak@gmail.com> <1468935397-11926-7-git-send-email-mirza.krak@gmail.com> CC: Stephen Warren , Thierry Reding , Alexandre Courbot , , Prashant Gaikwad , "Michael Turquette" , , , , , , , , , , Kumar Gala , From: Jon Hunter Message-ID: <7f558131-60c7-22e2-2b2e-93d4b405a2db@nvidia.com> Date: Mon, 25 Jul 2016 09:19:12 +0100 MIME-Version: 1.0 In-Reply-To: Return-Path: jonathanh@nvidia.com Content-Type: text/plain; charset="utf-8" List-ID: On 22/07/16 20:18, Mirza Krak wrote: > 2016-07-22 11:38 GMT+02:00 Jon Hunter : >>>> The driver should have a remove function given that we can build as a >>>> module. >>> >>> At the moment I do not know what we would do in a remove function and >>> hence me not adding one. >> >> Should just be the inverse of the probe (although there is no inverse >> for the parsing DT bit). If you don't wish to add a remove, that is >> fine, but make the driver a 'bool' and not 'tristate' in the Kconfig so >> it cannot be configured as a module. > > I understand the concept of a remove function, but I use devm_ calls > for all resources. These should be handled by the device core on a > driver detach? There is one clock that needs to be disabled in the remove. Cheers Jon -- nvpublic