ad525x_dpot: use correct rdac channel for ad5251/ad5252
The ad5251/ad5252 devices have rdac1 and rdac3, but no rdac0. So make sure we use the right channels so userspace gets correct data and not just garbage. Signed-off-by: steven miao <realmz6@gmail.com> Signed-off-by: Mike Frysinger <vapier@gentoo.org> Cc: Michael Hennerich <michael.hennerich@analog.com> Cc: Chris Verges <chrisv@cyberswitching.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
a4bd394956
commit
4b068de9ab
|
@ -47,9 +47,9 @@ enum dpot_devid {
|
|||
AD5258_ID = DPOT_CONF(F_RDACS_RW_TOL, BRDAC0, 6, 0), /* I2C */
|
||||
AD5259_ID = DPOT_CONF(F_RDACS_RW_TOL, BRDAC0, 8, 1),
|
||||
AD5251_ID = DPOT_CONF(F_RDACS_RW_TOL | F_CMD_INC,
|
||||
BRDAC0 | BRDAC3, 6, 2),
|
||||
BRDAC1 | BRDAC3, 6, 2),
|
||||
AD5252_ID = DPOT_CONF(F_RDACS_RW_TOL | F_CMD_INC,
|
||||
BRDAC0 | BRDAC3, 8, 3),
|
||||
BRDAC1 | BRDAC3, 8, 3),
|
||||
AD5253_ID = DPOT_CONF(F_RDACS_RW_TOL | F_CMD_INC,
|
||||
BRDAC0 | BRDAC1 | BRDAC2 | BRDAC3, 6, 4),
|
||||
AD5254_ID = DPOT_CONF(F_RDACS_RW_TOL | F_CMD_INC,
|
||||
|
|
Loading…
Reference in New Issue
Block a user