Home
last modified time | relevance | path

Searched full:bc1 (Results 1 – 11 of 11) sorted by relevance

/Zephyr-latest/include/zephyr/drivers/usb/
Dusb_bc12.h9 * @brief Public APIs for the USB BC1.2 battery charging detect drivers.
22 * @brief BC1.2 driver APIs
23 * @defgroup b12_interface BC1.2 driver APIs
31 * @name BC1.2 constants
35 /** BC1.2 USB charger voltage. */
38 * BC1.2 USB charger minimum current. Set to match the Isusp of 2.5 mA parameter.
39 * This is returned by the driver when either BC1.2 detection fails, or the
49 /** BC1.2 USB charger maximum current. */
55 * @brief Helper macro for setting a BC1.2 current limit
58 * @return A valid BC1.2 current limit, in uA, clamped between the BC1.2 minimum
[all …]
Demul_bc12.h9 * @brief Backend APIs for the BC1.2 emulators.
23 * @brief BC1.2 backend emulator APIs
24 * @defgroup b12_emulator_backend BC1.2 backed emulator APIs
43 * @brief Set the charging partner type connected to the BC1.2 device.
45 * The corresponding BC1.2 emulator updates the vendor specific registers
49 * @param target Pointer to the emulator structure for the BC1.2 emulator instance.
68 * The corresponding BC1.2 emulator updates the vendor specific registers
73 * @param target Pointer to the emulator structure for the BC1.2 emulator instance.
/Zephyr-latest/doc/hardware/peripherals/
Dbc12.rst3 BC1.2 Devices (Experimental)
7 referred to as just BC1.2. BC1.2 defines limits and detection mechanisms for USB
10 The BC1.2 specification uses the term Charging Port for the device that supplies
14 Note that the `BC1.2 Specification`_ uses the acronym PD for Portable Device. This
18 On many devices, BC1.2 is the fallback mechanism to determine the connected
22 Key parameters from the `BC1.2 Specification`_ include:
35 While the ICDP and IDCP rated currents go up to 5.0 A, the BC1.2 current is
36 limited by the IDEV_CHG parameter. So the BC1.2 support is capped at 1.5 A in
44 The BC1.2 device driver provides only two APIs, ``bc12_set_role()`` and
47 The application calls ``bc12_set_role()`` to transition the BC1.2 device to
[all …]
/Zephyr-latest/drivers/usb/bc12/
DKconfig5 bool "USB BC1.2 Drivers"
7 Enable USB BC1.2 (battery charging detection) drivers.
DKconfig.pi3usb920111 1.2 (BC1.2) with Standard/Charging/Dedicated downstream port
13 client mode it starts BC1.2 detection to detect the attached host
38 operating in CDP mode. Note that the BC1.2 negotiation compeletes
Dbc12_pi3usb9201.c69 /* BC1.2 driver contract specifies to return Isusp for SDP ports. */
209 * @brief Notify the application about changes to the BC1.2 partner.
211 * @param dev BC1.2 device instance
241 * are cleared prior to starting bc1.2 detection. in pi3usb9201_client_detect_start()
251 /* Have pi3usb9201 start bc1.2 detection */ in pi3usb9201_client_detect_start()
284 /* bc1.2 is complete and start bit does not auto clear */ in pi3usb9201_client_detect_finish()
369 /* The start bc1.2 bit does not auto clear */ in pi3usb9201_disconnect()
375 /* Mask interrupts until next bc1.2 detection event */ in pi3usb9201_disconnect()
404 * VBUS is present, but starting bc1.2 detection failed in pi3usb9201_set_portable_device()
414 LOG_ERR("bc1.2 detection failed, using defaults"); in pi3usb9201_set_portable_device()
[all …]
/Zephyr-latest/tests/drivers/usb/bc12/src/
Dpd_mode.c12 * @brief TestPurpose: Verify BC1.2 devices in portable device mode.
75 /* Report to the BC1.2 driver that VBUS is present */ in ZTEST_USER_F()
84 * The BC1.2 driver contract specifies to set the current to Isusp in ZTEST_USER_F()
85 * for SDP ports or when BC1.2 detection fails. in ZTEST_USER_F()
97 /* Report to the BC1.2 driver that VBUS is no longer present */ in ZTEST_USER_F()
102 /* The BC1.2 driver should invoke the callback on disconnects */ in ZTEST_USER_F()
127 /* Report to the BC1.2 driver that VBUS is no longer present */ in ZTEST_USER_F()
132 /* The BC1.2 driver should invoke the callback on disconnects */ in ZTEST_USER_F()
163 /* The BC1.2 driver should invoke the callback once to report the new state. */ in ZTEST_USER_F()
Dcharging_mode.c12 * @brief TestPurpose: Verify BC1.2 devices configured in charging mode.
60 /* The BC1.2 driver should invoke the callback on plug event */ in ZTEST_USER_F()
66 /* The BC1.2 driver should invoke the callback on unplug event */ in ZTEST_USER_F()
/Zephyr-latest/doc/hardware/emulator/
Dbus_emulators.rst96 ``_backend_api`` using the BC1.2 charging detector driver as the model
101 :alt: Device class example, demonstrating BC1.2 charging detectors.
105 The ``bus_api`` connects the BC1.2 emulators to the ``native_sim`` I2C
106 controller. The real BC1.2 drivers are unchanged and operate exactly as if there
116 In the case of the BC1.2 charging detector the backend API provides functions
117 to simulate connecting and disconnecting a charger to the emulated BC1.2 device.
123 #. Test registers BC1.2 detection callback using the Zephyr BC1.2 driver API.
124 #. Test connects a charger using the BC1.2 emulator backend.
126 #. Test disconnects a charger using the BC1.2 emulator backend.
/Zephyr-latest/dts/bindings/usb/
Dusb-bc12.yaml4 # Common fields for USB BC1.2 devices
13 Define the charging port mode supported by the BC1.2 device.
/Zephyr-latest/doc/hardware/emulator/img/
Ddevice_class_emulator.svg4 …BC1.2 Driver API</div></div></div></foreignObject><text x="116" y="131" fill="rgb(0, 0, 0)" font-f…