From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH] Add regmap support
Date: Wed, 3 Feb 2016 17:20:07 +0100 [thread overview]
Message-ID: <1454516411-22858-1-git-send-email-s.hauer@pengutronix.de> (raw)
This series adds simple regmap support. It's overdue to have regmap
support in barebox since regmap can make register accesses far more
generic and convenient. More and more kernel code depends on it, so
here it is for barebox. Two drivers are switched over to regmap to
provide some users.
----------------------------------------------------------------
Sascha Hauer (3):
Add initial regmap support
mfd: mc13xxx: Switch to regmap support
ARM: i.MX ocotp: Switch to regmap support
Steffen Trumtrar (1):
bitops: Fix shift overflow in GENMASK macros
arch/arm/mach-imx/ocotp.c | 146 ++++++---------
drivers/base/Makefile | 1 +
drivers/base/regmap/Makefile | 1 +
drivers/base/regmap/internal.h | 18 ++
drivers/base/regmap/regmap.c | 398 +++++++++++++++++++++++++++++++++++++++++
drivers/mfd/mc13xxx.c | 123 ++++++-------
include/linux/bitops.h | 7 +-
include/regmap.h | 62 +++++++
8 files changed, 594 insertions(+), 162 deletions(-)
create mode 100644 drivers/base/regmap/Makefile
create mode 100644 drivers/base/regmap/internal.h
create mode 100644 drivers/base/regmap/regmap.c
create mode 100644 include/regmap.h
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2016-02-03 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 16:20 Sascha Hauer [this message]
2016-02-03 16:20 ` [PATCH 1/4] bitops: Fix shift overflow in GENMASK macros Sascha Hauer
2016-02-03 16:20 ` [PATCH 2/4] Add initial regmap support Sascha Hauer
2016-02-03 16:20 ` [PATCH 3/4] mfd: mc13xxx: Switch to " Sascha Hauer
2016-02-03 16:20 ` [PATCH 4/4] ARM: i.MX ocotp: " Sascha Hauer
2016-02-04 7:38 ` Stefan Christ
2016-02-04 7:43 ` Sascha Hauer
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=1454516411-22858-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@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