From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: [PULL] IIO fixes for 4.0 set 4
Date: Mon, 30 Mar 2015 20:38:42 +0100 [thread overview]
Message-ID: <5519A642.3070407@kernel.org> (raw)
The following changes since commit 3d8bbe243dc7418b4b2eadcbf5693887d076a521:
Merge tag 'iio-fixes-for-4.0c' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus (2015-03-24 22:55:20 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-4.0d
for you to fetch changes up to 4ce7ca89d6e8eae9e201cd0e972ba323f33e2fb4:
iio: imu: Use iio_trigger_get for indio_dev->trig assignment (2015-03-28 13:51:40 +0000)
----------------------------------------------------------------
IIO fixes for 4.0 set 4
A couple more IIO fixes.
* Fix check for HAS_IOMEM in the cc100001_adc driver to avoid build errors.
Rather curiously it was ORed with Regulator and clock support.
* vf610 driver was trying to use an ADC clock outside the possible
spec on some boards. The driver assumed a fixed clock speed previously
across all boards, but that is not true. This fix ensures that the
reported frequency is correct on all boards.
* The adis imu common code directly set the current trigger to the
driver supplied one. Unfortunately this didn't increase the use count
leading to a double free via a particular path of changing the trigger
then removing the driver.
----------------------------------------------------------------
Darshana Padmadas (1):
iio: imu: Use iio_trigger_get for indio_dev->trig assignment
Richard Weinberger (1):
iio/adc/cc10001_adc.c: Fix !HAS_IOMEM build
Stefan Agner (1):
iio: adc: vf610: use ADC clock within specification
drivers/iio/adc/Kconfig | 3 +-
drivers/iio/adc/vf610_adc.c | 91 ++++++++++++++++++++++++++++--------------
drivers/iio/imu/adis_trigger.c | 2 +-
3 files changed, 64 insertions(+), 32 deletions(-)
next reply other threads:[~2015-03-30 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 19:38 Jonathan Cameron [this message]
2015-04-01 11:51 ` [PULL] IIO fixes for 4.0 set 4 Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5519A642.3070407@kernel.org \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-iio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.