From: Mark Brown <broonie@kernel.org>
To: Stefan Popa <stefan.popa@analog.com>
Cc: jic23@kernel.org, lars@metafoo.de, Michael.Hennerich@analog.com,
knaack.h@gmx.de, pmeerw@pmeerw.net, mark.rutland@arm.com,
davem@davemloft.net, mchehab+samsung@kernel.org,
gregkh@linuxfoundation.org, akpm@linux-foundation.org,
robh+dt@kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Crestez Dan Leonard <leonard.crestez@intel.com>
Subject: Re: [PATCH v5 3/6] regmap: Add regmap_noinc_read API
Date: Thu, 9 Aug 2018 11:14:53 +0100 [thread overview]
Message-ID: <20180809101453.GD6132@sirena.org.uk> (raw)
In-Reply-To: <1533653540-24796-4-git-send-email-stefan.popa@analog.com>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
On Tue, Aug 07, 2018 at 05:52:17PM +0300, Stefan Popa wrote:
> From: Crestez Dan Leonard <leonard.crestez@intel.com>
>
> The regmap API usually assumes that bulk read operations will read a
> range of registers but some I2C/SPI devices have certain registers for
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-noinc-read
for you to fetch changes up to 74fe7b551f3385fa585d92616c85b3a575b2b2cb:
regmap: Add regmap_noinc_read API (2018-08-09 11:00:15 +0100)
----------------------------------------------------------------
regmap: Support non-incrementing registers
Some devices have individual registers that don't autoincrement the
register address during bulk reads but instead repeatedly read the same
value, for example for monitoring GPIOs or ADCs. Add support for these.
----------------------------------------------------------------
Crestez Dan Leonard (1):
regmap: Add regmap_noinc_read API
drivers/base/regmap/internal.h | 3 ++
drivers/base/regmap/regmap.c | 79 +++++++++++++++++++++++++++++++++++++++++-
include/linux/regmap.h | 19 ++++++++++
3 files changed, 100 insertions(+), 1 deletion(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-09 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 14:52 [PATCH v5 0/6] iio: accel: Add adxl372 driver Stefan Popa
2018-08-07 14:52 ` [PATCH v5 1/6] iio: adxl372: New driver for Analog Devices ADXL372 Accelerometer Stefan Popa
2018-08-07 14:52 ` [PATCH v5 2/6] dt-bindings: iio: accel: Add docs for ADXL372 Stefan Popa
2018-08-09 21:34 ` Rob Herring
2018-08-07 14:52 ` [PATCH v5 3/6] regmap: Add regmap_noinc_read API Stefan Popa
2018-08-09 10:14 ` Mark Brown [this message]
2018-08-07 14:52 ` [PATCH v5 4/6] iio:adxl372: Add FIFO and interrupts support Stefan Popa
2018-08-07 14:52 ` [PATCH v5 5/6] iio:adxl372: Add sampling frequency support Stefan Popa
2018-08-07 14:52 ` [PATCH v5 6/6] iio:adxl372: Add filter bandwidth support Stefan Popa
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=20180809101453.GD6132@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=leonard.crestez@intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=stefan.popa@analog.com \
/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).