mirror of
https://github.com/lm-sensors/lm-sensors.git
synced 2026-11-06 15:51:34 +00:00
Cleanup a legacy comment that has been replicated to many drivers
but is no longer true. Backported from Linux 2.6. git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4328 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
1 parent
86da07df5b
commit
745df245fa
12 files changed
+12
-24
No files matched your search
@@ -143,8 +143,7 @@ static inline u8 FAN_TO_REG(long rpm, int div)
|
||||
#define VID_FROM_REG(val) ((val)==0x1f?0:(val)>=0x10?510-(val)*10:\
|
||||
205-(val)*5)
|
||||
|
||||
/* For each registered ADM1024, we need to keep some data in memory. That
|
||||
data is pointed to by adm1024_list[NR]->data. The structure itself is
|
||||
/* For each registered ADM1024, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new adm1024 client is
|
||||
allocated. */
|
||||
struct adm1024_data {
|
||||
|
||||
@@ -112,8 +112,7 @@ SENSORS_INSMOD_2(adm1025, ne1619);
|
||||
|
||||
#define ALARMS_FROM_REG(val) (val)
|
||||
|
||||
/* For each registered ADM1025, we need to keep some data in memory. That
|
||||
data is pointed to by adm1025_list[NR]->data. The structure itself is
|
||||
/* For each registered ADM1025, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new adm1025 client is
|
||||
allocated. */
|
||||
struct adm1025_data {
|
||||
|
||||
@@ -103,8 +103,7 @@ SENSORS_INSMOD_1(fscher);
|
||||
|
||||
/* Initial limits */
|
||||
|
||||
/* For each registered FSCHER, we need to keep some data in memory. That
|
||||
data is pointed to by fscher_list[NR]->data. The structure itself is
|
||||
/* For each registered FSCHER, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new fscher client is
|
||||
allocated. */
|
||||
struct fscher_data {
|
||||
|
||||
@@ -107,8 +107,7 @@ SENSORS_INSMOD_1(fscpos);
|
||||
|
||||
/* Initial limits */
|
||||
|
||||
/* For each registered FSCPOS, we need to keep some data in memory. That
|
||||
data is pointed to by fscpos_list[NR]->data. The structure itself is
|
||||
/* For each registered FSCPOS, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new fscpos client is
|
||||
allocated. */
|
||||
struct fscpos_data {
|
||||
|
||||
@@ -151,8 +151,7 @@ SENSORS_INSMOD_1(fscscy);
|
||||
|
||||
/* Initial limits */
|
||||
|
||||
/* For each registered FSCSCY, we need to keep some data in memory. That
|
||||
data is pointed to by fscscy_list[NR]->data. The structure itself is
|
||||
/* For each registered FSCSCY, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new fscscy client is
|
||||
allocated. */
|
||||
struct fscscy_data {
|
||||
|
||||
+1
-2
@@ -215,8 +215,7 @@ extern inline u8 DIV_TO_REG(long val)
|
||||
}
|
||||
#define DIV_FROM_REG(val) (1 << (val))
|
||||
|
||||
/* For each registered IT87, we need to keep some data in memory. That
|
||||
data is pointed to by it87_list[NR]->data. The structure itself is
|
||||
/* For each registered IT87, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new it87 client is
|
||||
allocated. */
|
||||
struct it87_data {
|
||||
|
||||
+1
-2
@@ -111,8 +111,7 @@ static inline u8 FAN_TO_REG(long rpm, int div)
|
||||
bad. Quite a lot of bookkeeping is done. A real driver can often cut
|
||||
some corners. */
|
||||
|
||||
/* For each registered LM78, we need to keep some data in memory. That
|
||||
data is pointed to by lm78_list[NR]->data. The structure itself is
|
||||
/* For each registered LM78, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new lm78 client is
|
||||
allocated. */
|
||||
struct lm78_data {
|
||||
|
||||
@@ -233,8 +233,7 @@ enum maxi_type { cristal, cognac, ashaki, nba };
|
||||
enum sensor_type { fan, temp, vid, pll, lcd, alarm };
|
||||
|
||||
/* For each registered MaxiLife controller, we need to keep some data in
|
||||
memory. That data is pointed to by maxi_list[NR]->data. The structure
|
||||
itself is dynamically allocated, at the same time when a new MaxiLife
|
||||
memory. It is dynamically allocated, at the same time when a new MaxiLife
|
||||
client is allocated. We assume MaxiLife will only be present on the
|
||||
SMBus and not on the ISA bus. */
|
||||
struct maxi_data {
|
||||
|
||||
@@ -54,8 +54,7 @@ SENSORS_INSMOD_1(mic74);
|
||||
/* Initial values */
|
||||
/* All registers are 0, except for MIC74_REG_DATA which is 0xFF */
|
||||
|
||||
/* For each registered MIC74, we need to keep some data in memory. That
|
||||
data is pointed to by mic74_list[NR]->data. The structure itself is
|
||||
/* For each registered MIC74, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new mic74 client is
|
||||
allocated. */
|
||||
struct mic74_data {
|
||||
|
||||
@@ -161,8 +161,7 @@ static inline u8 FAN_TO_REG(long rpm, int div)
|
||||
#define DIV_FROM_REG(val) (1 << (val))
|
||||
#define DIV_TO_REG(val) ((val)==8?3:(val)==4?2:(val)==1?0:1)
|
||||
|
||||
/* For the SIS5595, we need to keep some data in memory. That
|
||||
data is pointed to by sis5595_list[NR]->data. The structure itself is
|
||||
/* For the SIS5595, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the time when the new sis5595 client is
|
||||
allocated. */
|
||||
struct sis5595_data {
|
||||
|
||||
@@ -281,8 +281,7 @@ static inline u8 DIV_TO_REG(long val)
|
||||
return ((u8) i);
|
||||
}
|
||||
|
||||
/* For each registered chip, we need to keep some data in memory. That
|
||||
data is pointed to by w83627hf_list[NR]->data. The structure itself is
|
||||
/* For each registered chip, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new client is allocated. */
|
||||
struct w83627hf_data {
|
||||
struct i2c_client client;
|
||||
|
||||
@@ -246,8 +246,7 @@ static inline u8 DIV_TO_REG(long val, enum chips type)
|
||||
bad. Quite a lot of bookkeeping is done. A real driver can often cut
|
||||
some corners. */
|
||||
|
||||
/* For each registered W83781D, we need to keep some data in memory. That
|
||||
data is pointed to by w83781d_list[NR]->data. The structure itself is
|
||||
/* For each registered W83781D, we need to keep some data in memory. It is
|
||||
dynamically allocated, at the same time when a new w83781d client is
|
||||
allocated. */
|
||||
struct w83781d_data {
|
||||
|
||||
Reference in new issue
Block a user