Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	Guenter Roeck <linux@roeck-us.net>
Subject: [RFC PATCH 0/3] regmap: Implement regmap_multi_reg_read()
Date: Tue,  9 Jul 2024 18:56:19 -0700	[thread overview]
Message-ID: <20240710015622.1960522-1-linux@roeck-us.net> (raw)

regmap_multi_reg_read() is similar to regmap_bilk_read() but reads from
an array of non-sequential registers. It is helpful if multiple non-
sequential registers need to be read in a single operation which would
otherwise have to be mutex protected.

The name of the new function was chosen to match the existing function
regmap_multi_reg_write().

The first patch of the series introduces the new function. The following
two patches provide examples for its use.

----------------------------------------------------------------
Guenter Roeck (3):
      regmap: Implement regmap_multi_reg_read()
      hwmon: (adt7470) Use multi-byte regmap operations
      hwmon: (tmp401) Use multi-byte regmap operations

 drivers/base/regmap/regmap.c | 103 ++++++++++++++++++++++++++++---------------
 drivers/hwmon/adt7470.c      |  22 +++------
 drivers/hwmon/tmp401.c       |  19 +++-----
 include/linux/regmap.h       |   2 +
 4 files changed, 84 insertions(+), 62 deletions(-)

             reply	other threads:[~2024-07-10  1:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10  1:56 Guenter Roeck [this message]
2024-07-10  1:56 ` [RFC PATCH 1/3] regmap: Implement regmap_multi_reg_read() Guenter Roeck
2024-07-10  1:56 ` [RFC PATCH 2/3] hwmon: (adt7470) Use multi-byte regmap operations Guenter Roeck
2024-07-10  1:56 ` [RFC PATCH 3/3] hwmon: (tmp401) " Guenter Roeck
2024-07-10 23:24 ` (subset) [RFC PATCH 0/3] regmap: Implement regmap_multi_reg_read() Mark Brown
2024-07-11  1:14 ` Mark Brown
2024-07-11  3:33   ` Guenter Roeck
2024-07-11 11:39     ` Mark Brown

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=20240710015622.1960522-1-linux@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox