linux.git/drivers/iio, branch v3.10-rc2

iio: at91_adc: fix missing Sample and Hold time

2013-04-02T18:22:16+00:00

On the at91_adc a minimal Sample and Hold Time is necessary for the ADC to
guarantee the best converted final value between two channels selection.
This time has to be programmed through the bitfield SHTIM in the
Mode Register ADC_MR.

Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD 
Signed-off-by: Ludovic Desroches 
Signed-off-by: Jonathan Cameron

iio: at91_adc: add sleep mode support

2013-04-02T18:17:39+00:00

The sleep mode will allow to put the adc in sleep between conversion.

Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD 
Signed-off-by: Ludovic Desroches 
Acked-by: Maxime Ripard 
Signed-off-by: Jonathan Cameron

iio: at91_adc: add low and high res support

2013-04-02T18:17:26+00:00

at91 adc offers the choice between two resolutions: low and high.
The low and high resolution values depends on adc IP version, as many IP
properties have been exposed through device tree, these settings have also
been added to the dt bindings.

Signed-off-by: Ludovic Desroches 
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD 
Signed-off-by: Jonathan Cameron

iio:magnetometer:ak8975 move driver out of staging

2013-04-02T17:36:47+00:00

Issues raised in last series to propose this have now been resolved
so there should be no reason this driver cannot graduate from staging.

Signed-off-by: Jonathan Cameron 
Acked-by: Laxman Dewangan

iio: exynos_adc: Remove redundant of_match_ptr macro

2013-03-29T09:24:49+00:00

exynos_adc is a DT only driver and exynos_adc_match table is always
compiled in. Hence remove the macro.

Signed-off-by: Sachin Kamat 
Signed-off-by: Jonathan Cameron

iio:trigger: Introduce iio_tigger_{set,get}_drvdata

2013-03-25T21:06:09+00:00

Introduce iio_tigger_{set,get}_drvdata which allows to attach driver specific
data to a trigger. The functions wrap access to the triggers private_data field
and all current users are updated to use iio_tigger_{set,get}_drvdata instead of
directly accessing the private_data field. This is the first step towards
removing the private_data field from the iio_trigger struct.

The following coccinelle script has been used to update the drivers:

@@
struct iio_trigger *trigger;
expression priv;
@@
-trigger->private_data = priv
+iio_trigger_set_drv_data(trigger, priv)

@@
struct iio_trigger *trigger;
@@
-trigger->private_data
+iio_trigger_get_drv_data(trigger)


Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Jonathan Cameron

Merge tag 'iio-for-3.10a' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next

2013-03-25T17:50:03+00:00

Jonathan writes:

First set of IIO new drivers and cleanup for the 3.10 cycle.

New stuff

1) Add OF support for specifying mappings between iio devices and their
   in kernel consumers.
2) Driver for AD7923 (extra functionality and support for ad7904, ad7914 and
   ad7924 added later in series)
3) Driver for Exynos adc (dt suppor for phy added later in series).
4) Make iio_push_event save IRQ context - necessary if it is to be used
   within an interrupt handler.  Users of this functionality to follow.
5) For iio use the device tree node name to provide the hwmon name attribute
   if available.

Removal and moves out of staging

1) Drop the adt7410 driver from IIO now that there is a hmwon driver with
   equivalent support. This device is very much targeted at hardware
   monitoring so hwmon is a more appropriate host for the driver.
2) Move iio_hwmon driver to drivers/hwmon.

Cleanups

1) Minor cleanup in ST common library.
2) Large set of patches to break the info_mask element which previously used
odd and even bits to specify if a channel attribute was either shared across
similar channels or specific to only one.  Now we have two bitmaps, one for
those parameters that are specific to this channel and one for those shared
by all channels with the same type as this one.  This has no effect on the
userspace abi. It simplifies the core code and provides more space for new
channel parameters. It has been on the todo list for a long time!

Conflicts:
	drivers/iio/dac/ad5064.c

iio: adc: Add dt support for turning on the phy in exynos-adc

2013-03-17T22:46:55+00:00

Without this change the exynos adc controller needed to have its phy
enabled in some out-of-driver C code.  Add support for specifying the
phy enable register by listing it in the reg list.

Signed-off-by: Doug Anderson 
Tested-by: Naveen Krishna Chatradhi 
Signed-off-by: Jonathan Cameron

iio:adc:ad7923: Add support for the ad7904/ad7914/ad7924

2013-03-17T20:16:41+00:00

The ad7924 is software compatible with the ad7923. The ad7904 and ad7914 are the
8 and 10 bit version of the ad7924.

While we are at it also drop the "with temperature sensor" from the Kconfig
entry, since the chips do not have a temperature sensor.

Signed-off-by: Lars-Peter Clausen 
Cc: Patrick Vasseur 
Cc: Christophe Leroy 
Signed-off-by: Jonathan Cameron

iio:ad7923: Implement scale reporting

2013-03-17T20:16:40+00:00

The driver already claims to support scale reporting in its channel spec, but
doesn't actually implement this yet. This patch uses the regulator API to get
the reference voltage and calculates the scale based on that. The patch also
moves the global configuration bits into a field in the ad7923_state struct,
since depending on the RANGE bit, the range goes either from 0 to VREF or from 0
to 2 * VREF. So we need to know the setting of the RANGE bit when calculating
the scale.

Signed-off-by: Lars-Peter Clausen 
Cc: Patrick Vasseur 
Cc: Christophe Leroy 
Signed-off-by: Jonathan Cameron