Searched +full:divider +full:- +full:sel (Results 1 – 9 of 9) sorted by relevance
/Zephyr-latest/samples/sensor/fdc2x1x/boards/ |
D | nrf9160dk_nrf9160.overlay | 4 * SPDX-License-Identifier: Apache-2.0 8 clock-frequency = <I2C_BITRATE_FAST>; 12 sd-gpios = <&gpio0 16 GPIO_ACTIVE_HIGH>; 13 intb-gpios = <&gpio0 20 GPIO_ACTIVE_LOW>; 22 fref-divider = <1>; 24 fin-sel = <2>; 31 fref-divider = <1>; 33 fin-sel = <2>;
|
/Zephyr-latest/samples/basic/fade_led/boards/ |
D | cyw920829m2evk_02.overlay | 2 * SPDX-License-Identifier: Apache-2.0 8 #include <zephyr/dt-bindings/pwm/pwm.h> 9 #include <zephyr/dt-bindings/pwm/pwm_ifx_cat1.h> 13 pwm-led0 = &pwm_led0; 17 compatible = "pwm-leds"; 27 pinctrl-0 = <&p1_1_pwm0_0>; 28 pinctrl-names = "default"; 29 divider-type = <CY_SYSCLK_DIV_16_BIT>; 30 divider-sel = <1>; 31 divider-val = <9599>; [all …]
|
/Zephyr-latest/dts/bindings/pwm/ |
D | infineon,cat1-pwm.yaml | 4 # SPDX-License-Identifier: Apache-2.0 8 compatible: "infineon,cat1-pwm" 10 include: [pwm-controller.yaml, pinctrl-device.yaml] 21 pinctrl-0: 30 pinctrl-0 = <&p1_1_pwm0_0>; 33 pinctrl-names: 39 divider-type: 42 Specifies which type of divider to use. 46 divider-sel: 49 Specifies which divider of the selected type to configure. [all …]
|
/Zephyr-latest/dts/bindings/sensor/ |
D | ti,fdc2x1x.yaml | 2 # SPDX-License-Identifier: Apache-2.0 8 include: [sensor-device.yaml, i2c-device.yaml] 11 sd-gpios: 12 type: phandle-array 18 intb-gpios: 19 type: phandle-array 28 Set to identify the sensor as FDC2114 or FDC2214 (4-channel version) 33 Set the Auto-Scan Mode. 36 "active-channel" (single channel mode). 38 true = Auto-Scan conversions as selected by "rr-sequence" [all …]
|
/Zephyr-latest/soc/snps/arc_iot/ |
D | sysconf.c | 4 * SPDX-License-Identifier: Apache-2.0 47 * N = input divider value (1, 2, 3 … 15) 48 * M = feedback divider value (4, 5, 6 … 16383) 49 * NO = output divider value (1, 2, 4, or 8) 58 sysconf_reg_ptr->CLKSEL = CLKSEL_EXT_16M; in arc_iot_pll_conf_reg() 60 sysconf_reg_ptr->PLLCON = val | (0x52000000); in arc_iot_pll_conf_reg() 62 sysconf_reg_ptr->PLLCON = val | (1 << PLLCON_BIT_OFFSET_PLLRST); in arc_iot_pll_conf_reg() 63 sysconf_reg_ptr->PLLCON = val & (~(1 << PLLCON_BIT_OFFSET_PLLRST)); in arc_iot_pll_conf_reg() 65 while (!(sysconf_reg_ptr->PLLSTAT & (1 << PLLSTAT_BIT_OFFSET_PLLSTB))) { in arc_iot_pll_conf_reg() 69 sysconf_reg_ptr->CLKSEL = CLKSEL_PLL; in arc_iot_pll_conf_reg() [all …]
|
D | sysconf.h | 4 * SPDX-License-Identifier: Apache-2.0 41 volatile uint32_t DVFS_CLKDIV; /* DFSS main clock domain divider */ 152 extern void arc_iot_i2s_rx_clk_sel(uint8_t sel);
|
/Zephyr-latest/boards/nxp/mr_canhubk3/ |
D | mr_canhubk3.dts | 4 * SPDX-License-Identifier: Apache-2.0 7 /dts-v1/; 9 #include <dt-bindings/gpio/gpio.h> 10 #include <zephyr/dt-bindings/input/input-event-codes.h> 12 #include <dt-bindings/pwm/pwm.h> 13 #include "mr_canhubk3-pinctrl.dtsi" 14 #include <zephyr/dt-bindings/sensor/qdec_nxp_s32.h> 17 model = "NXP MR-CANHUBK3"; 25 zephyr,code-partition = &code_partition; 27 zephyr,shell-uart = &lpuart2; [all …]
|
/Zephyr-latest/tests/drivers/build_all/sensor/ |
D | i2c.dtsi | 4 * SPDX-License-Identifier: Apache-2.0 9 #include <zephyr/dt-bindings/sensor/lsm6dsv16x.h> 10 #include <zephyr/dt-bindings/sensor/lsm6dso.h> 11 #include <zephyr/dt-bindings/sensor/lsm6dso16is.h> 12 #include <zephyr/dt-bindings/sensor/lps22hh.h> 13 #include <zephyr/dt-bindings/sensor/lps2xdf.h> 14 #include <zephyr/dt-bindings/sensor/lis2ds12.h> 15 #include <zephyr/dt-bindings/sensor/lis2dw12.h> 16 #include <zephyr/dt-bindings/sensor/ism330dhcx.h> 17 #include <zephyr/dt-bindings/sensor/iis2dlpc.h> [all …]
|
/Zephyr-latest/doc/releases/ |
D | release-notes-3.3.rst | 14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery) 17 CMSIS-DSP as the default backend. 30 * CVE-2023-0359: Under embargo until 2023-04-20 32 * CVE-2023-0779: Under embargo until 2023-04-22 66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding. 71 * Starting from this release ``zephyr-`` prefixed tags won't be created 82 image states). Use of a truncated hash or non-sha256 hash will still work 88 registration function at boot-up. If applications register this then 93 application code, these will now automatically be registered at boot-up (this 129 This may cause out-of-tree scripts or commands to fail if they have relied [all …]
|