Home
last modified time | relevance | path

Searched full:facing (Results 1 – 24 of 24) sorted by relevance

/Zephyr-latest/dts/bindings/usb-c/
Dusb-c-connector.yaml89 * "host" for Downstream Facing Port (DFP)
90 * "device" for Upstream Facing Port (UFP)
/Zephyr-latest/dts/bindings/espi/
Dmicrochip,xec-espi-host-dev.yaml29 # optional properties application to different host facing devices
/Zephyr-latest/doc/hardware/peripherals/
Dbc12.rst56 * The application configured the port as an upstream facing port, i.e. a USB
74 a downstream facing port, i.e. a USB host port. For charging port mode, the
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D001_bug_report.md26 the problem you're facing:
/Zephyr-latest/include/zephyr/drivers/usb_c/
Dusbc_tc.h390 /** Data role is an Upstream Facing Port */
392 /** Data role is a Downstream Facing Port */
/Zephyr-latest/boards/microchip/mec172xmodular_assy6930/
Dmec172xmodular_assy6930.dts98 /* enable various eSPI child devices (host facing) */
/Zephyr-latest/boards/microchip/mec172xevb_assy6906/
Dmec172xevb_assy6906.dts104 /* enable various eSPI child devices (host facing) */
/Zephyr-latest/include/zephyr/drivers/timer/
Dsystem_timer.h128 * user-facing API is owned by the architecture, not the driver. The
/Zephyr-latest/include/zephyr/usb_c/
Dusbc.h98 /** Data Role has been set to Upstream Facing Port (UFP) */
100 /** Data Role has been set to Downstream Facing Port (DFP) */
/Zephyr-latest/arch/x86/include/
Dx86_mmu.h8 * None of these are application-facing, use only if you know what you are
/Zephyr-latest/include/zephyr/kernel/
Dthread.h71 /* user facing 'thread options'; values defined in include/kernel.h */
/Zephyr-latest/lib/os/zvfs/
Dzvfs_eventfd.c405 * Public-facing API
/Zephyr-latest/kernel/include/
Dmmu.h109 * is otherwise not application-facing.
/Zephyr-latest/drivers/usb/bc12/
Dbc12_pi3usb9201.c433 * as a downstream facing port but charging is disabled. in pi3usb9201_set_charging_mode()
/Zephyr-latest/doc/releases/
Drelease-notes-1.10.rst38 * Add the following application-facing memory domain APIs:
326 * :github:`3716` - define / implement application-facing memory domain APIs
Drelease-notes-2.1.rst873 * :github:`16035` - facing problem with SDHC driver disk mount, need help to debug better
Drelease-notes-2.2.rst1099 * :github:`20161` - Facing issue to setup zephyr on ubuntu
Drelease-notes-3.2.rst2164 * :github:`48149` - Sensor Subsystem: client facing API: finding sensors
/Zephyr-latest/doc/security/standards/
Detsi-303645.rst66 of the consumer-facing functionality
/Zephyr-latest/doc/develop/flash_debug/
Dprobes.rst463 It is usually useful when facing flashing issues, for instance when using
/Zephyr-latest/drivers/espi/
Despi_mchp_xec_v2.c1500 * RESET_VCC to de-assert. Host facing peripherals will no longer in espi_xec_init()
/Zephyr-latest/include/zephyr/sys/
Dtime_units.h103 * appropriately in a user-facing API. The boolean arguments are:
/Zephyr-latest/arch/x86/core/
Dx86_mmu.c892 * This only has implications for CONFIG_X86_KPTI where user thread facing
/Zephyr-latest/scripts/kconfig/
Dkconfiglib.py5097 and interface less confusing (especially in a user-facing interface).