Home
last modified time | relevance | path

Searched full:particular (Results 1 – 25 of 9782) sorted by relevance

12345678910>>...392

/kernel/linux/linux-5.10/kernel/sched/
Dcompletion.c18 * @x: holds the state of this particular completion
43 * @x: holds the state of this particular completion
45 * This will wake up all threads waiting on this particular completion event.
128 * @x: holds the state of this particular completion
144 * @x: holds the state of this particular completion
163 * @x: holds the state of this particular completion
177 * @x: holds the state of this particular completion
197 * @x: holds the state of this particular completion
215 * @x: holds the state of this particular completion
234 * @x: holds the state of this particular completion
[all …]
/kernel/linux/linux-5.10/drivers/leds/
DTODO39 about LED color. In particular, there's no way to make LED "white".
60 In particular, LED names are still a mess (see above) and utility
70 In future, it would be good to be able to set rgb led to particular
73 And probably user-friendly interface to access LEDs for particular
/kernel/linux/linux-5.10/drivers/staging/comedi/drivers/
Dni_routes.h17 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
46 * struct ni_device_routes - List of all src->dest sets for a particular device.
64 * such routes for that particular device.
131 * this particular device.
142 * ni_lookup_route_register() - Look up a register value for a particular route
144 * the particular device.
252 * particular valid NI signal/terminal route.
300 * the destination on the particular device.
/kernel/linux/linux-5.10/drivers/input/rmi4/
Drmi_bus.h22 * function for a particular device (basically, a driver for that RMI4 function)
26 * @dev: The device associated with this particular function.
56 * struct rmi_function_handler - driver routines for a particular RMI function.
68 * @suspend: Should perform any required operations to suspend the particular
70 * @resume: Should perform any required operations to resume the particular
/kernel/linux/linux-5.10/Documentation/driver-api/phy/
Dsamsung-usb2.rst11 the differences were minor and were found in particular bits of the
28 struct of_device_id definitions for particular SoCs.
33 structures that describe particular SoCs.
129 particular SoC is compiled in the driver. In case of Exynos 4210 four
/kernel/linux/linux-5.10/Documentation/driver-api/driver-model/
Dclass.rst15 implementation of that programming interface for a particular device on
16 a particular bus.
68 drivers of that particular class. To access all of the devices in the
146 particular class type. Device interfaces describe these mechanisms.
Dbus.rst50 determine if a particular driver supports a particular device by
52 particular device, without sacrificing bus-specific functionality or
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Dvoltage.c63 * voltdm_scale() - API to scale voltage of a particular voltage domain.
68 * for a particular voltage domain during DVFS.
115 * voltdm_reset() - Resets the voltage of a particular voltage domain
144 * particular voltage domain.
146 * @volt_data: the voltage table for the particular vdd which is to be
167 * particular voltage
/kernel/linux/linux-5.10/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt47 no longer built specifically for a particular group in the defense or
78 collection of systems which agree on the meaning of particular values
118 should assume that the DOI identifier field is not aligned on any particular
151 all tags, as well as fields within a tag, are not aligned on any particular
475 all datagrams that may exit a particular network interface port. All
482 all datagrams that may exit a particular network interface port. All
490 particular network interface port. All CIPSO labels within datagrams
496 particular IP network address. All CIPSO labels within datagrams destined
497 for the particular IP network MUST use the specified DOI identifier. All
502 particular IP host address. All CIPSO labels within datagrams destined for
[all …]
/kernel/liteos_a/kernel/include/
Dlos_ld_elflib.h21 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
75 * This API is used to load a shared object file under a particular module file path.
96 * This API is used to load an object file under a particular module file path.
117 * This API is used to unload a module with a particular module handle.
158 …* This API is used to search for the address of a symbol according to a particular module handle a…
/kernel/linux/linux-5.10/include/linux/device/
Dclass.h122 * class_find_device_by_name - device iterator for locating a particular device
134 * class_find_device_by_of_node : device iterator for locating a particular device
146 * class_find_device_by_fwnode : device iterator for locating a particular device
159 * class_find_device_by_devt : device iterator for locating a particular device
173 * class_find_device_by_acpi_dev : device iterator for locating a particular
Ddriver.h163 * driver_find_device_by_name - device iterator for locating a particular device
175 * driver_find_device_by_of_node- device iterator for locating a particular device
188 * driver_find_device_by_fwnode- device iterator for locating a particular device
201 * driver_find_device_by_devt- device iterator for locating a particular device
220 * driver_find_device_by_acpi_dev : device iterator for locating a particular
Dbus.h166 * bus_find_device_by_name - device iterator for locating a particular device
180 * bus_find_device_by_of_node : device iterator for locating a particular device
192 * bus_find_device_by_fwnode : device iterator for locating a particular device
204 * bus_find_device_by_devt : device iterator for locating a particular device
231 * bus_find_device_by_acpi_dev : device iterator for locating a particular device
/kernel/linux/linux-5.10/security/integrity/platform_certs/
Dkeyring_handler.h23 * Return the handler for particular signature list types found in the db.
28 * Return the handler for particular signature list types found in the dbx.
/kernel/linux/linux-5.10/drivers/staging/comedi/drivers/ni_routing/
Dni_route_values.h17 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
31 * used as the source of one particular trigger or another (using
77 * struct family_route_values - Register values for all routes for a particular
Dni_route_values.c17 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
25 * used as the source of one particular trigger or another (using
/kernel/linux/linux-5.10/drivers/crypto/qat/qat_common/
Dadf_pf2vf_msg.h10 * register associated with that particular VF.
13 * The bottom half is for PF->VF messages. In particular when the first
16 * The top half is for VF->PF messages. In particular when the first bit
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-event_source-devices-hv_24x75 that go into perf_event_attr.config for a particular pmu.
82 Provides the description of a particular event as provided by
93 Provides the "long" description of a particular event as
Dsysfs-class-bdi39 percentage of the write-back cache to a particular device.
44 Allows limiting a particular device to use not more than the
/kernel/linux/linux-5.10/drivers/staging/comedi/drivers/ni_routing/tools/
Dconvert_csv_to_c.py141 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
173 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
211 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
317 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
325 * used as the source of one particular trigger or another (using
355 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
393 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
401 * of one particular trigger or another (using *_src=TRIG_EXT).
/kernel/linux/linux-5.10/drivers/mtd/parsers/
DKconfig32 for your particular device. It won't happen automatically. The
94 for your particular device. It won't happen automatically. The
128 for your particular device. It won't happen automatically. The
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/
Dfsl,mxs-pinctrl.txt28 one is to adjust the pin configuration for some particular pins that need a
33 means a group of pins put together for particular peripheral to work in
34 particular function, like SSP0 functioning as mmc0-8bit. That said, the
/kernel/linux/linux-5.10/arch/powerpc/platforms/85xx/
Dqemu_e500.c6 * to a particular piece of hardware or a particular spec of virtual hardware,
/kernel/linux/linux-5.10/include/dt-bindings/dma/
Daxi-dmac.h14 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
33 * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Daxp809.dtsi18 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
37 * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

12345678910>>...392