Lines Matching full:i3c
15 #include <linux/i3c/ccc.h>
16 #include <linux/i3c/device.h>
31 * struct i3c_i2c_dev_desc - Common part of the I3C/I2C device descriptor
32 * @node: node element used to insert the slot into the I2C or I3C device
34 * @master: I3C master that instantiated this device. Will be used to do
35 * I2C/I3C transfers
39 * This structure is describing common I3C/I2C dev information.
57 * @lvr: LVR (Legacy Virtual Register) needed by the I3C core to know about
61 * Each I2C device connected on the I3C bus should have one.
75 * @lvr: LVR (Legacy Virtual Register) needed by the I3C core to know about
83 * connected on an I3C bus. This object is also passed to all
95 * struct i3c_ibi_slot - I3C IBI (In-Band Interrupt) slot
98 * @dev: the I3C device that has generated this IBI
104 * Every time an IBI comes in, the I3C master driver should find a free IBI
108 * How IBI slots are allocated is left to the I3C master driver, though, for
137 * New I3C messages can be sent from the IBI handler
141 * object is here to manage IBIs coming from a specific I3C device.
144 * infrastructure. I3C master drivers may have their own internal
159 * struct i3c_dev_boardinfo - I3C device board information
160 * @node: used to insert the boardinfo object in the I3C boardinfo list
165 * @static_addr: static address the I3C device listen on before it's been
169 * @pid: I3C Provisional ID exposed by the device. This is a unique identifier
174 * This structure is used to attach board-level information to an I3C device.
175 * Not all I3C devices connected on the bus will have a boardinfo. It's only
188 * struct i3c_dev_desc - I3C device descriptor
189 * @common: common part of the I3C device descriptor
190 * @info: I3C device information. Will be automatically filled when you create
195 * @dev: pointer to the I3C device object exposed to I3C device drivers. This
196 * should never be accessed from I3C master controller drivers. Only core
199 * @boardinfo: pointer to the boardinfo attached to this I3C device
201 * Internal representation of an I3C device. This object is only used by the
202 * core and passed to I3C master controller drivers when they're requested to
204 * The core maintains the link between the internal I3C dev descriptor and the
205 * object exposed to the I3C device drivers (&struct_i3c_device).
217 * struct i3c_device - I3C device object
218 * @dev: device object to register the I3C dev to the device model
219 * @desc: pointer to an i3c device descriptor object. This link is updated
220 * every time the I3C device is rediscovered with a different dynamic
222 * @bus: I3C bus this device is attached to
224 * I3C device object exposed to I3C device drivers. The takes care of linking
226 * All I3C devs on the I3C bus are represented, including I3C masters. For each
236 * The I3C specification says the maximum number of devices connected on the
239 * I3C master can also have limitations, so this number is just here as a
251 * enum i3c_bus_mode - I3C bus mode
252 * @I3C_BUS_MODE_PURE: only I3C devices are connected to the bus. No limitation
257 * devices when transmitting I3C frames
273 * enum i3c_addr_slot_status - I3C address slot status
277 * @I3C_ADDR_SLOT_I3C_DEV: address is assigned to an I3C device
280 * On an I3C bus, addresses are assigned dynamically, and we need to know which
283 * Addresses marked as reserved are those reserved by the I3C protocol
295 * struct i3c_bus - I3C bus object
296 * @cur_master: I3C master currently driving the bus. Since I3C is multi-master
305 * @scl_rate.i3c: maximum rate for the clock signal when doing I3C SDR/priv
308 * @scl_rate: SCL signal rate for I3C and I2C mode
309 * @devs.i3c: contains a list of I3C device descriptors representing I3C
311 * I3C master
314 * I3C master
315 * @devs: 2 lists containing all I3C/I2C devices connected to the bus
320 * to send I3C frames to these devices.
322 * devices: several drivers can send different I3C/I2C frames through
327 * The I3C bus is represented with its own object and not implicitly described
328 * by the I3C master to cope with the multi-master functionality, where one bus
338 unsigned long i3c; member
342 struct list_head i3c; member
349 * struct i3c_master_controller_ops - I3C master methods
350 * @bus_init: hook responsible for the I3C bus initialization. You should at
357 * @attach_i3c_dev: called every time an I3C device is attached to the bus. It
364 * data to I3C devices.
366 * @reattach_i3c_dev: called every time an I3C device has its addressed
372 * @detach_i3c_dev: called when an I3C device is detached from the bus. Usually
387 * @priv_xfers: do one or several private I3C SDR transfers
396 * @i2c_xfers: do one or several I2C transfers. Note that, unlike i3c
403 * @request_ibi: attach an IBI handler to an I3C device. This implies defining
417 * to the I3C device.
458 * struct i3c_master_controller - I3C master controller object
460 * @this: an I3C device object representing this master. This device will be
461 * added to the list of I3C devs available on the bus
468 * @boardinfo.i3c: list of I3C boardinfo objects
471 * @bus: I3C bus exposed by this master
478 * A &struct i3c_master_controller has to be registered to the I3C subsystem
491 struct list_head i3c; member
500 * @bus: the I3C bus
510 * i3c_bus_for_each_i3cdev() - iterate over all I3C devices present on the bus
511 * @bus: the I3C bus
512 * @dev: and I3C device descriptor pointer updated to point to the current slot
515 * Iterate over all I3C devs present on the bus.
518 list_for_each_entry(dev, &(bus)->devs.i3c, common.node)
548 * i3c_dev_get_master_data() - get master private data attached to an I3C
550 * @dev: the I3C device descriptor to get private data from
561 * i3c_dev_set_master_data() - attach master private data to an I3C device
563 * @dev: the I3C device descriptor to attach private data to
605 * @dev: I3C dev
631 * Return: the I3C bus @master is connected to