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
94 * struct i3c_ibi_slot - I3C IBI (In-Band Interrupt) slot
97 * @dev: the I3C device that has generated this IBI
103 * Every time an IBI comes in, the I3C master driver should find a free IBI
107 * How IBI slots are allocated is left to the I3C master driver, though, for
136 * New I3C messages can be sent from the IBI handler
140 * object is here to manage IBIs coming from a specific I3C device.
143 * infrastructure. I3C master drivers may have their own internal
158 * struct i3c_dev_boardinfo - I3C device board information
159 * @node: used to insert the boardinfo object in the I3C boardinfo list
164 * @static_addr: static address the I3C device listen on before it's been
168 * @pid: I3C Provisional ID exposed by the device. This is a unique identifier
173 * This structure is used to attach board-level information to an I3C device.
174 * Not all I3C devices connected on the bus will have a boardinfo. It's only
187 * struct i3c_dev_desc - I3C device descriptor
188 * @common: common part of the I3C device descriptor
189 * @info: I3C device information. Will be automatically filled when you create
194 * @dev: pointer to the I3C device object exposed to I3C device drivers. This
195 * should never be accessed from I3C master controller drivers. Only core
198 * @boardinfo: pointer to the boardinfo attached to this I3C device
200 * Internal representation of an I3C device. This object is only used by the
201 * core and passed to I3C master controller drivers when they're requested to
203 * The core maintains the link between the internal I3C dev descriptor and the
204 * object exposed to the I3C device drivers (&struct_i3c_device).
216 * struct i3c_device - I3C device object
217 * @dev: device object to register the I3C dev to the device model
218 * @desc: pointer to an i3c device descriptor object. This link is updated
219 * every time the I3C device is rediscovered with a different dynamic
221 * @bus: I3C bus this device is attached to
223 * I3C device object exposed to I3C device drivers. The takes care of linking
225 * All I3C devs on the I3C bus are represented, including I3C masters. For each
235 * The I3C specification says the maximum number of devices connected on the
238 * I3C master can also have limitations, so this number is just here as a
250 * enum i3c_bus_mode - I3C bus mode
251 * @I3C_BUS_MODE_PURE: only I3C devices are connected to the bus. No limitation
256 * devices when transmitting I3C frames
272 * enum i3c_addr_slot_status - I3C address slot status
276 * @I3C_ADDR_SLOT_I3C_DEV: address is assigned to an I3C device
279 * On an I3C bus, addresses are assigned dynamically, and we need to know which
282 * Addresses marked as reserved are those reserved by the I3C protocol
294 * struct i3c_bus - I3C bus object
295 * @cur_master: I3C master currently driving the bus. Since I3C is multi-master
304 * @scl_rate.i3c: maximum rate for the clock signal when doing I3C SDR/priv
307 * @scl_rate: SCL signal rate for I3C and I2C mode
308 * @devs.i3c: contains a list of I3C device descriptors representing I3C
310 * I3C master
313 * I3C master
314 * @devs: 2 lists containing all I3C/I2C devices connected to the bus
319 * to send I3C frames to these devices.
321 * devices: several drivers can send different I3C/I2C frames through
326 * The I3C bus is represented with its own object and not implicitly described
327 * by the I3C master to cope with the multi-master functionality, where one bus
337 unsigned long i3c; member
341 struct list_head i3c; member
348 * struct i3c_master_controller_ops - I3C master methods
349 * @bus_init: hook responsible for the I3C bus initialization. You should at
356 * @attach_i3c_dev: called every time an I3C device is attached to the bus. It
363 * data to I3C devices.
365 * @reattach_i3c_dev: called every time an I3C device has its addressed
371 * @detach_i3c_dev: called when an I3C device is detached from the bus. Usually
386 * @priv_xfers: do one or several private I3C SDR transfers
395 * @i2c_xfers: do one or several I2C transfers. Note that, unlike i3c
402 * @request_ibi: attach an IBI handler to an I3C device. This implies defining
416 * to the I3C device.
457 * struct i3c_master_controller - I3C master controller object
459 * @this: an I3C device object representing this master. This device will be
460 * added to the list of I3C devs available on the bus
467 * @boardinfo.i3c: list of I3C boardinfo objects
470 * @bus: I3C bus exposed by this master
477 * A &struct i3c_master_controller has to be registered to the I3C subsystem
490 struct list_head i3c; member
499 * @bus: the I3C bus
509 * i3c_bus_for_each_i3cdev() - iterate over all I3C devices present on the bus
510 * @bus: the I3C bus
511 * @dev: and I3C device descriptor pointer updated to point to the current slot
514 * Iterate over all I3C devs present on the bus.
517 list_for_each_entry(dev, &(bus)->devs.i3c, common.node)
547 * i3c_dev_get_master_data() - get master private data attached to an I3C
549 * @dev: the I3C device descriptor to get private data from
560 * i3c_dev_set_master_data() - attach master private data to an I3C device
562 * @dev: the I3C device descriptor to attach private data to
604 * @dev: I3C dev
630 * Return: the I3C bus @master is connected to