Re: [PATCH 2.6.32 to 3.7] staging: comedi: cb_pcidas64: fix incorrect AI range code handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2015/2/28 2:52, Ian Abbott wrote:
> commit be8e89087ec2d2c8a1ad1e3db64bf4efdfc3c298 upstream.
> 
> The hardware range code values and list of valid ranges for the AI
> subdevice is incorrect for several supported boards.  The hardware range
> code values for all boards except PCI-DAS4020/12 is determined by
> calling `ai_range_bits_6xxx()` based on the maximum voltage of the range
> and whether it is bipolar or unipolar, however it only returns the
> correct hardware range code for the PCI-DAS60xx boards.  For
> PCI-DAS6402/16 (and /12) it returns the wrong code for the unipolar
> ranges.  For PCI-DAS64/Mx/16 it returns the wrong code for all the
> ranges and the comedi range table is incorrect.
> 
> Change `ai_range_bits_6xxx()` to use a look-up table pointed to by new
> member `ai_range_codes` of `struct pcidas64_board` to map the comedi
> range table indices to the hardware range codes.  Use a new comedi range
> table for the PCI-DAS64/Mx/16 boards (and the commented out variants).
> 
> Signed-off-by: Ian Abbott <abbotti@xxxxxxxxx>
> Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>

Queued up for 3.4. Thanks!
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]