Home
last modified time | relevance | path

Searched refs:D3 (Results 1 – 25 of 77) sorted by relevance

1234

/Linux-v5.4/Documentation/i2c/
Di2c-topology.rst135 '--| dev D3 |
153 of the entire operation. But accesses to D3 are possibly interleaved
195 '--| dev D3 |
216 This means that accesses to both D2 and D3 are locked out for the full
234 '--| dev D4 | '--| dev D3 |
258 '--| dev D4 | '--| dev D3 |
263 are locked). But accesses to D3 and D4 are possibly interleaved at
264 any point. Accesses to D3 locks out D1 and D2, but accesses to D4
279 '--| dev D4 | '--| dev D3 |
282 When device D1 is accessed, accesses to D2 and D3 are locked out
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/thermal/
Drcar-thermal.txt7 fallback except R-Car V3M/E3/D3 and RZ/G2E.
20 - "renesas,thermal-r8a77995" (R-Car D3)
28 R-Car V3M/E3/D3 and RZ/G2E or 1 interrupt otherwise.
/Linux-v5.4/arch/arm64/boot/dts/amlogic/
Dmeson-gxbb-nanopi-k2.dts210 "Eth RX D3", "Eth RGMII TX Clk", "Eth TX En",
211 "Eth TX D0", "Eth TX D1", "Eth TX D2", "Eth TX D3",
217 "eMMC D0", "eMMC D1", "eMMC D2", "eMMC D3", "eMMC D4",
224 "SDCard D3", "SDCard D2", "SDCard Det",
242 "WIFI SDIO D3", "WIFI SDIO CLK", "WIFI SDIO CMD",
Dmeson-gxl-s905x-khadas-vim.dts146 "eMMC D0", "eMMC D1", "eMMC D2", "eMMC D3",
152 "SDCard D3", "SDCard D2", "SDCard Det",
160 "WIFI SDIO D3", "WIFI SDIO CLK", "WIFI SDIO CMD",
Dmeson-gxbb-odroidc2.dts204 "Eth RX D3", "Eth RGMII TX Clk", "Eth TX En",
205 "Eth TX D0", "Eth TX D1", "Eth TX D2", "Eth TX D3",
210 "eMMC D0", "eMMC D1", "eMMC D2", "eMMC D3", "eMMC D4",
216 "SDCard D3", "SDCard D2", "SDCard Det",
Dmeson-gxl-s905x-libretech-cc.dts198 "eMMC D0", "eMMC D1", "eMMC D2", "eMMC D3",
204 "SDCard D3", "SDCard D2", "SDCard Det",
/Linux-v5.4/arch/arm/boot/dts/
Dstm32f7-pinctrl.dtsi231 <STM32_PINMUX('C', 11, AF12)>, /* SDMMC1 D3 */
244 <STM32_PINMUX('C', 11, AF12)>, /* SDMMC1 D3 */
262 <STM32_PINMUX('B', 4, AF10)>, /* SDMMC2 D3 */
275 <STM32_PINMUX('B', 4, AF10)>, /* SDMMC2 D3 */
Defm32gg-dk3750.dts61 cs-gpios = <&gpio 51 1>; // D3
/Linux-v5.4/arch/m68k/fpsp040/
Dsrem_mod.S117 movel 8(%a0),%d5 | ...(D3,D4,D5) is |Y|
133 subl %d6,%d3 | ...(D3,D4,D5) is normalized
147 orl %d7,%d4 | ...(D3,D4,D5) normalized
152 addil #0x00003FFE,%d3 | ...(D3,D4,D5) normalized
207 clrl %d3 | ...D3 is Q
/Linux-v5.4/Documentation/devicetree/bindings/display/bridge/
Drenesas,lvds.txt23 - "renesas,r8a77995-lvds" for R8A77995 (R-Car D3) compatible LVDS encoders
52 mandatory for the first LVDS encoder on D3 and E3 SoCs, and shall point to
/Linux-v5.4/drivers/soc/renesas/
DKconfig231 bool "Renesas R-Car D3 SoC Platform"
235 This enables support for the Renesas R-Car D3 SoC.
305 bool "R-Car D3 System Controller support" if COMPILE_TEST
/Linux-v5.4/Documentation/devicetree/bindings/spi/
Defm32-spi.txt29 cs-gpios = <&gpio 51 1>; // D3
/Linux-v5.4/Documentation/devicetree/bindings/display/
Drenesas,du.txt24 - "renesas,du-r8a77995" for R8A77995 (R-Car D3) compatible DU
76 R8A77995 (R-Car D3) DPAD 0 LVDS 0 LVDS 1 -
/Linux-v5.4/Documentation/devicetree/bindings/pwm/
Drenesas,pwm-rcar.txt21 - "renesas,pwm-r8a77995": for R-Car D3
/Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/
Drenesas,irqc.txt26 - "renesas,intc-ex-r8a77995" (R-Car D3)
/Linux-v5.4/Documentation/devicetree/bindings/watchdog/
Drenesas,wdt.txt24 - "renesas,r8a77995-wdt" (R-Car D3)
/Linux-v5.4/Documentation/devicetree/bindings/power/
Drenesas,rcar-sysc.txt28 - "renesas,r8a77995-sysc" (R-Car D3)
/Linux-v5.4/Documentation/devicetree/bindings/reset/
Drenesas,rst.txt37 - "renesas,r8a77995-rst" (R-Car D3)
/Linux-v5.4/Documentation/networking/
DPLIP.txt141 D3->ACK 5 - 10 10 - 5
171 D3->D3 5 - 5
/Linux-v5.4/Documentation/devicetree/bindings/dma/
Drenesas,usb-dmac.txt20 - "renesas,r8a77995-usb-dmac" (R-Car D3)
/Linux-v5.4/Documentation/devicetree/bindings/usb/
Drenesas,usbhs.txt21 - "renesas,usbhs-r8a77995" for r8a77995 (R-Car D3) compatible device
/Linux-v5.4/Documentation/power/
Dpci.rst85 The PCI PM Spec defines 4 operating states for devices (D0-D3) and for buses
90 There are two variants of the D3 state defined by the specification. The first
91 one is D3hot, referred to as the software accessible D3, because devices can be
118 | D0 | D1, D2, D3 |
120 | D1 | D2, D3 |
122 | D2 | D3 |
124 | D1, D2, D3 | D0 |
133 while in a low-power state (D1-D3), but they are not required to be capable
166 labeled as D0, D1, D2, and D3 that roughly correspond to the native PCI PM
167 D0-D3 states (although the difference between D3hot and D3cold is not taken
[all …]
/Linux-v5.4/arch/arm64/boot/dts/renesas/
Dr8a77980-condor.dts36 regulator-name = "D3.3V";
/Linux-v5.4/Documentation/spi/
Dspi-lm70llp.rst42 D3 5 --> V+ 5
/Linux-v5.4/Documentation/devicetree/bindings/iommu/
Drenesas,ipmmu-vmsa.txt29 - "renesas,ipmmu-r8a77995" for the R8A77995 (R-Car D3) IPMMU.

1234