This fix checkpatch warnings:

WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This is a reimplementation of the old misc device driver for the
ROHM BH1780 ambient light sensor (drivers/misc/bh1780gli.c).

Differences from the old driver:
- Uses the IIO framework
- Uses runtime PM to idle the hardware after 5 seconds
- No weird custom power management from userspace
- No homebrewn values in sysfs

This uses the same (undocumented) device tree compatible-string
as the old driver ("rohm,bh1780gli").

Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Daniel Mack <daniel@caiaq.de>
Cc: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
Reviewed-by: NUlf Hansson <ulf.hansson@linaro.org>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Indent lines inside if statement.
Signed-off-by: NKsenija Stanojevic <ksenija.stanojevic@gmail.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

The ADIS16201 does not automatically clear the self test flag bit the self
test has been, so clear it manually. Otherwise we'll see a offset caused by
the self-test bias on the output values during normal operation.
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

The ADIS16201 does not automatically clear the self test flag bit the self
test has been, so clear it manually. Otherwise we'll see a offset caused by
the self-test bias on the output values during normal operation.
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

The ADIS16201 does not automatically clear the self test flag bit the self
test has been, so clear it manually. Otherwise we'll see a offset caused by
the self-test bias on the output values during normal operation.
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

The ADIS16201 does not automatically clear the self test flag bit the self
test has been, so clear it manually. Otherwise we'll see a offset caused by
the self-test bias on the output values during normal operation.
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Some variants of the devices from the ADIS family don't auto-clear the
self-test bit after the self-test has completed. Instead we have to
manually clear. Add support for this to the ADIS library.
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the errors reported by checkpatch.pl:

ERROR: code indent should use tabs where possible
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the error reported by checkpatch.pl:

ERROR: else should follow close brace '}'
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the error reported by checkpatch.pl:

ERROR: code indent should use tabs where possible
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the error reported by checkpatch.pl:

ERROR: code indent should use tabs where possible
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the error reported by checkpatch.pl:

ERROR: space prohibited before that ',' (ctx:WxW)
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the errors reported by checkpatch.pl:

ERROR: space prohibited before that ',' (ctx:WxW)
ERROR: code indent should use tabs where possible
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the error reported by checkpatch.pl:

ERROR: space prohibited before that ',' (ctx:WxW)
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the error reported by checkpatch.pl:

ERROR: switch and case should be at the same indent
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the error reported by checkpatch.pl:

ERROR: space required before the open parenthesis '('
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This fixes the error reported by checkpatch.pl:

