Searched refs:bitrate (Results 101 – 122 of 122) sorted by relevance
12345
/Zephyr-latest/drivers/i2c/ |
D | i2c_dw.c | 1122 dw->app_config = I2C_MODE_CONTROLLER | i2c_map_dt_bitrate(rom->bitrate); in i2c_dw_initialize() 1210 .bitrate = DT_INST_PROP(n, clock_frequency), \
|
D | i2c_ll_stm32_v1.c | 509 bitrate_cfg = i2c_map_dt_bitrate(cfg->bitrate); in i2c_stm32_target_register()
|
/Zephyr-latest/samples/modules/canopennode/ |
D | README.rst | 148 bitrate = 125000 159 sudo ip link set can0 type can bitrate 125000 restart-ms 100
|
/Zephyr-latest/doc/releases/ |
D | release-notes-3.7.rst | 153 * Deprecated the :c:func:`can_calc_prescaler` API function, as it allows for bitrate 641 * Added optional ``min-bitrate`` devicetree property for CAN transceivers. 643 … :c:macro:`DT_INST_CAN_TRANSCEIVER_MIN_BITRATE` for getting the minimum supported bitrate of a CAN 645 * Added support for specifying the minimum bitrate supported by a CAN controller in the internal 648 and maximum supported bitrate for a given CAN controller/CAN transceiver combination, reflecting 649 that retrieving the bitrate limits can no longer fail. Deprecated the existing 651 * Updated the CAN timing functions to take the minimum supported bitrate into consideration when 652 validating the bitrate. 655 ``bitrate`` and ``bitrate_data``. 897 * Added support for bitrate setting from the devicetree.
|
D | migration-guide-3.7.rst | 286 these properties can switch to using the ``bitrate``, ``sample-point``, ``bitrate-data``, and 289 :kconfig:option:`CONFIG_CAN_DEFAULT_BITRATE_DATA`) for specifying the initial CAN bitrate:
|
D | migration-guide-3.5.rst | 413 initial CAN bitrate using the ``bus-speed``, ``sample-point``, ``bus-speed-data``, and
|
D | release-notes-3.2.rst | 95 allow distinguishing between an out of range bitrate/sample point, an unsupported bitrate, and a 2471 …: can: CAN interfaces are brought up with default bitrate at boot, causing error frames if bus bit…
|
D | release-notes-2.5.rst | 391 algorithm to calculate optimal timing values from a bitrate and sample point. 392 The bitrate and sample point can be specified in the devicetree too. 402 A flag was introduced that enables a bitrate switch in CAN-FD frames.
|
D | release-notes-3.1.rst | 1233 …: can: CAN interfaces are brought up with default bitrate at boot, causing error frames if bus bit… 1460 * :github:`44985` - tests: drivers: can: timing: failure to set bitrate of 800kbit/s on nucleo_g474…
|
D | release-notes-1.12.rst | 746 * :github:`7933` - drivers: can: stm32_can: bitrate ignored
|
D | release-notes-2.7.rst | 1784 * :github:`34390` - i2s: bitrate is wrongly configured on STM32
|
D | release-notes-3.3.rst | 3419 * :github:`51177` - Change SPI configuration (bitrate) with MCUXpresso SPI driver fails
|
/Zephyr-latest/drivers/can/ |
D | can_sja1000.c | 790 err = can_calc_timing(dev, &timing, config->common.bitrate, in can_sja1000_init()
|
D | can_mcp2515.c | 975 ret = can_calc_timing(dev, &timing, dev_cfg->common.bitrate, in mcp2515_init()
|
D | can_xmc4xxx.c | 872 ret = can_calc_timing(dev, &timing, dev_cfg->common.bitrate, in can_xmc4xxx_init()
|
D | can_rcar.c | 1078 ret = can_calc_timing(dev, &timing, config->common.bitrate, in can_rcar_init()
|
D | can_renesas_ra.c | 847 ret = can_calc_timing(dev, &timing, cfg->common.bitrate, cfg->common.sample_point); in can_renesas_ra_apply_default_config()
|
D | can_stm32_bxcan.c | 662 ret = can_calc_timing(dev, &timing, cfg->common.bitrate, in can_stm32_init()
|
D | can_mcan.c | 1469 err = can_calc_timing(dev, &timing, config->common.bitrate, in can_mcan_init()
|
D | can_mcux_flexcan.c | 1148 err = can_calc_timing(dev, &data->timing, config->common.bitrate, in mcux_flexcan_init()
|
D | can_mcp251xfd.c | 1579 ret = can_calc_timing(dev, &timing, dev_cfg->common.bitrate, in mcp251xfd_init()
|
/Zephyr-latest/drivers/wifi/nrf_wifi/src/ |
D | wpa_supp_if.c | 1266 signal_info->data.current_tx_rate = info->sta_info.tx_bitrate.bitrate * 100; in nrf_wifi_wpa_supp_event_proc_get_sta()
|
12345