Home
last modified time | relevance | path

Searched full:certain (Results 1 – 25 of 1793) sorted by relevance

12345678910>>...72

/Linux-v6.1/include/linux/pinctrl/
Dpinmux.h23 * @request: called by the core to see if a certain pin can be made
33 * certain device to
35 * referencing pins) connected to a certain function selector. The group
39 * @set_mux: enable a certain muxing function with a certain pin group. The
43 * certain function whereas @group_selector selects a certain set of pins
45 * @gpio_request_enable: requests and enables GPIO on a certain pin.
50 * @gpio_disable_free: free up GPIO muxing on a certain pin, the reverse of
Dpinconf.h24 * @pin_config_get: get the config of a certain pin, if the requested config
32 * per-device info for a certain pin in debugfs
34 * per-device info for a certain group in debugfs
/Linux-v6.1/Documentation/driver-api/
Dpin-control.rst128 actual enumerated pins that are part of a certain group.
209 using a certain resistor value - pull up and pull down - so that the pin has a
290 controller handles control of a certain GPIO pin. Since a single pin controller
398 a certain physical pin (ball, pad, finger, etc) for multiple mutually exclusive
480 - FUNCTIONS have PIN GROUPS as defined on the generic level - so a certain
481 function is *always* associated with a certain set of pin groups, could
493 - The combination of a FUNCTION and a PIN GROUP determine a certain function
494 for a certain set of pins. The knowledge of the functions and pin groups
499 - The name of a function with a certain selector (>= 0)
500 - A list of groups associated with a certain function
[all …]
/Linux-v6.1/Documentation/userspace-api/media/v4l/
Ddev-event.rst10 notified on certain conditions taking place on a device. This might
32 Starting with kernel 3.1 certain guarantees can be given with regards to
42 3. Where applicable, certain event types can ensure that the payload of
/Linux-v6.1/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-bindings.txt12 For a client device to operate correctly, certain pin controllers must
13 set up certain specific pin configurations. Some client devices need a
31 they require certain specific named states for dynamic pin configuration.
61 the binding for that IP block requires certain pin states to
/Linux-v6.1/Documentation/networking/device_drivers/ethernet/freescale/
Ddpaa.rst185 queues is seen by the CPU as ingress traffic on a certain portal.
186 The DPAA QMan portal interrupts are affined each to a certain CPU.
193 When RSS is disabled, all traffic received by a certain interface is
198 traffic bursts from a certain queue are serviced by the same CPU.
201 certain interface when RSS is not enabled.
206 hardcoded, there is no indirection table to move traffic for a certain
212 RSS can be turned off for a certain interface using ethtool, i.e.::
/Linux-v6.1/drivers/net/wireless/intel/iwlwifi/mvm/
Dtime-event.h19 * In order to make sure that the fw is on a specific channel at a certain time
20 * and for a certain duration, the driver needs to issue a time event.
31 * When the driver needs to make sure we are in a certain channel, at a certain
32 * time and for a certain duration, it sends a Time Event. The flow against the
/Linux-v6.1/include/linux/
Dasync.h58 * async_schedule_domain - schedule a function for asynchronous execution within a certain domain
65 * wait within a certain synchronization domain rather than globally.
105 * wait within a certain synchronization domain rather than globally.
/Linux-v6.1/Documentation/driver-api/memory-devices/
Dti-gpmc.rst23 GPMC has certain timings that has to be programmed for proper
28 dependency for certain gpmc timings on gpmc clock frequency. Hence a
43 certain fields of struct gpmc_device_timings, zero those entries.
/Linux-v6.1/drivers/thermal/
Dthermal_core.h80 * a certain cooling device on a certain trip point
81 * in a certain thermal zone
/Linux-v6.1/drivers/usb/storage/
Dinitializers.h3 * Header file for Special Initializers for certain USB Mass Storage devices
19 * Also, for certain devices, the interrupt endpoint is used to convey
/Linux-v6.1/Documentation/networking/
Dtproxy.rst17 socket on your box, set the packet mark to a certain value::
36 Because of certain restrictions in the IPv4 routing output code you'll have to
62 acceptable in certain situations. (Think of proxying UDP for example: you won't
/Linux-v6.1/Documentation/devicetree/bindings/thermal/
Dnvidia,tegra30-tsensor.yaml20 a certain thermal/voltage threshold.
23 a certain thermal/voltage threshold.
/Linux-v6.1/Documentation/sound/designs/
Dpowersave.rst12 done fully or partially. It'll save a certain power consumption, thus
35 state. Also, it often takes certain time to wake up from the
/Linux-v6.1/kernel/
Dasync.c19 certain operations (primarily during system boot) to happen
157 * wait within a certain synchronization domain rather than globally.
246 * async_synchronize_full_domain - synchronize all asynchronous function within a certain domain
259 …* async_synchronize_cookie_domain - synchronize asynchronous function calls within a certain domai…
/Linux-v6.1/drivers/mmc/core/
Dquirks.h41 * - Certain Toshiba cards.
114 * Certain Hynix eMMC 4.41 cards might get broken when HPI feature
120 * Certain Micron (Numonyx) eMMC 4.5 cards might get broken when HPI
/Linux-v6.1/Documentation/networking/devlink/
Ddevlink-linecard.rst19 to mux the lanes with certain speed to multiple ports with lanes
34 * Provision a line card slot with certain line card type
45 cable of a certain type, without the need to
/Linux-v6.1/drivers/watchdog/
DKconfig336 and if it does, it reboots your system after a certain amount of
1042 it does, it reboots your computer after a certain amount of time.
1136 a certain amount of time.
1148 freeze, and if it does, it reboots your computer after a certain
1194 and if it does, it reboots your computer after a certain amount of time.
1320 freeze, and if it does, it reboots your computer after a certain
1386 freeze, and if it does, it reboots your computer after a certain
1457 and if it does, it reboots your computer after a certain amount of
1492 freeze, and if it does, it reboots your computer after a certain
1551 freeze, and if it does, it reboots your computer after a certain
[all …]
/Linux-v6.1/Documentation/admin-guide/blockdev/
Dfloppy.rst51 If you need certain options enabled every time you load the floppy driver,
67 certain controllers. This may speed up certain operations.
171 is needed on IBM L40SX laptops in certain video modes. (There seems
/Linux-v6.1/Documentation/networking/device_drivers/ethernet/neterion/
Ds2io.rst63 significant performance improvement on certain platforms(SGI Altix,
68 on certain platforms).
174 certain platforms(eg. SGI Altix, IBM xSeries).
/Linux-v6.1/Documentation/staging/
Dlzo.rst54 pointer. Distances are encoded using very few bits belonging to certain
56 Certain encodings involve one extra byte, others involve two extra bytes
74 In the code some length checks are missing because certain instructions
75 are called under the assumption that a certain number of bytes follow
/Linux-v6.1/Documentation/trace/
Dhisi-ptt.rst80 The weight influences the proportion of certain packets on the PCIe link.
117 device. It's also supported to trace the headers of certain type and of
118 certain direction.
163 You can trace the TLP headers of certain types by specifying the `type`
177 You can trace the TLP headers from certain direction, which is relative
/Linux-v6.1/Documentation/power/
Dopp.rst51 CONFIG_PM_OPP from power management menuconfig menu. Certain SoCs such as Texas
52 Instrument's OMAP framework allows to optionally boot at a certain OPP without
58 SoC framework -> modifies on required cases certain OPPs -> OPP layer
70 As the system proceeds to operate, SoC framework may choose to make certain
216 SoC temperature is lower than a certain threshold. The SoC framework
/Linux-v6.1/drivers/gpu/drm/msm/disp/mdp5/
Dmdp5_smp.h22 * Based on the size of the attached scanout buffer, a certain # of
25 * In some hw, some blocks are statically allocated for certain pipes
/Linux-v6.1/drivers/base/firmware_loader/
DKconfig19 828 bytes, enable this option unless you are certain you don't
114 You should only enable this functionality if you are certain you
146 certain you need to support some really custom firmware loading

12345678910>>...72