• Simon Glass's avatar
    dm: core: Don't use pinctrl for the root device · 84d26e29
    Simon Glass authored
    Currently when driver model starts up it finds the root uclass and the
    pinctrl uclass. This is because even the root node handles pinctrl
    processing.
    
    But this is not useful. The root node is not a real hardware device so
    cannot require any particular pinmux settings. Also it means that the
    memory leak tests fails, since they end up freeing more memory than
    they allocate: the marker it set after the root device and pinctrl
    uclass are allocated, and later once the pinctrl uclass is freed the memory
    used by driver model is less than when the marker was set.
    
    If a platform needs 'core' pin mulitplex settings it can do this with
    a driver that is probed on start-up. It would be an abuse of the root node
    to use this for pinctrl.
    
    To avoid this problem, only process pinctrl settings for non-root nodes.
    Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
    84d26e29
Name
Last commit
Last update
..
Kconfig Loading commit data...
Makefile Loading commit data...
device-remove.c Loading commit data...
device.c Loading commit data...
devres.c Loading commit data...
dump.c Loading commit data...
lists.c Loading commit data...
regmap.c Loading commit data...
root.c Loading commit data...
simple-bus.c Loading commit data...
syscon-uclass.c Loading commit data...
uclass.c Loading commit data...
util.c Loading commit data...