Lines Matching +full:single +full:- +full:chip

10 ----------
14     - Documentation/process/submit-checklist.rst
15     - Documentation/process/submitting-patches.rst
16     - Documentation/process/coding-style.rst
18 * Please run your patch through 'checkpatch --strict'. There should be no
22 * Please use the standard multi-line comment style. Do not mix C and C++
23   style comments in a single driver (with the exception of the SPDX license
34   hardware. In such cases, you should test-build the code on at least one
35   architecture. If run-time testing was not achieved, it should be written
43 -------------------------------------------
54 * Never mix bug fixes, cleanup, and functional enhancements in a single patch.
58 --------------
82 * Avoid calculations in macros and macro-generated functions. While such macros
95   and supported functions, please see Documentation/driver-api/driver-model/devres.rst.
100   must not print messages such as "Chip XXX not found/supported".
103   address if a chip is detected on that address. Unnecessary messages will just
106 * Provide a detect function if and only if a chip can be detected reliably.
108 * Only the following I2C addresses shall be probed: 0x18-0x1f, 0x28-0x2f,
109   0x48-0x4f, 0x58, 0x5c, 0x73 and 0x77. Probing other addresses is strongly
110   discouraged as it is known to cause trouble with other (non-hwmon) I2C
111   chips. If your chip lives at an address which can't be probed then the
115 * Avoid writing to chip registers in the detect function. If you have to write,
119   Keep in mind that the chip might not be what your driver believes it is, and
123   completely initialize your chip and your driver first, then register with
136 * Do not create non-standard attributes unless really needed. If you have to use
137   non-standard attributes, or you believe you do, discuss it on the mailing list
139   non-standard attribute(s).
140   Standard attributes are specified in Documentation/hwmon/sysfs-interface.rst.
142 * When deciding which sysfs attributes to support, look at the chip's
144   chip may offer, it should at least support all limits and alarms.
146 * Last but not least, please check if a driver for your chip already exists
149   a presumably new chip may simply have been relabeled.