Home
last modified time | relevance | path

Searched refs:format (Results 376 – 400 of 530) sorted by relevance

1...<<11121314151617181920>>...22

/Zephyr-latest/doc/services/device_mgmt/smp_groups/
Dsmp_group_8.rst592 (str)"format" : (uint)
631 … | "format" | format that the hash/checksum returns where 0 is for numerical and 1 is |
/Zephyr-latest/drivers/sensor/
DKconfig63 in a convenient format. It makes use of a fuel gauge to read its
/Zephyr-latest/scripts/west_commands/completion/
Dwest-completion.bash395 boards=( $(__west_x boards --format='{name}|{qualifiers}' "$@") )
/Zephyr-latest/boards/st/stm32f746g_disco/
Dstm32f746g_disco.dts281 pixel-format = <PANEL_PIXEL_FORMAT_RGB_565>;
/Zephyr-latest/boards/nxp/rd_rw612_bga/
Drd_rw612_bga.dtsi251 * broken out in the format required to connect directly to
/Zephyr-latest/doc/develop/tools/
Dstm32cubeide.rst49 CMake argument format. If an out-of-tree board is targeted, the ``BOARD_ROOT``
/Zephyr-latest/subsys/usb/device_next/class/
Dusbd_msc_scsi.c159 uint8_t format; member
471 r.format = 0x02; in fill_inquiry()
/Zephyr-latest/doc/hardware/porting/
Dsoc_porting.rst104 :ref:`kconfig` format. These select the architecture and peripherals
152 the Devicetree Source (DTS) format and must be included by any boards which use
/Zephyr-latest/drivers/i2s/
Di2s_mcux_sai.c518 switch (i2s_cfg->format & I2S_FMT_DATA_FORMAT_MASK) { in i2s_mcux_config()
568 switch (i2s_cfg->format & I2S_FMT_CLK_FORMAT_MASK) { in i2s_mcux_config()
601 if ((i2s_cfg->format & I2S_FMT_DATA_FORMAT_MASK) != I2S_FMT_DATA_FORMAT_PCM_SHORT) { in i2s_mcux_config()
/Zephyr-latest/doc/build/dts/
Dintro-syntax-structure.rst6 As the name indicates, a devicetree is a tree. The human-readable text format
230 The recommended format is ``"vendor,device"``, like ``"avago,apds9960"``,
323 This section describes how to write property values in DTS format. The property
/Zephyr-latest/modules/mbedtls/
DKconfig.tls-generic382 bool "Support for PEM certificate format"
384 By default only DER (binary) format of certificates is supported. Enable
385 this option to enable support for PEM format.
/Zephyr-latest/samples/subsys/mgmt/updatehub/
DREADME.rst253 format you SoC tools uses. In general, Zephyr can create images with binary
254 (``.bin``) image format or Intel's (``.hex``) image format.
/Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/src/
Dmain.c535 config.format = I2S_FMT_DATA_FORMAT_I2S; in main()
/Zephyr-latest/subsys/canbus/isotp/
DKconfig139 This option allow to use an alternative CAN frame id format.
/Zephyr-latest/boards/witte/linum/
Dlinum.dts320 pixel-format = <PANEL_PIXEL_FORMAT_RGB_565>;
/Zephyr-latest/boards/st/stm32h7b3i_dk/
Dstm32h7b3i_dk.dts253 pixel-format = <PANEL_PIXEL_FORMAT_RGB_565>;
/Zephyr-latest/arch/x86/zefi/
DREADME.txt65 format certainly allows that, and the UEFI specification doesn't
/Zephyr-latest/doc/build/signing/
Dindex.rst49 If your ``west flash`` :ref:`runner <west-runner>` uses an image format supported by imgtool, you
/Zephyr-latest/samples/subsys/shell/fs/
DREADME.rst190 Read file and dump in hex and ASCII format
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-arch.rst43 The `Bluetooth Specification`_ describes the format in which a Host must
48 the format for user and protocol data that needs to go over the air. The HCI
/Zephyr-latest/
DKconfig.zephyr736 bool "Build a binary in HEX format"
748 bool "Build a binary in BIN format"
769 bool "Build a binary in ELF format with .exe extension"
776 bool "Build a binary in S19 format"
788 bool "Build a binary in UF2 format"
1039 format length modifiers can be used universally across ILP32
/Zephyr-latest/scripts/ci/es_upload/
DREADME.md21 in the current Twister report format and in the upload script itself.
/Zephyr-latest/scripts/ci/
Dtwister_report_analyzer.py336 logging.basicConfig(level=args.log_level, format='%(levelname)-8s: %(message)s')
/Zephyr-latest/scripts/logging/dictionary/
Ddatabase_gen.py505 logging.basicConfig(format=LOGGER_FORMAT, level=logging.WARNING)
/Zephyr-latest/doc/develop/test/twister/
Dtwister_blackbox.rst16 Auxiliary test data follows whichever format it was in originally.

1...<<11121314151617181920>>...22