From: Mark Brown <broonie@kernel.org>
To: matthew.gerlach@linux.intel.com
Cc: "Zhang, Tianfei" <tianfei.zhang@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Wu, Hao" <hao.wu@intel.com>, "trix@redhat.com" <trix@redhat.com>,
"Xu, Yilun" <yilun.xu@intel.com>,
"Weight, Russell H" <russell.h.weight@intel.com>
Subject: Re: [PATCH v1] regmap: add generic indirect regmap support
Date: Fri, 10 Jun 2022 12:59:00 +0100 [thread overview]
Message-ID: <YqMyBFnNky7sP1dC@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2206091655490.1640209@rhweight-WRK1>
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
On Thu, Jun 09, 2022 at 05:30:43PM -0700, matthew.gerlach@linux.intel.com wrote:
> On Thu, 9 Jun 2022, Mark Brown wrote:
> > On Wed, Jun 08, 2022 at 11:54:26PM +0000, Zhang, Tianfei wrote:
> > > > ...that this appears to be entirely specific to some particular device, it's got
> > > > things like hard coded register addresses and timeouts which mean it can't be
> > > > reused.
> I think part of the confusion is that this patch should have been included
> in a patch set that actually uses this regmap. This patch really should be
> included with the following:
> https://lore.kernel.org/all/20220607032833.3482-1-tianfei.zhang@intel.com
> The hard coded register definitions are offsets to the passed in void
> __iomem base address. This set of registers provides the semantics of
> indirect register read/write to whatever the register set is connected to on
> the back end. Conceptually this could be considered a specific type
> indirect register access controller, but currently we have very different
> backend implementations in RTL. Part of our intent is to have consistent
> register interfaces for our FPGA IP so multiple drivers can reuse this
> regmap.
...which is all specific to your particular implmentation of this and
not a generic thing that will work for anyone else who implements the
concept of indirected register access and happens to use a different
control mechanism. If you have to use the same register interfaces to
reuse this code then the code isn't generic.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-10 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 1:37 Tianfei Zhang
2022-06-07 4:50 ` Greg KH
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 [this message]
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=YqMyBFnNky7sP1dC@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®