Searched full:certain (Results 1 – 25 of 2910) sorted by relevance
12345678910>>...117
| /kernel/linux/linux-5.10/include/linux/pinctrl/ |
| D | pinmux.h | 23 * @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
|
| D | pinconf.h | 24 * @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
|
| /kernel/linux/linux-6.6/include/linux/pinctrl/ |
| D | pinmux.h | 22 * @request: called by the core to see if a certain pin can be made
32 * certain device to
34 * referencing pins) connected to a certain function selector. The group
38 * @set_mux: enable a certain muxing function with a certain pin group. The
42 * certain function whereas @group_selector selects a certain set of pins
44 * @gpio_request_enable: requests and enables GPIO on a certain pin.
49 * @gpio_disable_free: free up GPIO muxing on a certain pin, the reverse of
|
| D | pinconf.h | 24 * @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
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | pinctl.rst | 128 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 …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | pin-control.rst | 127 actual enumerated pins that are part of a certain group.
195 using a certain resistor value - pull up and pull down - so that the pin has a
279 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 …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | dev-event.rst | 10 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
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-event.rst | 10 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
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 12 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
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/i915/ |
| D | Kconfig.profile | 70 certain platforms and certain engines which will be reflected in the
89 certain platforms and certain engines which will be reflected in the
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/freescale/ |
| D | dpaa.rst | 185 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.::
|
| /kernel/linux/linux-6.6/Documentation/networking/device_drivers/ethernet/freescale/ |
| D | dpaa.rst | 185 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.::
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 12 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
|
| /kernel/linux/linux-6.6/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | time-event.h | 19 * 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
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | async.h | 58 * async_schedule_domain - schedule a function for asynchronous execution within a certain domain
65 * wait within a certain synchronization domain rather than globally.
107 * wait within a certain synchronization domain rather than globally.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | async.h | 58 * async_schedule_domain - schedule a function for asynchronous execution within a certain domain
65 * wait within a certain synchronization domain rather than globally.
107 * wait within a certain synchronization domain rather than globally.
|
| /kernel/linux/linux-6.6/drivers/thermal/ |
| D | thermal_core.h | 85 * a certain cooling device on a certain trip point
86 * in a certain thermal zone
|
| /kernel/linux/linux-5.10/Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 23 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.
|
| /kernel/linux/linux-6.6/Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 23 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.
|
| /kernel/linux/linux-6.6/drivers/usb/storage/ |
| D | initializers.h | 3 * Header file for Special Initializers for certain USB Mass Storage devices
19 * Also, for certain devices, the interrupt endpoint is used to convey
|
| /kernel/linux/linux-5.10/drivers/usb/storage/ |
| D | initializers.h | 3 * Header file for Special Initializers for certain USB Mass Storage devices
19 * Also, for certain devices, the interrupt endpoint is used to convey
|
| /kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | time-event.h | 76 * In order to make sure that the fw is on a specific channel at a certain time
77 * and for a certain duration, the driver needs to issue a time event.
88 * When the driver needs to make sure we are in a certain channel, at a certain
89 * time and for a certain duration, it sends a Time Event. The flow against the
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | tproxy.rst | 17 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
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | tproxy.rst | 17 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
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra30-tsensor.yaml | 20 a certain thermal/voltage threshold.
23 a certain thermal/voltage threshold.
|
12345678910>>...117