linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	William Breathitt Gray <vilhelm.gray@gmail.com>
Subject: [PATCH v4 0/1] iio: stx104: Add IIO support for the ADC channels
Date: Mon, 25 Jul 2016 13:53:36 -0400	[thread overview]
Message-ID: <cover.1469468983.git.vilhelm.gray@gmail.com> (raw)

Changes in v4:
  - Replace "DAC" with "IIO" in the MAINTAINERS file entry for the STX104 since
    this driver now supports the ADC functionality rather than simply the DAC
Changes in v3:
  - Squash move patch as unneeded thanks to "git format-patch -M"
  - Fix multiline comment syntax for value conversion math explanation
  - Select between two const iio_chan_spec structures in order to support
    differential input channels configuration correctly for multiple devices
Changes in v2:
  - IIO_CHAN_INFO_RAW mask used for analog input channels
  - STX104_ prefix added to IN_CHAN_OFFSET define
  - STX104_MAX_NUM_CHAN define removed as unnecessary
  - Whitespace added to pad comment about ADC sample capture and completion wait
  - Switch statement in write_raw callback refactored to return 0
  - Comma added to last element initialization of stx104_info
  - Comment added to warn why stx104_channels is not const
  - Comment added to explain GPIO offset in gpio_get_direction callback
  - ARRAY_SIZE macro utilized to get number of channels in stx104_channels
  - Replace devm_iio_device_register with iio_device_register call and
    respective iio_device_unregister call
  - Perform GPIO chip registration before iio_device_register to prevent race
    condition

The first patch of version 2 of this patchset ("iio: stx104: Unregister IIO
device on remove callback") has been removed from this patchset since it was
picked up in the iio.git fixes-togreg-post-rc1 branch.

The move patch of version 2 of this patchset has been squashed with the ADC
support implementation code since the "git format-patch -M" command has been
used to clarify the rename of the stx104.c file from the dac directory to the
adc directory.

William Breathitt Gray (1):
  iio: stx104: Add IIO support for the ADC channels

 MAINTAINERS                       |   4 +-
 drivers/iio/adc/Kconfig           |  15 ++++
 drivers/iio/adc/Makefile          |   1 +
 drivers/iio/{dac => adc}/stx104.c | 157 ++++++++++++++++++++++++++++++++------
 drivers/iio/dac/Kconfig           |  10 ---
 drivers/iio/dac/Makefile          |   1 -
 6 files changed, 151 insertions(+), 37 deletions(-)
 rename drivers/iio/{dac => adc}/stx104.c (59%)

-- 
2.7.3

             reply	other threads:[~2016-07-25 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 17:53 William Breathitt Gray [this message]
2016-07-25 17:54 ` [PATCH v4 1/1] iio: stx104: Add IIO support for the ADC channels William Breathitt Gray
2016-08-21 19:39   ` Jonathan Cameron
2016-08-22 13:24     ` William Breathitt Gray
2016-08-23 18:12       ` Jonathan Cameron

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=cover.1469468983.git.vilhelm.gray@gmail.com \
    --to=vilhelm.gray@gmail.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).