Searched refs:should (Results 26 – 50 of 1262) sorted by relevance
12345678910>>...51
| /Zephyr-latest/subsys/net/lib/lwm2m/ |
| D | Kconfig.ipso | 14 This IPSO object should be used with a temperature sensor to
32 Select which version of the IPSO Temperature object should be used.
60 Select which version of the IPSO Generic Sensor object should be used.
100 Select which version of the IPSO Humidity Sensor object should be
131 Select which version of the IPSO Pressure Sensor object should be
178 Select which version of the IPSO Accelerometer object should be used.
207 Select which version of the IPSO Buzzer object should be used.
248 Select which version of the IPSO On/Off Switch object should be used.
278 Select which version of the IPSO Push Button object should be used.
291 This IPSO object should be used with a current sensor to
[all …]
|
| /Zephyr-latest/boards/gd/gd32f403z_eval/doc/ |
| D | index.rst | 97 terminal should be :code:`/dev/ttyUSB0`. For example:
104 string. Connection should be configured as follows:
119 You should see "Hello World! gd32f403z_eval" in your terminal.
134 should install `GD32 ISP Console`_ software at some Linux path. The recommended
158 terminal should be :code:`/dev/ttyUSB0`. For example:
165 string. Connection should be configured as follows:
174 You should see "Hello World! gd32f403z_eval" in your terminal.
|
| /Zephyr-latest/boards/gd/gd32e103v_eval/doc/ |
| D | index.rst | 97 terminal should be :code:`/dev/ttyUSB0`. For example:
104 string. Connection should be configured as follows:
119 You should see "Hello World! gd32e103v_eval" in your terminal.
134 should install `GD32 ISP Console`_ software at some Linux path. The recommended
158 terminal should be :code:`/dev/ttyUSB0`. For example:
165 string. Connection should be configured as follows:
174 You should see "Hello World! gd32e103v_eval" in your terminal.
|
| /Zephyr-latest/samples/subsys/modbus/rtu_server/ |
| D | README.rst | 17 but it should work with any board that has a free UART interface or USB
18 device controller. Additionally the board should have three LEDs.
39 The two A+, B- lines should be connected to the RS-485 shield.
45 USB device port should be connected to the USB port of a computer.
75 to the RTU server. If CDC ACM UART is used, ttyUSB should be replaced by a
90 Client should confirm successful communication and LED0 should light.
|
| /Zephyr-latest/soc/aspeed/ast10x0/ |
| D | Kconfig | 23 of /chosen/zephyr,sram in devicetree. The user should generally avoid
30 reg[1] of /chosen/zephyr,sram in devicetree. The user should
|
| /Zephyr-latest/drivers/ps2/ |
| D | Kconfig.npcx | 25 This should be lower than the PS2_INIT_PRIORITY as
26 NPCX PS/2 controller device driver should initialize
|
| /Zephyr-latest/boards/nordic/thingy53/ |
| D | Kconfig | 19 image application where one or more images should be located on
32 image application where one or more images should be located on
|
| /Zephyr-latest/drivers/i2c/ |
| D | Kconfig.sam0 | 28 0 means that the driver should use the K_FOREVER value,
29 i.e. it should wait as long as necessary.
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.cc2520 | 18 The default value should be sufficient, but in case it proves to be
27 be ready first (and sometime gpio should be the very first as spi
74 Such feature should not be used for anything but 802.15.4 security.
83 you know what you are doing. It should be initialized after CC2520
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 003_rfc-proposal.md | 31 reading this section each engineer should have a rather clear picture of what
37 This section is freeform - you should describe your change in as much detail
41 By reading this section, each team member should be able to know what exactly
|
| /Zephyr-latest/doc/project/ |
| D | dev_env_and_tools.rst | 17 Pull requests should be appropriately :ref:`labeled<gh_labels>`,
23 should use GitHub. GitHub Actions automatically assigns a responsible reviewer
58 should belong to. A project maintainers or TSC member monitoring the inflow of
60 why a change should belong to another category.
62 - Changes should not be merged before the minimal time has expired.
79 involvement. Such changes should not change the logic or the design of a
108 A Pull-Request should have an Assignee
111 - An assignee to a pull request should not be the same as the
117 - Pull requests should not be merged without an approval by the assignee.
119 Pull Request should not be merged by author without review
[all …]
|
| /Zephyr-latest/drivers/xen/ |
| D | Kconfig | 14 allocation with k_malloc(), so CONFIG_HEAP_MEM_POOL_SIZE should be
29 grant table driver in runtime. This value should be <= max_grant_frames
|
| /Zephyr-latest/boards/panasonic/pan1783/ |
| D | Kconfig | 15 image application where one or more images should be located on
28 image application where one or more images should be located on
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_context.rst | 6 The net_context API is not meant for application use. Application should use
|
| /Zephyr-latest/drivers/display/ |
| D | Kconfig.mcux_elcdif | 43 4-bytes pixel format, e.g. ARGB8888. Applications should change this value
64 rotation angle based on the call to display_write, so the user should
68 height settings of the screen in devicetree should not be modified
76 production applications should simply disable the PXP.
102 rotation angle based on the call to display_write, so the user should
106 height settings of the screen in devicetree should not be modified
|
| /Zephyr-latest/samples/drivers/video/tcpserversink/ |
| D | README.rst | 24 On :zephyr:board:`mimxrt1064_evk`, The MT9M114 camera module should be plugged in the
25 J35 camera connector. A USB cable should be connected from a host to the micro
62 For video software generator, the default resolution should be width=320 and height=160.
|
| /Zephyr-latest/tests/subsys/edac/ibecc/ |
| D | README.rst | 11 IBECC should be enabled in BIOS. This is usually enabled in the default
20 For injection test Error Injection should be enabled.
37 Due to high security risk Error Injection capability should not be
|
| /Zephyr-latest/boards/nordic/nrf7002dk/ |
| D | Kconfig | 27 image application where one or more images should be located on
44 image application where one or more images should be located on
|
| /Zephyr-latest/samples/subsys/modbus/tcp_server/ |
| D | README.rst | 17 but it should work with any board or shield that has a network interface.
18 Additionally the board should have three LEDs.
55 Client should confirm successful communication and LED0 should light.
|
| /Zephyr-latest/drivers/audio/ |
| D | Kconfig.dmic_mcux | 20 This determines how many buffers the driver should allocate and
22 API should provide at least one more buffer than this value, since
|
| /Zephyr-latest/drivers/dma/ |
| D | Kconfig.nxp_edma | 26 bool "Set if CPU should be interrupted when CITER = BITER / 2"
29 Enable this configuration if the CPU should be
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig | 39 the clock to be running already, you should let the default value as it
46 Timer drivers should select this flag if they are capable of
49 one should be expected not to produce a call to
56 This option should be selected by drivers implementing support for
62 This option should be selected by drivers implementing a lock free
|
| /Zephyr-latest/doc/build/dts/ |
| D | design.rst | 35 determine the hardware supported by a board. This should be obtained from
39 particular compatible are enabled. This can and should be done with devicetree
43 generated and maintained by hand. This can and should be obtained from the
46 - Runtime determination of ``struct device`` relationships should be done using
81 dtschema does not yet meet Zephyr's needs, we should try to follow what it is
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | mspi.rst | 68 * The :c:struct:`mspi_dev_cfg` should be filled by device tree and helper macro
71 * The controller driver should then validate the members of :c:struct:`mspi_dev_cfg`
74 * The controller driver should implement a mutex to protect from accidental access.
112 The mspi controller's bindings should reference mspi-controller.yaml as one of the base.
135 The mspi device's bindings should reference mspi-device.yaml as one of the base.
164 User should specify target operating parameters in the DTS such as ``mspi-max-frequency``,
166 It should represent the typical configuration of the device during normal operations.
174 by software, it should be performed in :c:func:`mspi_dev_config` call.
176 The device driver should record the current operating conditions of the device to support
|
| /Zephyr-latest/boards/u-blox/ubx_bmd380eval/ |
| D | Kconfig.ubx_bmd380eval | 9 # should be CKAA,
|
12345678910>>...51
