Lines Matching +full:i2c +full:- +full:errors
3 Improved Inter-Integrated Circuit (I3C) Bus
6 I3C (Improved Inter-Integrated Circuit) is a two-signal shared
18 .. _i3c-controller-api:
36 .. code-block:: c
82 for example, at power-on. So it is a good idea to reset and
113 the assignment process and errors out.
133 #. Do ``ENEC`` to re-enable events from devices.
135 * The helper function, :c:func:`i3c_bus_init`, only re-enables
136 hot-join events. IBI event should only be enabled when
139 In-Band Interrupt (IBI)
142 If a target device can generate In-Band Interrupt (IBI),
173 .. code-block:: devicetree
178 #address-cells = < 0x3 >;
179 #size-cells = < 0x0 >;
184 pinctrl-0 = < &pinmux-i3c >;
185 pinctrl-names = "default";
187 i2c-scl-hz = < 400000 >;
189 i3c-scl-hz = < 12000000 >;
193 i3c-dev0: i3c-dev0@420000ABCD12345678 {
194 compatible = "vendor,i3c-dev";
201 i2c-dev0: i2c-dev0@380000000000000050 {
202 compatible = "vendor-i2c-dev";
211 -----------
220 * If non-zero and property ``assigned-address`` is not set,
224 * Second element is the upper 16-bit of the Provisioned ID (PID)
225 which contains the manufacturer ID left-shifted by 1. This is
226 the bits 33-47 (zero-based) of the 48-bit Provisioned ID.
228 * Third element contains the lower 32-bit of the Provisioned ID
229 which is a combination of the part ID (left-shifted by 16,
230 bits 16-31 of the PID) and the instance ID (left-shifted by 12,
231 bits 12-15 of the PID).
233 Note that the unit-address (the part after ``@``) must match
235 32-bit integer, combining to form a 96-bit integer. This is
239 ----------------------
285 Similar to I3C devices, the unit-address must match the ``reg``
286 property fully where each element is treated as 32-bit integer,
287 combining to form a 96-bit integer.
307 API can accommodate I2C API calls without modifications if the controller
308 device driver implements the I2C API. This has the advantage of using
309 existing I2C devices without any modifications to their device drivers.
311 any calls to I2C API will need to look up the corresponding device
312 descriptor from the I2C device address. This adds a bit of processing
313 cost to any I2C API calls.
316 I2C device support via the I3C controller API. During device
322 the I2C device must be declared according to I3C standard:
326 device drivers can be used as-is without modifications. This requires
329 .. code-block:: devicetree
335 i2c-dev0: i2c-dev0@420000000000000050 {
336 compatible = "vendor-i2c-dev";
363 .. _I3C Specification: https://www.mipi.org/specifications/i3c-sensor-specification