Searched refs:tied (Results 1 – 25 of 46) sorted by relevance
12
/Linux-v5.15/Documentation/devicetree/bindings/soc/qcom/ |
D | qcom,smd.txt | 61 In turn, subnodes of the "edges" represent devices tied to SMD channels on that 69 Definition: a list of channels tied to this device, used for matching 75 "rpm" subsystem. For the "rpm" subsystem we have a device tied to the
|
D | qcom,glink.txt | 41 Each subnode of the GLINK node represent function tied to a virtual 49 Definition: a list of channels tied to this function, used for matching
|
D | qcom,apr.txt | 26 Each subnode of the APR node represents service tied to this apr. The name
|
/Linux-v5.15/drivers/gpu/drm/nouveau/nvkm/engine/disp/ |
D | vga.c | 166 u32 tied = nvkm_rd32(device, 0x001084) & 0x10000000; in nvkm_rdvgaowner() local 167 if (tied == 0) { in nvkm_rdvgaowner()
|
/Linux-v5.15/Documentation/spi/ |
D | spi-lm70llp.rst | 66 collector is tied to VCC. 72 hand, the transistor is cut off and the voltage tied to it's collector is
|
/Linux-v5.15/Documentation/security/ |
D | landlock.rst | 69 A domain is a read-only ruleset tied to a set of subjects (i.e. tasks' 72 domain. Indeed, once in a domain, each rule is tied to a layer level. To
|
/Linux-v5.15/Documentation/driver-api/nvdimm/ |
D | security.rst | 93 An key with the current passphrase payload that is tied to the nvdimm should be 101 An key with the current passphrase payload that is tied to the nvdimm should be 115 An encrypted-key with the current user passphrase that is tied to the nvdimm
|
/Linux-v5.15/security/landlock/ |
D | Kconfig | 12 directory, etc.) tied to a file hierarchy. Such policy can be
|
/Linux-v5.15/Documentation/devicetree/bindings/mmc/ |
D | sdhci-atmel.txt | 20 For instance on SAMA5D2, the pin is usually tied to the GND with a resistor
|
/Linux-v5.15/drivers/net/wireless/microchip/wilc1000/ |
D | Kconfig | 37 immediately following reset when pin 9 (SDIO_SPI_CFG) is tied to
|
/Linux-v5.15/Documentation/userspace-api/media/v4l/ |
D | pixfmt-meta-intel-ipu3.rst | 50 Both 3A statistics and pipeline parameters described here are closely tied to
|
/Linux-v5.15/arch/powerpc/boot/dts/ |
D | xpedite5200.dts | 431 cle-line = <0x8>; /* CLE tied to A3 */ 432 ale-line = <0x10>; /* ALE tied to A4 */
|
D | xpedite5200_xmon.dts | 435 cle-line = <0x8>; /* CLE tied to A3 */ 436 ale-line = <0x10>; /* ALE tied to A4 */
|
D | ebony.dts | 316 /* Ebony has all 4 IRQ pins tied together per slot */
|
D | bamboo.dts | 281 /* Bamboo has all 4 IRQ pins tied together per slot */
|
/Linux-v5.15/Documentation/driver-api/media/drivers/ |
D | cx88-devel.rst | 66 GPIO 16(I believe) is tied to the IR port (if present).
|
/Linux-v5.15/Documentation/virt/kvm/arm/ |
D | psci.rst | 17 a given guest is tied to a particular PSCI revision (unlikely), or if
|
/Linux-v5.15/Documentation/devicetree/bindings/spi/ |
D | spi-davinci.txt | 23 lines can be tied to the interrupt controller. Set this
|
/Linux-v5.15/arch/arm/boot/dts/ |
D | armada-388-clearfog.dtsi | 193 * address pins tied low, which takes addresses 0x50 and 0x51.
|
D | sun7i-a20-bananapi-m1-plus.dts | 262 /* VBUS on usb host ports are tied to DC5V and therefore always on */
|
/Linux-v5.15/drivers/clk/samsung/ |
D | Kconfig | 92 certains clocks from SoC, but it could also be tied to other devices
|
/Linux-v5.15/Documentation/fb/ |
D | ep93xx-fb.rst | 127 the VIDSCRNPAGE (framebuffer physical offset) to be tied low. There is
|
/Linux-v5.15/Documentation/networking/device_drivers/ethernet/pensando/ |
D | ionic.rst | 93 reflects the rx-usecs value as they are tied together on the same interrupt.
|
/Linux-v5.15/Documentation/devicetree/bindings/mfd/ |
D | aspeed-lpc.txt | 138 The UARTs present in the ASPEED SoC can have their resets tied to the reset
|
/Linux-v5.15/Documentation/driver-api/ |
D | ioctl.rst | 238 is not tied to a physical device or constrained by the file system 248 that is not tied to a file descriptor.
|
12