From: Mark Brown <broonie@kernel.org>
To: "Lars Möllendorf" <lars.moellendorf@plating.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about regmap_range_cfg and regmap_mmio
Date: Wed, 4 Mar 2020 12:03:21 +0000 [thread overview]
Message-ID: <20200304120321.GA5646@sirena.org.uk> (raw)
In-Reply-To: <d2eb2248-0120-7b0f-9bcf-4f9c71954117@plating.de>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
On Wed, Mar 04, 2020 at 12:25:09PM +0100, Lars Möllendorf wrote:
> this mail is copied from internal issue written in markdown - I hope
> this is still readable as mail.
Not really frankly. I *think* you are saying that paging doesn't work
due to relying on having register read and write operations?
> My assumption is that paging is not a common use case for Memory-mapped
> I/O and thus has not been implemented for this case.
> - Are my assumptions correct?
> - If so, what would you recommend me to do:
> - Continue using `regmap-mmio` and implement my custom paging
> functions on top of that?
This will obviously work.
> - Enhance the current `regmap-mmio` implementation so it does paging
> and submit a patch?
That's not really possible since MMIO never writes the register address
to the bus.
> - Write my own `better-regmap-mmio` implementation?
It's not clear what that would mean.
You could also look into making the paging code not rely on explicit
register read and write operations.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-04 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 11:25 Lars Möllendorf
2020-03-04 12:03 ` Mark Brown [this message]
2020-03-04 13:28 ` Lars Möllendorf
2020-03-04 19:28 ` 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=20200304120321.GA5646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lars.moellendorf@plating.de \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®