From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: andrey.smirnov@convergeddevices.net
Cc: broonie@opensource.wolfsonmicro.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Add "no-bus" configuration for regmap API
Date: Fri, 21 Dec 2012 01:47:15 -0800 [thread overview]
Message-ID: <1356083238-6932-1-git-send-email-andrew.smirnov@gmail.com> (raw)
This patch proposes extension to the API that was suggested by Mark in
the following thread:
http://article.gmane.org/gmane.linux.kernel/1383734
The idea behind extensions is to allow the devices that expose some
register-like interface but whose protocol for reading or writing
those registers could not be simplified to serialized bytestream
writes to be used within 'regmap' framework
Original RFC thread can be found here:
https://lkml.org/lkml/2012/11/23/367
First two patches are refactoring patches that add all the necessary
plumbing to the regmap internals and move old functionality to use
that infrastracture.
Third patch introduces code that implements 'no-bus' configuration
Andrey Smirnov (3):
Add provisions to have user-defined read operation
Add provisions to have user-defined write operation
Add "no-bus" option for regmap API
drivers/base/regmap/internal.h | 5 ++
drivers/base/regmap/regmap.c | 156 +++++++++++++++++++++++++++++-----------
include/linux/regmap.h | 7 ++
3 files changed, 126 insertions(+), 42 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-12-21 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 9:47 Andrey Smirnov [this message]
2012-12-21 9:47 ` [PATCH 1/3] Add provisions to have user-defined read operation Andrey Smirnov
2012-12-21 9:47 ` [PATCH 2/3] Add provisions to have user-defined write operation Andrey Smirnov
2012-12-21 9:47 ` [PATCH 3/3] Add "no-bus" option for regmap API Andrey Smirnov
2012-12-27 18:24 ` Mark Brown
2012-12-29 19:18 ` Andrey Smirnov
2012-12-27 17:41 ` [PATCH 0/3] Add "no-bus" configuration " 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=1356083238-6932-1-git-send-email-andrew.smirnov@gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=andrey.smirnov@convergeddevices.net \
--cc=broonie@opensource.wolfsonmicro.com \
--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®