Home
last modified time | relevance | path

Searched +full:design +full:- +full:cap (Results 1 – 11 of 11) sorted by relevance

/Zephyr-latest/dts/bindings/sensor/
Dmaxim,max17262.yaml4 # SPDX-License-Identifier: Apache-2.0
11 include: [sensor-device.yaml, i2c-device.yaml]
14 design-voltage:
17 description: Battery Design Voltage in mV (3300 to 4400)
19 desired-voltage:
24 desired-charging-current:
27 description: Battery Design Charging Current in mA (e.g. 2000)
29 design-cap:
34 empty-voltage:
39 recovery-voltage:
[all …]
/Zephyr-latest/samples/sensor/max17262/
Dapp.overlay4 * SPDX-License-Identifier: Apache-2.0
13 design-voltage = <3600>;
14 desired-voltage = <3600>;
15 desired-charging-current = <2000>;
16 design-cap = <17000>;
17 empty-voltage = <3300>;
18 recovery-voltage = <3880>;
19 charge-voltage = <3600>;
/Zephyr-latest/drivers/sensor/
Dshell_battery.c4 * SPDX-License-Identifier: Apache-2.0
19 * first is the sensor channel to read (-1 to terminate the list)
36 if (chan == -1) { in get_channels()
55 struct sensor_value charge, v_desired, v_design, cap, nom_cap; in cmd_battery() local
63 return -ENODEV; in cmd_battery()
82 SENSOR_CHAN_GAUGE_FULL_CHARGE_CAPACITY, &cap, in cmd_battery()
86 -1); in cmd_battery()
95 shell_fprintf(sh, SHELL_NORMAL, "V-desired: %d.%02d V\n", in cmd_battery()
104 shell_fprintf(sh, SHELL_NORMAL, "I-desired: %5d mA\n", in cmd_battery()
110 shell_fprintf(sh, SHELL_NORMAL, "V-design: %d.%02d V\n", in cmd_battery()
[all …]
/Zephyr-latest/doc/_scripts/
Dredirects.py3 SPDX-License-Identifier: Apache-2.0
10 - Please keep this list sorted alphabetically.
11 - URLs must be relative to document root (with NO leading slash), and
16 # zephyr-keep-sorted-start
33 ('connectivity/bluetooth/api/audio/shell/cap', 'connectivity/bluetooth/shell/audio/cap'),
43 … ('connectivity/bluetooth/bluetooth-audio-arch', 'connectivity/bluetooth/bluetooth-le-audio-arch'),
44 …('connectivity/bluetooth/bluetooth-le-audio-arch', 'connectivity/bluetooth/api/audio/bluetooth-le-…
45 ('connectivity/bluetooth/cap', 'connectivity/bluetooth/api/audio/cap'),
47 ('connectivity/bluetooth/dis-pics', 'connectivity/bluetooth/bluetooth-qual'),
48 ('connectivity/bluetooth/gap-pics', 'connectivity/bluetooth/bluetooth-qual'),
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/api/audio/
Dbluetooth-le-audio-arch.rst13 {{{ GATT | GAP } | Low-level protocols (L2CAP, ATT, etc.)} | GAP | ISO}
18 Overall design
21 The overall design of the LE Audio stack is that the implementation follows the specifications
98 label="CAP";
169 HAS -> CAS;
170 PBS -> CAS;
171 TMAS -> CAS;
172 GMAS -> CAS;
174 CAS -> MCS;
175 CAS -> TBS;
[all …]
/Zephyr-latest/tests/drivers/build_all/sensor/
Di2c.dtsi4 * 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/
Dmigration-guide-3.7.rst22 out-of-tree SoCs and boards to be ported to the new model. See the
25 * The following build-time generated headers:
27 .. list-table::
28 :header-rows: 1
30 * - Affected header files
31 * - ``app_version.h``
32 * - ``autoconf.h``
33 * - ``cmake_intdef.h``
34 * - ``core-isa-dM.h``
35 * - ``devicetree_generated.h``
[all …]
Drelease-notes-3.5.rst38 * CVE-2023-3725 `Zephyr project bug tracker GHSA-2g3m-p6c7-8rr3
39 <https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-2g3m-p6c7-8rr3>`_
41 * CVE-2023-4257 `Zephyr project bug tracker GHSA-853q-q69w-gf5j
42 <https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-853q-q69w-gf5j>`_
44 * CVE-2023-4258 `Zephyr project bug tracker GHSA-m34c-cp63-rwh7
45 <https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-m34c-cp63-rwh7>`_
47 * CVE-2023-4259 `Zephyr project bug tracker GHSA-gghm-c696-f4j4
48 <https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-gghm-c696-f4j4>`_
50 * CVE-2023-4260 `Zephyr project bug tracker GHSA-gj27-862r-55wh
51 <https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-gj27-862r-55wh>`_
[all …]
Drelease-notes-3.1.rst61 * Split CAN classic and CAN-FD APIs:
90 was moved from Kconfig to :ref:`devicetree <dt-guide>`.
91 See the :dtcompatible:`st,stm32f1-pinctrl` devicetree binding for more information.
182 * MIPI-DSI
184 * Added a :ref:`MIPI-DSI api <mipi_dsi_api>`. This is an experimental API,
196 * Added support for enabling/disabling CAN-FD mode at runtime using :c:macro:`CAN_MODE_FD`.
220 * Added support for Provisioners over PB-GATT
231 * Implemented ISO-AL TX unframed fragmentation
232 * Added support for back-to-back receiving of PDUs on nRF5x platforms
249 newly created informational-only callback struct :c:struct:`bt_conn_auth_info_cb`.
[all …]
Drelease-notes-2.4.rst33 * CVE-2020-10060: UpdateHub Might Dereference An Uninitialized Pointer
34 * CVE-2020-10064: Improper Input Frame Validation in ieee802154 Processing
35 * CVE-2020-10066: Incorrect Error Handling in Bluetooth HCI core
36 * CVE-2020-10072: all threads can access all socket file descriptors
37 * CVE-2020-13598: FS: Buffer Overflow when enabling Long File Names in FAT_FS and calling fs_stat
38 * CVE-2020-13599: Security problem with settings and littlefs
39 * CVE-2020-13601: Under embargo until 2020/11/18
40 * CVE-2020-13602: Remote Denial of Service in LwM2M do_write_op_tlv
50 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
62 * The :c:func:`wdt_feed` function will now return ``-EAGAIN`` if
[all …]
Drelease-notes-3.3.rst14 * 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 …]