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

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