- 30 Jan, 2013 3 commits
-
-
H Hartley Sweeten authored
Move some of the functions to remove the need for the forward declarations. Signed-off-by:
H Hartley Sweeten <hsweeten@visionengravers.com> Cc: Ian Abbott <abbotti@mev.co.uk> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
H Hartley Sweeten authored
For aesthetic reasons, reorder the pcmcia_driver variables and add some whitespace. Signed-off-by:
-
H Hartley Sweeten authored
For aesthetic reasons, move all the MODULE_* information to the end of the file. Signed-off-by:
-
- 29 Jan, 2013 1 commit
-
-
Greg Kroah-Hartman authored
Merge tag 'iio-for-3.9b-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next Jonathan writes: Second set of IIO new drivers, cleanups and fixes for the 3.9 cycle. This second version is due to a little fixup for an include path being added to the tsl2563 move out of staging after a report from Fengguang Wu and the 0-day kernel build testing backend. Minor bits: 1) A Kconfig dependency fix for the max1363 driver that has been causing some autobuilder fails in Linux Next. 2) Removal of a stale makefile entry 3) Fix an incorrect arguement for a sizeof call 4) Duplicate code removal in tsl2x7x driver 5) A missing spin lock init in hid-sensor-time New features: 1) mxs adc driver gains support for touchscreen special functions 2) mxs driver gainst supprot for the MX23 and dt entries added 3) adis16400 gains adis16448 support and some additional bells and whistles Moves out of staging. 1) adis16400 - a venerable driver gets a make over and moves out of staging. 2) Kxsd9 moved out fo staging 3) adis16080 gets cleaned up and moved out of staging 4) tsl2563 gets a little cleaned up and move out of staging Removals 1) sw_ring is killed off with all remaining drivers converted to kfifo. This has been scheduled for a long time since we switched to kfifo. There is demand for a high performance alternative, but this was never it and I'm glad to see this vestage of IIOs youth gone once and for all!
-
- 27 Jan, 2013 1 commit
-
-
Jonathan Cameron authored
This driver is simple, uses the latest interfaces and contains few if any controversial elements. All of its interfaces have been in place for a long time now. Hence let's move it out of staging. Signed-off-by:
Jonathan Cameron <jic23@kernel.org> Acked-by:
Peter Meerwald <pmeerw@pmeerw.net>
-
- 26 Jan, 2013 35 commits
-
-
Jonathan Cameron authored
Signed-off-by:
-
Jonathan Cameron authored
A rather over complicated exit path given there is only one exit route and nothing much is done after it. Signed-off-by:
-
Jonathan Cameron authored
Fix formatting of some comments and drop a few generic information free ones. Signed-off-by:
-
Jonathan Cameron authored
Not sure why these were ever there. Signed-off-by:
-
Lars-Peter Clausen authored
The driver is rather simple and in a good shape. It follows the IIO ABI and the standard codechecker tools do not report any issues, so move it out of staging. While moving it also remove one outdated 'fixme' comment. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
Lars-Peter Clausen authored
Report scale and offset for the velocity, voltage and temperature channels. Signed-off-by:
-
Lars-Peter Clausen authored
All sections in which the transfer buffer is accessed are already protected by the IIO device's mlock. So we do not need the extra mutex protecting the buffer. Signed-off-by:
-
Lars-Peter Clausen authored
The sample buffer contains big endian 16bit words. So use the be16 datatype for the buffer and use the proper helper functions for endianness conversion instead of openconding it. Signed-off-by:
-
Lars-Peter Clausen authored
During sampling the driver currently does a spi_read followed by a spi_write. This is not a problem per se, since CS needs to be deasserted between the two transfers. So even if another device claims the bus between the two transfers we should still get a result. But the code is actually spread out over multiple functions. E.g. the spi_read happens in one function the spi_write in another, this makes the code harder to follow. This patch re-factors the code to just use a single spi transaction to do both the read and the write transfer. Signed-off-by:
-
Lars-Peter Clausen authored
The adis16100 is very similar to the adis16080. The driver description already states that the driver supports the adis16100 as-well. But so far the there is no device id table for the adis16100 and the drivers does not bind to a device named adis16100. Signed-off-by:
-
Marek Vasut authored
Add interrupt mapping and compatible string for MX23 LRADC. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Fabio Estevam <fabio.estevam@freescale.com> Acked-by:
Shawn Guo <shawn.guo@linaro.org> Signed-off-by:
-
Marek Vasut authored
This patch adds support for i.MX23 into the LRADC driver. The LRADC block on MX23 is not much different from the one on MX28, thus this is only a few changes fixing the parts that are specific to MX23. Signed-off-by:
-
Peter Huewe authored
found with coccicheck sizeof when applied to a pointer typed expression gives the size of the pointer The semantic patch that makes this output is available in scripts/coccinelle/misc/noderef.cocci. More information about semantic patching is available at http://coccinelle.lip6.fr/Signed-off-by:
Peter Huewe <peterhuewe@gmx.de> Signed-off-by:
-
Jonathan Cameron authored
This is a very simple driver giving basic access to this part over an spi bus. Signed-off-by: -
Jonathan Cameron authored
Remove an unneeded initialization and trivial reorder to ensure the device is ready when the device is registered. Signed-off-by: -
Axel Lin authored
Signed-off-by:
Axel Lin <axel.lin@ingics.com> Acked-by:
Alexander Holler <holler@ahsoftware.de> Signed-off-by:
-
Jonathan Cameron authored
Whilst this is IIO's oldest buffer implementation it is messy, poorly implemented and whilst it works, no one is entirely sure it always will. New IIO drivers have not been using this for some time and now all remaining old users have been converted to use the kfifo based alternative. Clearly a fifo isn't the same as a ring buffer but in many use cases it really doesn't matter. We also loose the watershed based poll implementation. However having poll effectively report data only when the buffer was half full was at best an 'unusual' use of the interface. At somepoint in the future we may bring watersheds back on a different buffer implementation, but then we will think a lot more about how to do the interface first. Signed-off-by: -
Jonathan Cameron authored
sw ring is going away so switch over to kfifo based buffer implementation. The only real change is that poll will return on some data there rather than buffer 50% full. Signed-off-by: -
Jonathan Cameron authored
sw_ring buffer implementation is going away so switch to the kfifo based alternative. Signed-off-by: -
Jonathan Cameron authored
The sw_ring buffer is being removed in favour of the kfifo version. This is one of only a couple of driver still supporting its use. This driver will hopefully also be removed in favour of supporting the part in the unified ST accelerometer driver. Signed-off-by: -
Lars-Peter Clausen authored
The adis16448 is more or less from the same family of devices as supported by this driver. It features three acceleration channels, three angular velocity channels, three magnetometer channels, one temperature channels and one barometric pressure channel. Signed-off-by:
-
Lars-Peter Clausen authored
Expose some information useful for debugging a device in debugfs. This includes for now the flash count, the product id and the serial number and raw register access. Signed-off-by:
-
Lars-Peter Clausen authored
The adis16400 and similar have two different base sampling rate available, from which the actual sampling rate is derived. 1638 Hz and 52.85 Hz, switching to the lower base sampling rate allows to support lower sampling rates. This patch adds support for switching to the lower base sampling rate if the requested sampling frequency is outside of the range which can be supported by the higher base sampling rate. The function which is used to read the current sampling rate already has support for the lower sampling rate, so no changes are required there. Signed-off-by:
-
Lars-Peter Clausen authored
The devices supported by this drivers support sample rates with less than one sample per second. To support this increase the samplerate precession to allow setting (and reading) the samplerate with a milli-HZ precession. Signed-off-by:
-
Lars-Peter Clausen authored
This adis16400 driver is in pretty good shape now, so move it out of staging. Signed-off-by:
-
Lars-Peter Clausen authored
Do a set of minor miscellaneous code style cleanups for the adis16400 before moving it out of staging. Delete outdated comments, removed excess whitespace, add missing whitespace, replace u{8,16} with uint{8,16}_t. Signed-off-by: -
Lars-Peter Clausen authored
While the samplerate supported by the devices which are supported by this driver is not continuous it supports a wide range, much more than currently listed in the samplerate_available attribute. Also it accepts all values written to the samplerate attribute and will round-up them to the nearest supported sample rate. So remove the samplerate_available attribute. Signed-off-by:
-
Lars-Peter Clausen authored
To be compliant to the IIO specification we should not include the "SPS" suffix in the "samplerate" attribute contents. Signed-off-by:
-
Lars-Peter Clausen authored
Similar to like we already did for the generic adis library preallocate and pre-construct the SPI transfer message for the adis16400. For devices which do not support burst mode sampling does not differ from other adis devices and so we use the generic functions of the adis library in this case. In burst mode we can only sample all channels at once, so use the IIO cores demux facility instead of doing this manually. Signed-off-by:
-
Lars-Peter Clausen authored
Most of the channels declared in the adis16400 driver look quite similar. This patch adds a bunch of helper macros to initialize the channel spec for this driver. This allows us to drastically reduce the number of lines of code needed for the channel spec declaration. Signed-off-by:
-
Lars-Peter Clausen authored
Use the triggered buffer helper functions to setup and tear down the buffer for the adis16400 instead of doing this manually. This also means that we switch away from the deprecated sw_ring buffer and use the kfifo buffer now instead. Signed-off-by:
-
Lars-Peter Clausen authored
Use the new adis library for the adis16400 driver. This allows us to completely scrap the adis16400 trigger code and more than half of the core driver code. For now we can not make use of the generic adis buffer implementation since the adis16400 driver has special requirements due to its burst mode support. But we will eventually get to this. Signed-off-by:
-
Lars-Peter Clausen authored
The chip_info struct for contains a defaul_scan_mask field. But it is never actually used in the code, so remove it from the chip_info struct. Signed-off-by:
-
Lars-Peter Clausen authored
The 3db divisors table is partially wrong and incomplete. Also the code rounds up to the next higher frequency if the requested frequency would matches one of the available frequencies. These two issues are fixed by this patch. The patch also changes the driver to round down the filter frequency if it is larger than the largest supported frequency instead of rejecting it as an invalid value. Signed-off-by:
-
Lars-Peter Clausen authored
ilog2 is not defined for 0, so we need to handle the case where the requested frequency is larger than the base sampling rate. In this case we'll round down and set the sampling rate to the base sampling rate. Signed-off-by:
-
