From: Greg KH <gregkh@linuxfoundation.org>
To: Tianfei Zhang <tianfei.zhang@intel.com>
Cc: broonie@kernel.org, rafael@kernel.org,
linux-kernel@vger.kernel.org, hao.wu@intel.com, trix@redhat.com,
yilun.xu@intel.com, russell.h.weight@intel.com,
Matthew Gerlach <matthew.gerlach@linux.intel.com>
Subject: Re: [PATCH v1] regmap: add generic indirect regmap support
Date: Tue, 7 Jun 2022 06:50:17 +0200 [thread overview]
Message-ID: <Yp7ZCWq3yjNcMM4N@kroah.com> (raw)
In-Reply-To: <20220607013755.594554-1-tianfei.zhang@intel.com>
On Mon, Jun 06, 2022 at 09:37:55PM -0400, Tianfei Zhang wrote:
> From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
>
> This patch adds support for regmap APIs that are intended to be used by
> the drivers of some devices which support generic indirect register access,
> for example PMCI (Platform Management Control Interface) device, HSSI
> (High Speed Serial Interface) device in FPGA.
>
> Signed-off-by: Matthew Gerlach <matthew.gerlach@linux.intel.com>
> Signed-off-by: Tianfei Zhang <tianfei.zhang@intel.com>
> ---
> drivers/base/regmap/Kconfig | 3 +
> drivers/base/regmap/Makefile | 1 +
> .../base/regmap/regmap-indirect-register.c | 133 ++++++++++++++++++
> include/linux/regmap.h | 12 ++
> 4 files changed, 149 insertions(+)
> create mode 100644 drivers/base/regmap/regmap-indirect-register.c
Don't we need users of these before we can take them?
thanks,
greg k-h
next prev parent reply other threads:[~2022-06-07 4:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 1:37 [PATCH v1] regmap: add generic indirect regmap support Tianfei Zhang
2022-06-07 4:50 ` Greg KH [this message]
2022-06-07 5:57 ` Zhang, Tianfei
2022-06-07 13:15 ` Mark Brown
2022-06-08 0:27 ` matthew.gerlach
2022-06-08 10:43 ` Mark Brown
2022-06-08 23:54 ` Zhang, Tianfei
2022-06-09 10:14 ` Mark Brown
2022-06-10 0:30 ` matthew.gerlach
2022-06-10 11:59 ` Mark Brown
2022-08-09 17:06 ` Russ Weight
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=Yp7ZCWq3yjNcMM4N@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=hao.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=rafael@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=tianfei.zhang@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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).