Home
last modified time | relevance | path

Searched refs:expose (Results 1 – 25 of 83) sorted by relevance

1234

/freebsd-13.1/contrib/llvm-project/llvm/tools/lli/
H A DExecutionUtils.cpp107 expose(Mangle("__dump_jit_debug_descriptor"), &dumpDebugDescriptor); in LLIBuiltinFunctionGenerator()
110 expose(Mangle("__dump_jit_debug_objects"), &dumpDebugObjects); in LLIBuiltinFunctionGenerator()
H A DExecutionUtils.h50 template <typename T> void expose(orc::SymbolStringPtr Name, T *Handler) { in expose() function
/freebsd-13.1/sys/contrib/device-tree/Bindings/misc/
H A Dge-achc.txt6 Note: This device does not expose the peripherals as USB devices.
/freebsd-13.1/sys/contrib/device-tree/Bindings/hwmon/
H A Dntc_thermistor.txt32 - "#thermal-sensor-cells" Used to expose itself to thermal fw.
/freebsd-13.1/sys/contrib/device-tree/Bindings/mfd/
H A Dstmpe.txt3 STMPE is an MFD device which may expose the following inbuilt devices: gpio,
H A Datmel-tcb.txt15 The TCB can expose multiple subdevices:
H A Dtc3589x.txt3 The Toshiba TC3589x series are I2C-based MFD devices which may expose the
/freebsd-13.1/sys/contrib/openzfs/contrib/intel_qat/patch/
H A D0001-timespec.diff1 This patch attempts to expose timespec and getnstimeofday which were
/freebsd-13.1/crypto/openssl/doc/man3/
H A DSSL_get_client_random.pod51 These functions expose internal values from the TLS handshake, for
62 do not expose it, or any information about it, to anybody.
/freebsd-13.1/contrib/lutok/
H A DREADME5 RAII to prevent resource leakage, expose C++-friendly data types, report
/freebsd-13.1/sys/contrib/device-tree/Bindings/gpio/
H A Dsgpio-aspeed.txt23 - ngpios : number of *hardware* GPIO lines, see gpio.txt. This will expose
/freebsd-13.1/sys/contrib/device-tree/Bindings/interrupt-controller/
H A Damlogic,meson-gpio-intc.txt6 or level and polarity. It does not expose all 256 mux inputs because the
/freebsd-13.1/sys/contrib/device-tree/src/arm64/marvell/
H A Darmada-3720-espressobin.dtsi91 * Connector J17 and J18 expose a number of different features. Some pins are
/freebsd-13.1/sys/contrib/device-tree/Bindings/interconnect/
H A Dinterconnect.txt12 nodes, which expose the interconnect related capabilities of the interconnect
H A Dfsl,imx8m-noc.yaml16 Some of those buses expose register areas mentioned in the memory maps as GPV
/freebsd-13.1/sys/contrib/device-tree/Bindings/display/panel/
H A Dpanel-common.yaml85 Some panels expose EDID information through an I2C-compatible
151 # controller exposed through a control bus such as I2C or DSI. Others expose
/freebsd-13.1/sys/contrib/device-tree/Bindings/display/bridge/
H A Dthine,thc63lvd1024.yaml20 configured through input signals and the chip does not expose any control
/freebsd-13.1/sys/riscv/conf/
H A DNOTES50 device nvd # expose NVMe namespaces as disks, depends on nvme
/freebsd-13.1/sys/dev/videomode/
H A Dediddevs93 * EDID version 1.3 requires that monitors expose the monitor name with
/freebsd-13.1/sys/contrib/device-tree/Bindings/ufs/
H A Dufshcd-pltfrm.txt54 - #reset-cells : Must be <1> for Qualcomm UFS controllers that expose
/freebsd-13.1/sys/contrib/device-tree/Bindings/sound/
H A Dst,sti-asoc-card.txt6 sti sound drivers allows to expose sti SoC audio interface through the
/freebsd-13.1/sys/dev/bhnd/cores/chipc/pwrctl/
H A Dbhnd_pwrctl_hostb_if.m44 # Early PWRCTL chipsets[1] expose clock management via their host bridge
/freebsd-13.1/sys/contrib/device-tree/Bindings/mux/
H A Dmux-controller.txt129 it is idle. For multiplexer chips that expose several mux controllers, the
/freebsd-13.1/sys/contrib/device-tree/Bindings/fsi/
H A Dfsi.txt6 nodes to probed engines. This allows for fsi engines to expose non-probeable
/freebsd-13.1/sys/contrib/device-tree/Bindings/clock/
H A Dbaikal,bt1-ccu-div.yaml73 clock provider just doesn't expose either switching functions, or the rate

1234