Searched full:responsible (Results 1 – 25 of 926) sorted by relevance
12345678910>>...38
| /Linux-v5.4/net/netlabel/ |
| D | netlabel_addrlist.c | 43 * responsible for calling the rcu_read_[un]lock() functions.
66 * it is returned, otherwise NULL is returned. The caller is responsible for
93 * responsible for calling the rcu_read_[un]lock() functions.
117 * it is returned, otherwise NULL is returned. The caller is responsible for
144 * returned, otherwise a negative value is returned. The caller is responsible
181 * returned, otherwise a negative value is returned. The caller is responsible
217 * Remove the specified IP address entry. The caller is responsible for
235 * entry on success, NULL on failure. The caller is responsible for calling
257 * Remove the specified IP address entry. The caller is responsible for
275 * entry on success, NULL on failure. The caller is responsible for calling
|
| D | netlabel_domainhash.c | 99 * correct bucket number for the domain. The caller is responsible for
131 * which matches any address family entries. The caller is responsible for
166 * entries. The caller is responsible ensuring that the hash table is
202 * the given information. Caller is responsible for holding the necessary
572 * lower level protocol handler (i.e. CIPSO). Caller is responsible for
852 * NULL. The caller is responsible for ensuring that rcu_read_[un]lock() is
871 * responsible for ensuring that rcu_read_[un]lock() is called.
901 * responsible for ensuring that rcu_read_[un]lock() is called.
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | dtv-core.rst | 8 - A bridge driver that is responsible to talk with the bus where the other
15 the hardware responsible for tuning into a digital TV transponder or
|
| /Linux-v5.4/Documentation/networking/ |
| D | devlink-info-versions.rst | 41 Control unit firmware version. This firmware is responsible for house
58 Version of the software responsible for supporting/handling the
|
| D | nfc.txt | 13 The NFC subsystem is responsible for:
18 The subsystem is divided in some parts. The 'core' is responsible for
20 responsible for providing an interface to control operations and low-level
|
| D | cdc_mbim.txt | 92 responsible for negotiating a control message size complying with the
105 The userspace application is responsible for all control message
176 The userspace management application is responsible for adding new
216 The DSS supporting userspace management application is responsible for
|
| /Linux-v5.4/security/ |
| D | inode.c | 101 * is unloaded, you are responsible here). If an error occurs, the
194 * you are responsible here). If an error occurs, the function will return
222 * you are responsible here). If an error occurs, the function will return
254 * you are responsible here). If an error occurs, the function will return
293 * removed; you are responsible here.
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | slimbus.rst | 31 A manager device is responsible for enumeration, configuration, and dynamic
36 Framer device is responsible for clocking the bus, and transmitting frame-sync
49 responsible to select the active-framer for clocking the bus.
|
| /Linux-v5.4/include/uapi/linux/ |
| D | hyperv.h | 191 * is responsible for communicating with the host and responsible for
193 * responsible for data gathering.
218 * is also responsible for binding the key name to the index as well. The
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | cxlflash.rst | 32 responsible for the initialization of the adapter, setting up the
205 This ioctl is responsible for transitioning the LUN to direct
222 This ioctl is responsible for transitioning the LUN to virtual mode
253 This ioctl is responsible for resizing a previously created virtual
272 This ioctl is responsible for releasing a previously obtained
285 This ioctl is responsible for unregistering a context with the
297 This ioctl is responsible for cloning a previously created
|
| /Linux-v5.4/drivers/slimbus/ |
| D | slimbus.h | 93 * responsible for clocking the bus.
94 * Manager is responsible for framer hand-over.
380 * 'Manager device' is responsible for device management, bandwidth
389 * Manager is also responsible for entering (and exiting) low-power-mode
396 * device'. Interface device is responsible for monitoring the bus and
|
| /Linux-v5.4/drivers/staging/unisys/Documentation/ABI/ |
| D | sysfs-platform-visorchipset | 59 responsible for enabling and disabling SR-IOV devices when the
78 responsible for enabling and disabling SR-IOV devices when the
|
| /Linux-v5.4/Documentation/devicetree/bindings/media/ |
| D | qcom,venus.txt | 42 power domain which is responsible for collapsing
80 power domain which is responsible for collapsing
|
| /Linux-v5.4/drivers/hwtracing/coresight/ |
| D | Kconfig | 22 responsible for transporting and collecting the trace data
52 responsible for bridging the gap between the on-chip coresight
|
| /Linux-v5.4/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 27 not be responsible for the errors so resetting them individually is not a
64 or Master driver implementers are responsible for writing valid values in
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-c2c.txt | 207 - pid of the process responsible for the accesses
210 - tid of the process responsible for the accesses
213 - code address responsible for the accesses
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | davinci-vpbe.rst | 47 When connected to an external encoder, vpbe controller is also responsible
57 Responsible for setting outputs provided through internal DACs and also
|
| /Linux-v5.4/drivers/w1/slaves/ |
| D | Kconfig | 118 as the one who is responsible for charging/discharging/monitoring
130 as the one who is responsible for charging/discharging/monitoring
|
| /Linux-v5.4/Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 59 that means that the handler has claimed the device node and is now responsible
61 be responsible for preparing the device node for unregistration in that case.
|
| /Linux-v5.4/Documentation/devicetree/bindings/clock/ |
| D | imx7ulp-clock.txt | 20 The System Clock Generation (SCG) is responsible for clock generation
38 The Peripheral Clock Control (PCC) is responsible for clock selection,
|
| /Linux-v5.4/drivers/soc/sunxi/ |
| D | Kconfig | 11 device is responsible on mapping the SRAM in the sunXi SoCs
|
| /Linux-v5.4/drivers/acpi/dptf/ |
| D | Kconfig | 8 This participant is responsible for exposing platform telemetry:
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/reset/ |
| D | mt6323-poweroff.txt | 3 The power controller which could be found on PMIC is responsible for externally
|
| /Linux-v5.4/drivers/mtd/maps/ |
| D | sc520cdp.c | 37 ** responsible PARxx registers in the SC520's MMCR region. This will
186 ** Find the PARxx registers that are responsible for activating in sc520cdp_setup_par()
202 printk(KERN_NOTICE "Could not find PAR responsible for %s\n", in sc520cdp_setup_par()
|
| /Linux-v5.4/arch/powerpc/kvm/ |
| D | book3s_hv_ras.c | 208 * subcore status. Only primary threads from each subcore is responsible
266 * If resync_req == true, then this thread is responsible to in kvmppc_realmode_hmi_handler()
293 * Check if this thread is responsible to resync TB. in kvmppc_realmode_hmi_handler()
|
12345678910>>...38
