Searched full:signaling (Results 1 – 25 of 639) sorted by relevance
12345678910>>...26
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra186-pmc.txt | 46 used to set pad power state and signaling voltage. A pad can be either
47 in active or power down mode. The support for power state and signaling
49 1.8 V signaling voltages are supported on pins where software
50 controllable signaling voltage switching is available.
77 TEGRA_IO_PAD_VOLTAGE_3V3 to select between signaling voltages.
82 for ao-hv. Following pads have software configurable signaling
|
| D | nvidia,tegra20-pmc.yaml | 247 and signaling voltage. A pad can be either in active or power down mode.
248 The support for power state and signaling voltage configuration varies
249 depending on the pad in question. 3.3V and 1.8V signaling voltages
250 are supported on pins where software controllable signaling voltage
287 TEGRA_IO_PAD_VOLTAGE_3V3 to select between signaling voltages.
291 pads. None of the Tegra124 or Tegra132 pads support signaling
294 state configuration. Signaling voltage switching is supported
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | intro.rst | 51 other value (notably, "open drain" signaling).
55 cases (to support bidirectional signaling). GPIO controllers may have
96 driven) signaling. That term applies to CMOS transistors; "open collector" is
105 don't. When you need open drain signaling but your hardware doesn't directly
115 The same logic can be applied to emulate open source signaling, by driving the
123 delays the rising edge of SCK, and the I2C master adjusts its signaling rate
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | intro.rst | 51 other value (notably, "open drain" signaling).
55 cases (to support bidirectional signaling). GPIO controllers may have
96 driven) signaling. That term applies to CMOS transistors; "open collector" is
105 don't. When you need open drain signaling but your hardware doesn't directly
115 The same logic can be applied to emulate open source signaling, by driving the
123 delays the rising edge of SCK, and the I2C master adjusts its signaling rate
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mmc/ |
| D | nvidia,tegra20-sdhci.yaml | 114 signaling modes.
119 automatic calibration times out on a 1.8 V signaling mode.
124 signaling modes.
129 automatic calibration times out on a 3.3 V signaling mode.
142 signaling modes.
147 automatic calibration times out on a 1.8 V signaling mode.
152 signaling modes.
164 automatic calibration times out on a 3.3 V signaling mode.
|
| /kernel/linux/linux-6.6/drivers/platform/x86/intel/wmi/ |
| D | sbl-fw-update.c | 3 * Slim Bootloader(SBL) firmware update signaling driver
116 dev_info(&wdev->dev, "Slim Bootloader signaling driver attached\n"); in intel_wmi_sbl_fw_update_probe()
122 dev_info(&wdev->dev, "Slim Bootloader signaling driver removed\n"); in intel_wmi_sbl_fw_update_remove()
143 MODULE_DESCRIPTION("Slim Bootloader firmware update signaling driver");
|
| /kernel/linux/linux-5.10/drivers/platform/x86/ |
| D | intel-wmi-sbl-fw-update.c | 3 * Slim Bootloader(SBL) firmware update signaling driver
116 dev_info(&wdev->dev, "Slim Bootloader signaling driver attached\n"); in intel_wmi_sbl_fw_update_probe()
122 dev_info(&wdev->dev, "Slim Bootloader signaling driver removed\n"); in intel_wmi_sbl_fw_update_remove()
144 MODULE_DESCRIPTION("Slim Bootloader firmware update signaling driver");
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra186-pmc.yaml | 73 state and signaling voltage. A pad can be either in active or
74 power down mode. The support for power state and signaling voltage
76 1.8 V signaling voltages are supported on pins where software
77 controllable signaling voltage switching is available.
131 signaling voltages: sdmmc2-hv, dmic-hv, sdmmc1-hv, sdmmc3-hv,
|
| D | nvidia,tegra20-pmc.yaml | 277 and signaling voltage. A pad can be either in active or power down mode.
278 The support for power state and signaling voltage configuration varies
279 depending on the pad in question. 3.3V and 1.8V signaling voltages
280 are supported on pins where software controllable signaling voltage
317 TEGRA_IO_PAD_VOLTAGE_3V3 to select between signaling voltages.
321 pads. None of the Tegra124 or Tegra132 pads support signaling
324 state configuration. Signaling voltage switching is supported
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | atmsvc.h | 2 /* atmsvc.h - ATM signaling kernel-demon interface definitions */
16 /* become ATM signaling demon control socket */
49 * if signaling only uses one ATM interface).
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | atmsvc.h | 2 /* atmsvc.h - ATM signaling kernel-demon interface definitions */
16 /* become ATM signaling demon control socket */
49 * if signaling only uses one ATM interface).
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | dma-fence.h | 50 * DMA_FENCE_FLAG_TIMESTAMP_BIT - timestamp recorded for fence signaling
75 * signaling while simultaneously notifying the cb_list. Ergo, we
160 * Enable software signaling of fence.
163 * signaling, they can implement this op to enable the necessary
176 * signaling. True indicates successful enabling.
190 * driver must always have signaling enabled.
410 * function doesn't enable signaling, it is not guaranteed to ever return
437 * function doesn't enable signaling, it is not guaranteed to ever return
573 * rather than success. This must be set before signaling (so that the value
590 * After a fence is signaled the timestamp is updated with the signaling time,
[all …]
|
| D | dma-fence-chain.h | 32 * @cb: callback for signaling
34 * This is used to add the callback for signaling the
41 * @work: irq work item for signaling
|
| /kernel/linux/linux-5.10/net/atm/ |
| D | signaling.h | 2 /* net/atm/signaling.h - ATM signaling */
|
| /kernel/linux/linux-6.6/net/atm/ |
| D | signaling.h | 2 /* net/atm/signaling.h - ATM signaling */
|
| /kernel/linux/linux-6.6/include/net/caif/ |
| D | caif_layer.h | 36 * enum caif_ctrlcmd - CAIF Stack Control Signaling sent in layer.ctrlcmd().
63 * They are used for signaling originating from the modem or CAIF Link Layer.
79 * enum caif_modemcmd - Modem Control Signaling, sent from CAIF Client
123 * @modemcmd: Used for control signaling downwards in the stack.
210 * Used for signaling responses (CAIF_CTRLCMD_*_RSP)
|
| /kernel/linux/linux-5.10/include/net/caif/ |
| D | caif_layer.h | 36 * enum caif_ctrlcmd - CAIF Stack Control Signaling sent in layer.ctrlcmd().
63 * They are used for signaling originating from the modem or CAIF Link Layer.
79 * enum caif_modemcmd - Modem Control Signaling, sent from CAIF Client
123 * @modemcmd: Used for control signaling downwards in the stack.
210 * Used for signaling responses (CAIF_CTRLCMD_*_RSP)
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/ |
| D | nvidia,tegra20-sdhci.txt | 64 calibration offsets for 3.3 V signaling modes.
67 calibration offsets for 1.8 V signaling modes.
71 out on a 3.3 V signaling mode.
75 out on a 1.8 V signaling mode.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | dma-fence.h | 50 * DMA_FENCE_FLAG_TIMESTAMP_BIT - timestamp recorded for fence signaling
75 * signaling while simultaneously notifying the cb_list. Ergo, we
160 * Enable software signaling of fence.
163 * signaling, they can implement this op to enable the necessary
176 * signaling. True indicates successful enabling.
190 * driver must always have signaling enabled.
390 * function doesn't enable signaling, it is not guaranteed to ever return
417 * function doesn't enable signaling, it is not guaranteed to ever return
538 * rather than success. This must be set before signaling (so that the value
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | twl4030_omap3.dtsi | 26 * this file. For proper idle mode signaling with sys_clkreq and sys_off_mode
28 * sys_nvmode2 signaling.
|
| D | am5729-beagleboneai.dts | 557 /* DS: Default speed (DS) up to 25 MHz, including 1- and 4-bit modes (3.3 V signaling). */
558 /* HS: High speed up to 50 MHz (3.3 V signaling). */
559 /* SDR12: SDR up to 25 MHz (1.8 V signaling). */
560 /* SDR25: SDR up to 50 MHz (1.8 V signaling). */
561 /* SDR50: SDR up to 100 MHz (1.8 V signaling). */
562 /* SDR104: SDR up to 208 MHz (1.8 V signaling) */
563 /* DDR50: DDR up to 50 MHz (1.8 V signaling). */
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/ti/omap/ |
| D | twl4030_omap3.dtsi | 26 * this file. For proper idle mode signaling with sys_clkreq and sys_off_mode
28 * sys_nvmode2 signaling.
|
| D | am5729-beagleboneai.dts | 556 /* DS: Default speed (DS) up to 25 MHz, including 1- and 4-bit modes (3.3 V signaling). */
557 /* HS: High speed up to 50 MHz (3.3 V signaling). */
558 /* SDR12: SDR up to 25 MHz (1.8 V signaling). */
559 /* SDR25: SDR up to 50 MHz (1.8 V signaling). */
560 /* SDR50: SDR up to 100 MHz (1.8 V signaling). */
561 /* SDR104: SDR up to 208 MHz (1.8 V signaling) */
562 /* DDR50: DDR up to 50 MHz (1.8 V signaling). */
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mailbox/ |
| D | st,stm32-ipcc.yaml | 10 The IPCC block provides a non blocking signaling mechanism to post and
12 It provides the signaling for N bidirectionnal channels. The number of
|
| /kernel/linux/linux-6.6/Documentation/scheduler/ |
| D | completion.rst | 40 - the signaling side through a call to complete() or complete_all().
43 Note that while initialization must happen first, the waiting and signaling
243 Signaling completions:
256 The signaling will work as expected even if completions are signaled before
271 Signaling completion from IRQ context is fine as it will appropriately
|
12345678910>>...26