From: Mark Brown <broonie@kernel.org>
To: Baolin Wang <baolin.wang7@gmail.com>
Cc: lee.jones@linaro.org, arnd@arndb.de, orsonzhai@gmail.com,
zhang.lyra@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/3] mfd: syscon: Add reg_update_bits() callback support
Date: Thu, 9 Apr 2020 11:48:02 +0100 [thread overview]
Message-ID: <20200409104802.GB5399@sirena.org.uk> (raw)
In-Reply-To: <759f7471d03946ae273a06f7bcca8a54528ec08c.1586422035.git.baolin.wang7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On Thu, Apr 09, 2020 at 04:57:57PM +0800, Baolin Wang wrote:
> --- a/include/linux/regmap.h
> +++ b/include/linux/regmap.h
> @@ -340,6 +340,8 @@ struct regmap_access_table {
> * read operation on a bus such as SPI, I2C, etc. Most of the
> * devices do not need this.
> * @reg_write: Same as above for writing.
> + * @reg_update_bits: Optional, should only be provided for devices whose update
> + * operation cannot be represented as read and write.
> * @fast_io: Register IO is fast. Use a spinlock instead of a mutex
> * to perform locking. This field is ignored if custom lock/unlock
> * functions are used (see fields lock/unlock of struct regmap_config).
> @@ -416,6 +418,8 @@ struct regmap_config {
>
> int (*reg_read)(void *context, unsigned int reg, unsigned int *val);
> int (*reg_write)(void *context, unsigned int reg, unsigned int val);
> + int (*reg_update_bits)(void *context, unsigned int reg,
> + unsigned int mask, unsigned int val);
This is fine, we already have this operation for buses, but why is this
munged in with the MFD patch?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-09 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 8:57 [RFC PATCH 0/3] Add new reg_update_bits() support Baolin Wang
2020-04-09 8:57 ` [RFC PATCH 1/3] mfd: syscon: Add reg_update_bits() callback support Baolin Wang
2020-04-09 10:48 ` Mark Brown [this message]
2020-04-09 14:13 ` Baolin Wang
2020-04-09 14:27 ` Mark Brown
2020-04-10 2:15 ` Baolin Wang
2020-04-09 8:57 ` [RFC PATCH 2/3] regmap: Add reg_update_bits() support Baolin Wang
2020-04-09 10:45 ` Mark Brown
2020-04-09 14:12 ` Baolin Wang
2020-04-09 14:26 ` Mark Brown
2020-04-10 2:55 ` Baolin Wang
2020-04-09 8:57 ` [RFC PATCH 3/3] soc: sprd: Add Spreadtrum special bits updating support Baolin Wang
2020-04-09 9:15 ` [RFC PATCH 0/3] Add new reg_update_bits() support Arnd Bergmann
2020-04-09 9:40 ` Baolin Wang
2020-04-09 9:52 ` Arnd Bergmann
2020-04-09 9:56 ` Baolin Wang
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=20200409104802.GB5399@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=baolin.wang7@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@gmail.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
all inboxes | Powered by JetHome®