Home
last modified time | relevance | path

Searched refs:period (Results 151 – 175 of 265) sorted by relevance

1234567891011

/Zephyr-latest/drivers/disk/nvme/
DKconfig48 int "Timeout period for NVMe request"
/Zephyr-latest/samples/sensor/ccs811/
DREADME.rst37 After a soft reset, there is a 5-second startup period
/Zephyr-latest/subsys/tracing/test/
Dtracing_string_format_test.c322 k_timeout_t period) in sys_trace_k_timer_start() argument
325 (uint32_t)duration.ticks, (uint32_t)period.ticks); in sys_trace_k_timer_start()
/Zephyr-latest/drivers/pwm/
Dpwm_mc_esp32.c63 uint32_t period; member
507 capture->period = channel->inverted ? in mcpwm_esp32_isr()
530 capture->capture_period ? capture->period : 0u, in mcpwm_esp32_isr()
Dpwm_nxp_s32_emios.c658 uint32_t period = 0, pulse = 0; in pwm_nxp_s32_capture_callback() local
661 period = pwm_nxp_s32_capture_calc(data->ch_data[channel].edge_buff[0], in pwm_nxp_s32_capture_callback()
672 period = pwm_nxp_s32_capture_calc(data->ch_data[channel].edge_buff[0], in pwm_nxp_s32_capture_callback()
681 data->ch_data[channel].callback(dev, channel, period, pulse, 0, in pwm_nxp_s32_capture_callback()
/Zephyr-latest/subsys/net/l2/ethernet/gptp/
Dgptp.c756 int32_t new_itv, old_itv, period; in gptp_update_sync_interval() local
771 period = new_itv; in gptp_update_sync_interval()
800 K_MSEC(period)); in gptp_update_sync_interval()
/Zephyr-latest/drivers/dai/intel/dmic/
Ddmic.c171 static inline void dai_dmic_set_sync_period(uint32_t period, const struct dai_intel_dmic *dmic) in dai_dmic_set_sync_period() argument
173 uint32_t val = CONFIG_DAI_DMIC_HW_IOCLK / period - 1; in dai_dmic_set_sync_period()
235 static inline void dai_dmic_set_sync_period(uint32_t period, const struct dai_intel_dmic *dmic) {} in dai_dmic_set_sync_period() argument
/Zephyr-latest/drivers/sensor/renesas/isl29035/
DKconfig47 The sampling period of the internal ADC of the light sensor.
/Zephyr-latest/boards/espressif/esp32s3_eye/
Desp32s3_eye_procpu.dts50 sample-period-ms = <50>;
/Zephyr-latest/doc/security/standards/
Detsi-303645.rst68 * - defined support period
69 - minimum length of time, expressed as a period or by an end-date, for which a
259 and services they operate during the defined support period.
361 transparent to the user, the defined support period.
369 for the absence of software updates, the period and method of hardware replacement
370 support and a defined support period should be published by the manufacturer in an
/Zephyr-latest/drivers/wifi/nrf_wifi/
DKconfig.nrfwifi465 bool "extending TWT service period"
515 RSSI stale timeout is the period after which the driver queries
692 int "RPU recovery quiet period in milliseconds"
695 Quiet period in milliseconds after RPU recovery is triggered. During
696 this period, no new RPU recovery will be triggered.
767 int "Keepalive period in seconds"
771 Keepalive period in seconds to send keepalive packets to the AP.
/Zephyr-latest/drivers/sensor/vishay/vcnl36825t/
Dvcnl36825t.h298 enum vcnl36825t_measurement_period period; member
/Zephyr-latest/boards/st/b_g474e_dpow1/
Db_g474e_dpow1.dts175 * hbit_clk = HSI_clk / 27 = 592.6 kHz = 1.687 uSec period
/Zephyr-latest/boards/ite/it8xxx2_evb/
Dit8xxx2_evb.dts50 scan-period = <IT8XXX2_VCMP_SCAN_PERIOD_600US>;
/Zephyr-latest/boards/ite/it82xx2_evb/
Dit82xx2_evb.dts52 scan-period = <IT8XXX2_VCMP_SCAN_PERIOD_600US>;
/Zephyr-latest/boards/st/stm32g071b_disco/
Dstm32g071b_disco.dts177 * hbit_clk = HSI_clk / 27 = 592.6 kHz = 1.687 uSec period
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dshell.rst753 * ``PerRes``: Resolution of the publication period steps:
759 * ``PerSteps``: Number of publication period steps, or 0 to disable periodic publication.
778 * ``PerRes``: Resolution of the publication period steps:
784 * ``PerSteps``: Number of publication period steps, or 0 to disable periodic publication.
899 * ``Per``: Logarithmic representation of the Heartbeat subscription period:
902 …* ``1`` to ``17``: The node will subscribe to Heartbeat messages for 2\ :sup:`(period - 1)` second…
919 * ``Per``: Logarithmic representation of the Heartbeat publication period:
922 * ``1`` to ``17``: The node will publish Heartbeat messages every 2\ :sup:`(period - 1)` seconds.
1009 ``mesh models health period-get``
1012 Get the current Health Server publish period divisor.
[all …]
/Zephyr-latest/subsys/bluetooth/mesh/shell/
Dcfg.c1528 addr, mod_id, pub.addr, pub.app_idx, pub.cred_flag, pub.ttl, pub.period, in mod_pub_get()
1564 pub.period = (steps << 2) + res_step; in mod_pub_set()
1676 sub->src, sub->dst, sub->period, sub->count, sub->min, sub->max); in hb_sub_print()
1709 sub.period = shell_strtoul(argv[3], 0, &err); in hb_sub_set()
1764 shell_print(sh, "\tdst 0x%04x count 0x%02x period 0x%02x", pub.dst, pub.count, pub.period); in hb_pub_get()
1778 pub.period = shell_strtoul(argv[3], 0, &err); in hb_pub_set()
/Zephyr-latest/doc/project/
Drelease_process.rst23 - Each release period will consist of a development phase followed by a
229 for an extended period and is the recommended release for
235 - **Extended Stabilisation period**: Allow for more testing and bug fixing
238 - **Long Term**: Maintained for an extended period of time (at least 2.5 years)
258 stabilization period. Feature freeze of regular releases happens 3-4 weeks
259 before the scheduled release date. The stabilization period for LTS is extended
/Zephyr-latest/boards/seagate/legend/
Dlegend.dts158 * The maximum period needed on Legend devices for activity LED
/Zephyr-latest/include/zephyr/xen/public/
Ddomctl.h230 uint32_t period; member
/Zephyr-latest/soc/nordic/nrf52/
DKconfig127 Due to Anomaly 219 the low period of SCL clock is too short to meet
/Zephyr-latest/boards/arduino/nano_33_iot/doc/
Dindex.rst48 The SAMD21 MCU has 3 TCC based PWM units with up to 4 outputs each and a period
/Zephyr-latest/subsys/logging/backends/
DKconfig.rtt76 Sleep period between TX retry attempts. During RTT session, host pulls
/Zephyr-latest/subsys/logging/frontends/
DKconfig25 int "Dropped notification period"

1234567891011