| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | cfg_srv.c | 117 uint8_t ttl, uint8_t period, uint8_t retransmit, bool store) in _mod_pub_set() argument
127 if (!model->pub->update && period) { in _mod_pub_set()
140 model->pub->period = 0U; in _mod_pub_set()
173 model->pub->period = period; in _mod_pub_set()
676 net_buf_simple_add_u8(&msg, mod->pub->period); in send_mod_pub_status()
2274 net_buf_simple_add_u8(&msg, bt_mesh_hb_log(pub->period)); in hb_pub_send_status()
2319 pub.period = 0x10000; in heartbeat_pub_set()
2321 pub.period = bt_mesh_hb_pwr2(param->period_log); in heartbeat_pub_set()
2405 uint32_t period; in heartbeat_sub_set() local
2422 period = 0x10000; in heartbeat_sub_set()
[all …]
|
| /Zephyr-latest/drivers/led/ |
| D | led_pwm.c | 68 (uint32_t) ((uint64_t) dt_led->period * value / 100)); in led_pwm_set_brightness()
|
| /Zephyr-latest/ |
| D | CODE_OF_CONDUCT.md | 95 those enforcing the Code of Conduct, for a specified period of time. This
106 communication with the community for a specified period of time. No public or
108 with those enforcing the Code of Conduct, is allowed during this period.
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.nrf_grtc | 50 NRF_GRTC_SYSCOUNTER_SLEEP_MINIMUM_LATENCY period makes no sense.
|
| /Zephyr-latest/boards/arduino/zero/ |
| D | arduino_zero.dts | 97 /* Gives a maximum period of 1.4 s */
|
| /Zephyr-latest/drivers/pwm/ |
| D | pwm_stm32.c | 56 uint32_t period; member
701 cpt->period = get_channel_capture[cpt->channel - 1](cfg->timer); in pwm_stm32_isr()
729 cpt->period = get_channel_capture[cpt->channel - 1](cfg->timer); in pwm_stm32_isr()
752 cpt->callback(dev, cpt->channel, cpt->capture_period ? cpt->period : 0u, in pwm_stm32_isr()
|
| D | Kconfig | 33 period/pulse widths.
|
| /Zephyr-latest/samples/modules/lvgl/accelerometer_chart/ |
| D | README.rst | 15 the chart. The update period is configurable, see
|
| /Zephyr-latest/boards/atmel/sam0/samd21_xpro/ |
| D | samd21_xpro.dts | 66 /* Gives a maximum period of 1.4s */
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | connection_mgmt.rst | 13 longer period of time, since this ensures that the object remains valid
|
| /Zephyr-latest/boards/atmel/sam0/samr34_xpro/ |
| D | samr34_xpro.dts | 67 /* Gives a maximum period of 1.4s */
|
| /Zephyr-latest/boards/adafruit/trinket_m0/ |
| D | adafruit_trinket_m0.dts | 101 /* Gives a maximum period of 1.4 s */
|
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.processing | 73 int "Set internal log processing thread sleep period"
76 Log processing thread sleeps for requested period given in
|
| /Zephyr-latest/boards/atmel/sam0/saml21_xpro/ |
| D | saml21_xpro.dts | 67 /* Gives a maximum period of 1.4s */
|
| /Zephyr-latest/subsys/net/lib/wifi_credentials/ |
| D | Kconfig | 72 Wait period before falling back to the next entry in the list of stored SSIDs.
|
| /Zephyr-latest/samples/basic/servo_motor/ |
| D | README.rst | 39 Note that a commonly used period value is 20 ms. See
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 414 …tely removes the handshake when device resumes operation after long idle period. Greatly helps whe…
608 after a configured time period.
617 Client will deregister and stay idle for the disable period.
668 - No actions needed, client will re-register once the disable period is over.
677 Configuring lifetime and activity period
683 .. list-table:: Update period variables
708 This is then affecting the period of updates the client is doing.
710 period of when the device is reachable from the server.
719 registration and configure the period accurately, even if server changes the lifetime parameter.
|
| /Zephyr-latest/drivers/counter/ |
| D | counter_renesas_ra_agt.c | 51 uint32_t period; /* Current timer period (counts) */ member
287 info.period_counts = data->period; in counter_ra_agt_get_freq()
459 data->period = period_counts; in r_agt_period_register_set()
|
| /Zephyr-latest/subsys/demand_paging/eviction/ |
| D | Kconfig | 47 int "Recently accessed period, in milliseconds"
|
| /Zephyr-latest/boards/atmel/sam0/same54_xpro/ |
| D | same54_xpro.dts | 64 /* Gives a maximum period of 1.1s for 120MHz main clock */
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.stm32_hal | 91 int "Carrier check timeout period (ms)"
96 Set the RX idle timeout period in milliseconds after which the
|
| /Zephyr-latest/tests/drivers/build_all/input/ |
| D | app.overlay | 117 steps-per-period = <4>;
128 steps-per-period = <4>;
|
| /Zephyr-latest/include/zephyr/bluetooth/mesh/ |
| D | cfg_cli.h | 413 uint8_t period; member
432 uint8_t period; member
480 uint8_t period; member
|
| /Zephyr-latest/drivers/clock_control/ |
| D | clock_control_litex.c | 1133 pm, global_period, clkout_period, period; in litex_clk_get_phase() local
1153 period = delay_time * global_period + pm; in litex_clk_get_phase()
1155 period = period * 1000 / clkout_period; in litex_clk_get_phase()
1156 period = period * 360; in litex_clk_get_phase()
1158 return litex_round(period, 1000); in litex_clk_get_phase()
|
| /Zephyr-latest/subsys/net/lib/lwm2m/ |
| D | Kconfig | 206 minimum time period, the notification must be sent after the time
207 period expires.
214 between notifications. When this time period expires a notification
504 int "LwM2M engine update period"
508 Time period after the previous update or registration when to send the next update message.
509 This allows modifying lifetime without affecting the update period.
511 send the update. When both values are set, smallest period will be used.
|
