7dc5b18ff7
In case of multiple kernel module instances using the same dpll device: if only one registers dpll device, then only that one can register directly connected pins with a dpll device. When unregistered parent is responsible for determining if the muxed pin can be registered with it or not, the drivers need to be loaded in serialized order to work correctly - first the driver instance which registers the direct pins needs to be loaded, then the other instances could register muxed type pins. Allow registration of a pin with a parent even if the parent was not yet registered, thus allow ability for unserialized driver instance load order. Do not WARN_ON notification for unregistered pin, which can be invoked for described case, instead just return error. Fixes: |
||
---|---|---|
.. | ||
dpll_core.c | ||
dpll_core.h | ||
dpll_netlink.c | ||
dpll_netlink.h | ||
dpll_nl.c | ||
dpll_nl.h | ||
Kconfig | ||
Makefile |