ERROR: that open brace { should be on the previous line
Signed-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

BMI160 is an Inertial Measurement Unit (IMU) which provides acceleration
and angular rate measurement. It also offers a secondary I2C interface
for connecting a magnetometer sensor (usually BMM160).

Current driver offers support for accelerometer and gyroscope readings
via sysfs or via buffer interface using an external trigger (e.g.
hrtimer). Data is retrieved from IMU via I2C or SPI interface.

Datasheet is at:
	http://www.mouser.com/ds/2/783/BST-BMI160-DS000-07-786474.pdfSigned-off-by: NDaniel Baluta <daniel.baluta@intel.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

* Unify log messages
* Add more DEBUG messages

Apparently this driver is working unreliably on some platforms that I can't
test. Therefore I want an easy way for bug reporters to provide useful
information without making the driver too chatty by default.
Signed-off-by: NHarald Geyer <harald@ccbib.org>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Replace the code that guarantees the device stays in direct mode with
iio_device_{claim|release}_direct_mode() which does same.
Signed-off-by: NAlison Schofield <amsfield22@gmail.com>
Acked-by: NLars-Peter Clausen <lars@metafoo.de>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.

Patch created using Coccinelle plus manual edits.
Signed-off-by: NAlison Schofield <amsfield22@gmail.com>
Acked-by: NJoachim Eastwood <manabian@gmail.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This patch adds support for the AD5592R (spi) and AD5593R (i2c)
ADC/DAC/GPIO devices.
Signed-off-by: NPaul Cercueil <paul.cercueil@analog.com>
Signed-off-by: NMichael Hennerich <michael.hennerich@analog.com>
Reviewed-by: NLinus Walleij <linus.walleij@linaro.org>
Acked-by: NRob Herring <robh@kernel.org>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

This will be used together with an external trigger (e.g hrtimer based
software trigger).
Signed-off-by: NGregor Boirie <gregor.boirie@parrot.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

The following functions are supported:
 - write, read potentiometer value
 - potentiometer scale

Datasheet: https://datasheets.maximintegrated.com/en/ds/DS1803.pdfSigned-off-by: NSlawomir Stepien <sst@poczta.fm>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

fix checkpatch.pl warning about 'Prefer 'unsigned int' to bare use of
'unsigned''
Signed-off-by: NClifton Barnes <clifton.a.barnes@gmail.com>
Acked-by: NMartyn Welch <martyn@welchs.me.uk>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>

fix checkpatch.pl warning about 'Avoid CamelCase'
Signed-off-by: NDaeseok Youn <daeseok.youn@gmail.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>

The "ch->ch_bd" is already assined to "bd" but this is only
for checking null or MAGIC number.
in the dgnc_tty_ioctl function, bd can be used for referencing
to board_ops structure.
Signed-off-by: NDaeseok Youn <daeseok.youn@gmail.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>

Currently, lowmemorykiller (LMK) is using TIF_MEMDIE for two purposes.
One is to remember processes killed by LMK, and the other is to
accelerate termination of processes killed by LMK.

But since LMK is invoked as a memory shrinker function, there still
should be some memory available. It is very likely that memory
allocations by processes killed by LMK will succeed without using
ALLOC_NO_WATERMARKS via TIF_MEMDIE. Even if their allocations cannot
escape from memory allocation loop unless they use ALLOC_NO_WATERMARKS,
lowmem_deathpending_timeout can guarantee forward progress by choosing
next victim process.

On the other hand, mark_oom_victim() assumes that it must be called with
oom_lock held and it must not be called after oom_killer_disable() was
called. But LMK is calling it without holding oom_lock and checking
oom_killer_disabled. It is possible that LMK calls mark_oom_victim()
due to allocation requests by kernel threads after current thread
returned from oom_killer_disabled(). This will break synchronization
for PM/suspend.

This patch introduces per a task_struct flag for remembering processes
killed by LMK, and replaces TIF_MEMDIE with that flag. By applying this
patch, assumption by mark_oom_victim() becomes true.
Signed-off-by: NTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Acked-by: NMichal Hocko <mhocko@suse.com>
Cc: Arve Hjonnevag <arve@android.com>
Cc: Riley Andrews <riandrews@android.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>

bmc150_i2c_regmap_conf is defined three times (in bmc150-accel-core.c,
bmc150-accel-i2c.c and and bmc150-accel-spi.c), although the
definition is the same.

Use one common definition for bmc150_i2c_regmap_conf in all
included files.
Signed-off-by: NIrina Tirdea <irina.tirdea@intel.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Signed-off-by: NCrestez Dan Leonard <leonard.crestez@intel.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

UV index indicating strength of sunburn-producing ultraviolet (UV) radiation
Signed-off-by: NPeter Meerwald-Stadler <pmeerw@pmeerw.net>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Signed-off-by: NPeter Meerwald-Stadler <pmeerw@pmeerw.net>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

The scale would result in uV instead of expected mV.
Mostly cosmetic, since the value of 'Power' was computed OK.
Signed-off-by: NMarc Titinger <marc.titinger@baylibre.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Add signed differential channels and update the voltage scale for
differential conversions.
Signed-off-by: NLudovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Do not erase previous configuration of the mode register when setting
the sampling frequency.
Signed-off-by: NLudovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

The following functionalities are supported:
 - write, read from volatile memory

Datasheet: http://ww1.microchip.com/downloads/en/DeviceDoc/22060b.pdfSigned-off-by: NSlawomir Stepien <sst@poczta.fm>
Reviewed-by: NJoachim Eastwood <manabian@gmail.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Fix following sparse warning:
warning: cast to restricted __be16
Signed-off-by: NKsenija Stanojevic <ksenija.stanojevic@gmail.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

Commit 845c8770 ("i2c / ACPI: Assign IRQ for devices that have
GpioInt automatically") automatically assigns the first ACPI GPIO
interrupt in client->irq, so we can remove the probing code from
drivers that use only one interrupt.

Commit 0f079650 ("iio: remove gpio interrupt probing from drivers
that use a single interrupt") removes gpio interrupt probing from most
drivers. This patch cleans the remaining ones.
Signed-off-by: NIrina Tirdea <irina.tirdea@intel.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>

GPIO handling code has been removed from the drivers (since
this is now handled by the ACPI core) in commit 0f079650 ("iio:
remove gpio interrupt probing from drivers that use a single interrupt").

Remove the include for linux/gpio/consumer.h since it is no longer
used.
Signed-off-by: NIrina Tirdea <irina.tirdea@intel.com>
Signed-off-by: NJonathan Cameron <jic23@kernel.org>