Searched refs:tri (Results 1 – 12 of 12) sorted by relevance
| /f-stack/freebsd/contrib/device-tree/Bindings/gpio/ |
| H A D | gpio-xilinx.txt | 20 - xlnx,tri-default : if n-th bit is 1, GPIO-n is in tristate mode 25 - xlnx,tri-default-2 : as above but for the second channel 44 xlnx,tri-default = <0xffffffff>; 45 xlnx,tri-default-2 = <0xffffffff>;
|
| /f-stack/freebsd/arm/allwinner/ |
| H A D | aw_nmi.c | 76 enum intr_trigger tri; member 261 if (pol != nmi_intr->pol || trig != nmi_intr->tri) in aw_nmi_setup_intr() 268 nmi_intr->tri = trig; in aw_nmi_setup_intr() 297 sc->intr.tri = INTR_TRIGGER_CONFORM; in aw_nmi_teardown_intr() 377 sc->intr.tri = INTR_TRIGGER_CONFORM; in aw_nmi_attach()
|
| /f-stack/freebsd/contrib/device-tree/Bindings/net/wireless/ |
| H A D | ieee80211.txt | 11 An example case for this can be tri-band wireless router with two
|
| /f-stack/freebsd/contrib/device-tree/src/mips/xilfpga/ |
| H A D | nexys4ddr.dts | 51 xlnx,tri-default = <0xffffffff>;
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/ |
| H A D | pinctrl-bindings.txt | 4 such as pull-up/down, tri-state, drive-strength etc are designated as pin 15 need to reconfigure pins at run-time, for example to tri-state pins when the
|
| H A D | nvidia,tegra20-pinmux.txt | 6 the tri-state, mux, pull-up/down, and pad control register sets.
|
| /f-stack/freebsd/contrib/device-tree/src/arm64/qcom/ |
| H A D | msm8998-mtp.dtsi | 397 * module is in tri-state (module powered off or not
|
| H A D | msm8998-clamshell.dtsi | 329 * module is in tri-state (module powered off or not
|
| H A D | sc7180-idp.dts | 504 * in tri-state (module powered off or not driving the
|
| H A D | sdm845-cheza.dtsi | 965 * in tri-state (module powered off or not driving the
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | tegra20-colibri.dtsi | 761 /* Not tri-stating GMI_WR_N on SODIMM pin 93 RDnWR */ 766 line-name = "Not tri-state RDnWR";
|
| H A D | tegra30-colibri.dtsi | 187 /* Not tri-stating GMI_WR_N on RDnWR SODIMM pin 93 */
|