Messages in this thread | | | From | Linus Walleij <> | Date | Sat, 25 Jun 2022 20:09:39 +0200 | Subject | Re: Default async probing for DT based systems |
| |
On Fri, Jun 17, 2022 at 8:01 PM Saravana Kannan <saravanak@google.com> wrote: > On Fri, Jun 17, 2022 at 1:21 AM Linus Walleij <linus.walleij@linaro.org> wrote: > > On Thu, Jun 16, 2022 at 5:25 AM Saravana Kannan <saravanak@google.com> wrote: > > > > > Since fw_devlink=on is the default behavior and fw_devlink understands > > > approximately 24 DT bindings, > > > > How can I see which these are, in the kernel tree? > > device/of/property.c has an array of these binding handling functions > in of_supplier_bindings[]. > > Most of the functions there are created using DEFINE_SIMPLE_PROP() or > DEFINE_SUFFIX_PROP() that's also in the same file.
Thanks!
We already have some device links in pin control, it's an opt-in for drivers, used e.g in drivers/pinctrl/stm32/pinctrl-stm32.c where you see pctl->pctl_desc.link_consumers = true; how does that play with this? Double device links at different levels?
I had a patch to just enforce device links on all pinctrl resources, but it seemed over the top: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/commit/?h=consumer-link-enforce&id=73441cf773ed91bff0e7f66614d391b2514188bf
Yours, Linus Walleij
| |