Lines Matching +full:pcs +full:- +full:handle

19 it for non-exported symbols too. We will use the prefix ``foo_`` in this
28 routines, and should be zero-initialized except for fields with data you
29 provide.  A client structure holds device-specific information like the
62 All other fields are for call-back functions which will be explained
70 structure at all.  You should use this to keep device-specific data.
81 to NULL in remove() or if probe() failed anymore. The i2c-core does this
95 but many chips have some kind of register-value idea that can easily
103 	if (reg < 0x10)	/* byte-sized register */
105 	else		/* word-sized register */
111 	if (reg == 0x10)	/* Impossible to write - driver error! */
112 		return -EINVAL;
113 	else if (reg < 0x10)	/* byte-sized register */
115 	else			/* word-sized register */
125 that were more appropriate to SMBus (and PCs) than to I2C.  One of these
139 ---------------------
141 System infrastructure, typically board-specific initialization code or
144 and linking them to board-specific configuration information about IRQs
158 handle may be used during foo_probe().  If foo_probe() reports success
159 (zero not a negative status code) it may save the handle and use it until
172 ---------------
200 ----------------
204 (typically using device-specific, dedicated identification registers),
216 ---------------
265   /* a few non-GPL license types are also allowed */
273 power state -- like putting a transceiver into a low power mode, or
274 activating a system wakeup mechanism -- do that by implementing the
289 or reboots (including kexec) -- like turning something off -- use a
300 A generic ioctl-like function call back is supported. You will seldom
317 -----------------------
343 You can read the file i2c-protocol.rst for more information about the
348 -------------------
379 These ones were removed from i2c-core because they had no users, but could
393 You can read the file smbus-protocol.rst for more information about the