diff options
| author | Andrea Merello <[email protected]> | 2019-09-12 16:43:07 +0200 |
|---|---|---|
| committer | Jonathan Cameron <[email protected]> | 2019-09-15 11:25:21 +0100 |
| commit | c270bbf7bb9ddc4e2a51b3c56557c377c9ac79bc (patch) | |
| tree | 1f20738fbd8841dccc9fd821003de177933004a7 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 5a56c518c4d22c2b909eff6b18c7e40e1642c53d (diff) | |
iio: ad7949: kill pointless "readback"-handling code
The device could be configured to spit out also the configuration word
while reading the AD result value (in the same SPI xfer) - this is called
"readback" in the device datasheet.
The driver checks if readback is enabled and it eventually adjusts the SPI
xfer length and it applies proper shifts to still get the data, discarding
the configuration word.
The readback option is actually never enabled (the driver disables it), so
the said checks do not serve for any purpose.
Since enabling the readback option seems not to provide any advantage (the
driver entirely sets the configuration word without relying on any default
value), just kill the said, unused, code.
Signed-off-by: Andrea Merello <[email protected]>
Reviewed-by: Alexandru Ardelean <[email protected]>
Signed-off-by: Jonathan Cameron <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions