Searched refs:resolver (Results 1 – 18 of 18) sorted by relevance
5 Device Tree resolver, residing in drivers/of/resolver.c7 How the resolver works10 The resolver is given as an input an arbitrary tree compiled with the14 In sequence the resolver works by the following steps:
11 Say yes here to build support for Analog Devices spi resolver22 Say yes here to build support for Analog Devices spi resolver
13 obj-y += resolver/
15 source "drivers/staging/iio/resolver/Kconfig"
31 functions resolver. This function receives a pointer to its custom context37 kernel functions resolver. The _tep_ argument is trace event parser context.39 resolver is used by the APIs _tep_find_function()_,44 resolver to the default function. The _tep_ argument is trace event parser
89 Functions resolver:
12 Say yes here to build support for Analog Devices spi resolver
14 obj-$(CONFIG_OF_RESOLVE) += resolver.o
38 obj-y += resolver/
95 source "drivers/iio/resolver/Kconfig"
20 helper "/sbin/dns.resolver" via /etc/request-key.conf.
25 resolver@0 {
179 bool "Use the legacy NFS DNS resolver"184 resolver script.
19 The DNS resolver module provides a way for kernel services to make DNS queries
57 The DNS resolver
517 struct func_resolver *resolver = malloc(sizeof(*resolver)); in tep_set_function_resolver() local519 if (resolver == NULL) in tep_set_function_resolver()522 resolver->func = func; in tep_set_function_resolver()523 resolver->priv = priv; in tep_set_function_resolver()526 tep->func_resolver = resolver; in tep_set_function_resolver()
562 DNS resolver cache keyring is an example of this.
12093 F: drivers/of/resolver.c
