linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	pmeerw@pmeerw.net, lee.jones@linaro.org, b.galvani@gmail.com,
	linus.walleij@linaro.org, andreas@kemnade.info,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	phh@phh.me, stefan@agner.ch, letux-kernel@openphoenux.org
Subject: [PATCH 0/5] mfd: rn5t618: add ADC support
Date: Fri, 17 Jan 2020 22:59:21 +0100	[thread overview]
Message-ID: <20200117215926.15194-1-andreas@kemnade.info> (raw)

This series adds support for the ADC in the RN5T618/RC5T619.
It depends on the IRQ support added in the RTC support series here:
https://lore.kernel.org/lkml/20191220122416.31881-1-andreas@kemnade.info/

First regmap setup has to be fixed because there is a register
wrongly classified as volatile.

I tested the driver only with the RC5T619 but it should work with the with 
the RN5T618 as well based on these facts:
- The corresponding register definitions originally went into the kernel
  for the RN5T618
- Public datasheet sections about the ADC look same.
- Out-of-tree code for these chips look same regarding to ADC

I marked these untested patches as RFC, and IMHO they require a Tested-By.
Feel free to ignore them if the whole series would be delayed just because
of missing Tested-By for those.

Andreas Kemnade (5):
  mfd: rn5t618: mark ADC control register volatile
  mfd: rn5t618: add ADC subdevice for RC5T619
  iio: adc: rn5t618: Add ADC driver for RN5T618/RC5T619
  mfd: rn5t618: add IRQ definitions for RN5T618
  mfd: rn5t618: add ADC subdevice for RN5T618

 drivers/iio/adc/Kconfig       |  10 ++
 drivers/iio/adc/Makefile      |   1 +
 drivers/iio/adc/rn5t618-adc.c | 266 ++++++++++++++++++++++++++++++++++
 drivers/mfd/rn5t618.c         |  49 ++++++-
 4 files changed, 324 insertions(+), 2 deletions(-)
 create mode 100644 drivers/iio/adc/rn5t618-adc.c

-- 
2.20.1


             reply	other threads:[~2020-01-17 22:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 21:59 Andreas Kemnade [this message]
2020-01-17 21:59 ` [PATCH 1/5] mfd: rn5t618: mark ADC control register volatile Andreas Kemnade
2020-01-20  8:49   ` Lee Jones
2020-01-17 21:59 ` [PATCH 2/5] mfd: rn5t618: add ADC subdevice for RC5T619 Andreas Kemnade
2020-01-20  8:49   ` Lee Jones
2020-01-24 15:28     ` Andreas Kemnade
2020-01-27  9:28       ` Lee Jones
2020-01-27 11:15         ` Andreas Kemnade
2020-01-17 21:59 ` [PATCH 3/5] iio: adc: rn5t618: Add ADC driver for RN5T618/RC5T619 Andreas Kemnade
2020-01-18 14:53   ` Jonathan Cameron
2020-01-18 22:14     ` Andreas Kemnade
2020-01-17 21:59 ` [RFC PATCH 4/5] mfd: rn5t618: add IRQ definitions for RN5T618 Andreas Kemnade
2020-01-17 21:59 ` [RFC PATCH 5/5] mfd: rn5t618: add ADC subdevice " Andreas Kemnade

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=20200117215926.15194-1-andreas@kemnade.info \
    --to=andreas@kemnade.info \
    --cc=b.galvani@gmail.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=lee.jones@linaro.org \
    --cc=letux-kernel@openphoenux.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phh@phh.me \
    --cc=pmeerw@pmeerw.net \
    --cc=stefan@agner.ch \
    /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).