From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9] mfd: Add anatop mfd driver
Date: Thu, 15 Mar 2012 12:09:48 +0000 [thread overview]
Message-ID: <20120315120948.GG3138@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201203150907.29895.arnd@arndb.de>
On Thu, Mar 15, 2012 at 09:07:29AM +0000, Arnd Bergmann wrote:
> Very broadly speaking, I wonder whether we could use the regmap
> infrastructure for these things in the future, but I would first
> need to understand whether that is actually in the scope of regmap.
> It seems that you just need a subset of what regmap provides,
> so it could work, but it might not actually be better than what
> you have now.
> Mark, can you comment on that?
There were some other mutterings about using regmap for memory mapped
devices, mostly from the point of view of building framework features
like this on top of it. regmap currently makes some assumptions that
the I/O is going to be slow so approximately any amount of CPU time can
usefully be spent on avoiding I/O but we can probably do something about
that. It also uses mutexes to lock I/O which might not be the most
sensible thing for memory mapped devices, but again that's solveable.
Right now there's no memory mapping support but there's no reason that
can't be added.
In short, it does seem sensible to want to have some support for this
for devices that use appropriate idioms.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120315/37f8408c/attachment.sig>
next prev parent reply other threads:[~2012-03-15 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 7:43 [PATCH v9] mfd: Add anatop mfd driver Ying-Chun Liu (PaulLiu)
2012-03-15 9:07 ` Arnd Bergmann
2012-03-15 12:09 ` Mark Brown [this message]
2012-03-15 15:52 ` Arnd Bergmann
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=20120315120948.GG3138@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).