[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140708145249.GX30458@sirena.org.uk>
Date: Tue, 8 Jul 2014 16:52:49 +0200
From: Mark Brown <broonie@...nel.org>
To: Julia Lawall <julia.lawall@...6.fr>
Cc: Fabio Estevam <festevam@...il.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
Takashi Iwai <tiwai@...e.de>,
linux-kernel <linux-kernel@...r.kernel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Himangi Saraogi <himangi774@...il.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: sgtl5000: Use devm_ functions
On Tue, Jul 08, 2014 at 10:15:20AM +0200, Julia Lawall wrote:
> On Tue, 8 Jul 2014, Mark Brown wrote:
> > It should be fairly clear given what they do I'd have thought - the
> > devm_ functions tie the deallocation of a resource to the unbinding of
> > a driver from a device so they can only be used to replace things that
> > get cleaned up in a device model unbind path. There's not usually a
> > great deal of indirection going on in those.
> It is completely clear what they do. What is not clear is what device
> libraries are set up to call the freeing functions at what point. For
> example, I know that that platform drivers are set up for this, but once I
> tried to find the lines of code that would justify that, but I could not.
> Perhaps I was not patient enough or missed something.
All devices do this - it's done as part of the driver model core code so
there is no need for individual buses to do anything.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists