[lkml]   [2017]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] regmap: add regmap_debugfs_exit as devres action
On Mon, May 15, 2017 at 01:08:27AM -0700, Stefan Agner wrote:

> Instead of manually cleanup regmap_debugfs_exit, use devres action
> to do the cleanup. This also works for external users of
> regmap_attach_dev.

Why? It's also not clear to me that this will work if something creates
a regmap, frees it and then creates another one on the same device
without a reprobe. There have been a few devices that did that as part
of enumeration of the device, they created a simple regmap to read ID
registers then replaced it with a more complete description of the
actual device they found.

> This fixes warnings when reloading certain drivers making use of
> regmap_debugfs_exit:
> imx7d-pinctrl 30330000.iomuxc: Failed to create debugfs directory

How? (and this should be in the changelog.)

> @@ -1215,7 +1216,6 @@ void regmap_exit(struct regmap *map)
> struct regmap_async *async;
> regcache_exit(map);
> - regmap_debugfs_exit(map);
> regmap_range_exit(map);
> if (map->bus && map->bus->free_context)
> map->bus->free_context(map->bus_context);

This isn't obviously correct, it reorders the cleanup such that the
debugfs entries will only get removed when the device is removed which
means that the debugfs entries will be hanging around after the regmap
has been deinstantiated. In the common case where it too was allocated
as a managed resource that'll work out but if for some reason it wasn't
allocated as as managed resource then the debugfs entry will be
dealocated after the regmap.

We should also be doing the debugfs cleanup before the regcache cleanup
but that's a separate and preexisting bug.
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2017-05-19 18:48    [W:0.025 / U:12.328 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site