Lines Matching refs:parameter

194 You do not have to use this parameter interface; but don't try to use
214    probe: insmod parameter. 
218    probe_range: insmod parameter. 
222    ignore: insmod parameter.
225      This parameter overrules 'normal' and 'probe', but not the 'force' lists.
226    ignore_range: insmod parameter. 
230      This parameter overrules 'normal' and 'probe', but not the 'force' lists.
231    force: insmod parameter. 
273      modulo parameter: only addresses which are 0 module this value relative
275    probe: insmod parameter. Initialize this list with SENSORS_I2C_END values.
279    probe_range: insmod parameter. Initialize this list with SENSORS_I2C_END 
285    ignore: insmod parameter. Initialize this list with SENSORS_I2C_END values.
288      addresses are never probed. This parameter overrules 'normal' and 
290    ignore_range: insmod parameter. Initialize this list with SENSORS_I2C_END 
295      This parameter overrules 'normal' and 'probe', but not the 'force' lists.
361 them (unless a `force' parameter was used). In addition, addresses that
369 The `kind' parameter contains 0 if this call is due to a `force'
370 parameter, and -1 otherwise (for i2c_detect, it contains 0 if
371 this call is due to the generic `force' parameter, and the chip type
372 number if it is due to a specific `force' parameter).
382 For now, you can ignore the `flags' parameter. It is there for future use.
419       if (kind < 0) /* Only if no force parameter was used */ {
467     /* Now, we do the remaining detection. If no `force' parameter is used. */
470        parameter was used. */
482     /* Determine the chip type. Not needed if a `force_CHIPTYPE' parameter
491         printk("foo: Ignoring 'force' parameter for unknown chip at "
689 parameter contains the bytes the read/write, the third the length of the
795 Finally, the last parameter is the call-back to gather the data
803 can be called in several ways; the operation parameter determines