Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 170
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 12 7月, 2015 1 次提交
  3. 29 6月, 2015 1 次提交
  5. 14 6月, 2015 1 次提交
  7. 08 6月, 2015 3 次提交
  9. 23 5月, 2015 3 次提交
  11. 14 5月, 2015 1 次提交
  13. 13 5月, 2015 3 次提交
  15. 11 5月, 2015 1 次提交
  17. 08 5月, 2015 1 次提交
    • N
      iio: adc: cc10001: Fix the channel number mapping · 13415a99
      由 Naidu Tellapati 提交于 
      When some of the ADC channels are reserved for remote CPUs,
the scan index and the corresponding channel number doesn't
match. This leads to convesion on the incorrect channel during
triggered capture.

Fix this by using a scan index to channel mapping encoded
in the iio_chan_spec for this purpose while starting conversion
on a particular ADC channel in trigger handler.

Also, the channel_map is not really used anywhere but in probe(), so
no need to keep track of it. Remove it from device structure.

While here, add 1 to number of channels to register timestamp channel
with the IIO core.

Fixes: 1664f6a5 ("iio: adc: Cosmic Circuits 10001 ADC driver")
Signed-off-by: NNaidu Tellapati <naidu.tellapati@imgtec.com>
Signed-off-by: NEzequiel Garcia <ezequiel.garcia@imgtec.com>
Cc: <Stable@vger.kernel.org>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>
      13415a99
  19. 07 5月, 2015 1 次提交
  21. 19 4月, 2015 5 次提交
  23. 10 4月, 2015 1 次提交
    • J
      iio/axp288_adc: add missing channel info mask · d0716b0e
      由 Jacob Pan 提交于 
      Commit 65de7654 ("iio: iio: Fix iio_channel_read return if
channel havn't info") added a check for valid info masks.

This patch adds missing channel info masks for all ADC channels.
Otherwise, iio_read_channel_raw() would return -EINVAL when called
by consumer drivers.

Note that the change of _processed to _raw actually fixes an ABI abuse
in the original driver where it was used to avoid some special handling
rather than because it was correct.
Signed-off-by: NJacob Pan <jacob.jun.pan@linux.intel.com>
Cc: <Stable@vger.kernel.org>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>
      d0716b0e
  25. 09 4月, 2015 1 次提交
  27. 28 3月, 2015 2 次提交
    • S
      iio: adc: vf610: use ADC clock within specification · f54e9f2b
      由 Stefan Agner 提交于 
      Depending on conversion mode used, the ADC clock (ADCK) needs
to be below a maximum frequency. According to Vybrid's data
sheet this is 20MHz for the low power conversion mode.

The ADC clock is depending on input clock, which is the bus
clock by default. Vybrid SoC are typically clocked at at 400MHz
or 500MHz, which leads to 66MHz or 83MHz bus clock respectively.
Hence, a divider of 8 is required to stay below the specified
maximum clock of 20MHz.

Due to the different bus clock speeds, the resulting sampling
frequency is not static. Hence use the ADC clock and calculate
the actual available sampling frequency dynamically.

This fixes bogous values observed on some 500MHz clocked Vybrid
SoC. The resulting value usually showed Bit 9 being stuck at 1,
or 0, which lead to a value of +/-512.
Signed-off-by: NStefan Agner <stefan@agner.ch>
Acked-by: NFugang Duan <B38611@freescale.com>
Cc: <Stable@vger.kernel.org>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>
      f54e9f2b
    • R
      iio/adc/cc10001_adc.c: Fix !HAS_IOMEM build · bbc45f3a
      由 Richard Weinberger 提交于 
      Fixes:
drivers/built-in.o: In function `cc10001_adc_probe':
cc10001_adc.c:(.text+0x412e92): undefined reference to `devm_ioremap_resource'
Signed-off-by: NRichard Weinberger <richard@nod.at>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>
      bbc45f3a
  29. 12 3月, 2015 1 次提交
  31. 08 3月, 2015 2 次提交
  33. 07 3月, 2015 1 次提交
  35. 26 2月, 2015 1 次提交
  37. 05 2月, 2015 2 次提交
  39. 04 2月, 2015 1 次提交
  41. 30 1月, 2015 1 次提交
  43. 29 1月, 2015 1 次提交
  45. 10 1月, 2015 1 次提交
  47. 26 12月, 2014 1 次提交
  49. 12 12月, 2014 2 次提交
    • L
      iio: ad799x: Fix ad7991/ad7995/ad7999 config setup · 2eacc608
      由 Lars-Peter Clausen 提交于 
      The ad7991/ad7995/ad7999 does not have a configuration register like the
other devices that can be written and read. The configuration is written as
part of the conversion sequence.

Fixes: 0f7ddcc1 ("iio:adc:ad799x: Write default config on probe and reset alert status on probe")
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Tested-by: NMike Looijmans <mike.looijmans@topic.nl>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>
      2eacc608
    • L
      iio: Move buffer registration to the core · 3e1b6c95
      由 Lars-Peter Clausen 提交于 
      Originally device and buffer registration were kept as separate operations
in IIO to allow to register two distinct sets of channels for buffered and
non-buffered operations. This has since already been further restricted and
the channel set registered for the buffer needs to be a subset of the
channel set registered for the device. Additionally the possibility to not
have a raw (or processed) attribute for a channel which was registered for
the device was added a while ago. This means it is possible to not register
any device level attributes for a channel even if it is registered for the
device. Also if a channel's scan_index is set to -1 and the channel is
registered for the buffer it is ignored.

So in summary it means it is possible to register the same channel array for
both the device and the buffer yet still end up with distinctive sets of
channels for both of them. This makes the argument for having to have to
manually register the channels for both the device and the buffer invalid.
Considering that the vast majority of all drivers want to register the same
set of channels for both the buffer and the device it makes sense to move
the buffer registration into the core to avoid some boiler-plate code in the
device driver setup path.
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>
      3e1b6c95
  51. 18 11月, 2014 1 次提交