linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Crestez Dan Leonard <leonard.crestez@intel.com>
To: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Daniel Baluta <daniel.baluta@intel.com>,
	Crestez Dan Leonard <leonard.crestez@intel.com>
Subject: [PATCH v2 0/2] Add support for adc101c* and adc121c*
Date: Mon,  4 Apr 2016 21:21:40 +0300	[thread overview]
Message-ID: <cover.1459793615.git.leonard.crestez@intel.com> (raw)

Changes since last version:
 * Use struct adcxx1_model in the first patch as well.
 * Use VLA buf in adc081c_trigger_handler.
 * Rerrange code so the diffs look nicer.
 * Fixed other smaller review comments.

I did not add an enum for models because it's not clear how adding another
layer of indirection would help. Maybe if we ever want to scan the table of
models? But that's not useful here.

The devices actually have names like ADC121C021/ADC121C027 to identify chips
with different pinouts but identical I2C interfaces. Those differences don't
currently matter to the driver.

Crestez Dan Leonard (2):
  ti-adc081c: Add support for adc101c* and adc121c*
  ti-adc081c: Initial triggered buffer support

 drivers/iio/adc/Kconfig      |   6 +--
 drivers/iio/adc/ti-adc081c.c | 103 ++++++++++++++++++++++++++++++++++++++-----
 2 files changed, 94 insertions(+), 15 deletions(-)

-- 
2.5.5


             reply	other threads:[~2016-04-04 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 18:21 Crestez Dan Leonard [this message]
2016-04-04 18:21 ` [PATCH v2 1/2] ti-adc081c: Add support for adc101c* and adc121c* Crestez Dan Leonard
2016-04-10 14:25   ` Jonathan Cameron
2016-04-04 18:21 ` [PATCH v2 2/2] ti-adc081c: Initial triggered buffer support Crestez Dan Leonard
2016-04-04 18:39   ` kbuild test robot
2016-04-10 14:29   ` 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.1459793615.git.leonard.crestez@intel.com \
    --to=leonard.crestez@intel.com \
    --cc=daniel.baluta@intel.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).