From: ciminaghi@gnudd.com
To: sameo@linux.intel.com, rubini@gnudd.com,
giancarlo.asnaghi@st.com, broonie@opensource.wolfsonmicro.com
Cc: linux-kernel@vger.kernel.org, Davide Ciminaghi <ciminaghi@gnudd.com>
Subject: [PATCH v3 00/10] sta2x11-mfd patches
Date: Fri, 9 Nov 2012 15:19:51 +0100 [thread overview]
Message-ID: <1352470801-2418-1-git-send-email-ciminaghi@gnudd.com> (raw)
From: Davide Ciminaghi <ciminaghi@gnudd.com>
Hi,
this is v3 of a patchset submitted on
2012/10/22 (see https://lkml.org/lkml/2012/10/22/290)
and 2012/09/12 (see https://lkml.org/lkml/2012/9/12/139).
Here's a summary of changes in v3:
* Regmap support fix:
sta2x11_apb_soc_regs_writeable_reg() fixed as
suggested by Mark Brown
(see https://lkml.org/lkml/2012/10/23/448)
* Regmap support fix: regmap field in struct
sta2x11_mfd (a single struct regmap * in v2) becomes
an array of struct regmap pointers, one per platform
device.
Davide Ciminaghi (10):
drivers/mfd/sta2x11-mfd: add apb-soc regs driver and factor out
common code
drivers/mfd/sta2x11-mfd: add regmap support
drivers/mfd/sta2x11-mfd: add sta2x11_mfd_get_regs_data() function
drivers/mfd/sta2x11-mfd: use defines for platform devices' names
drivers/mfd/sta2x11-mfd: only add sta2x11_mfd if it hasn't already
been added
drivers/mfd/sta2x11-mfd: platform probe: don't mind about gpio
platform data
drivers/mfd/sta2x11-mfd: use one lock per device instead of one lock
per mfd
drivers/mfd/sta2x11-mfd: add scr (otp registers) platform driver
drivers/mfd/sta2x11-mfd: add defines for some sta2x11 sctl registers
drivers/mfd/sta2x11-mfd: add myself to copyright
drivers/mfd/Kconfig | 1 +
drivers/mfd/sta2x11-mfd.c | 532 +++++++++++++++++++++++++++------------
include/linux/mfd/sta2x11-mfd.h | 198 ++++++++++++++-
3 files changed, 574 insertions(+), 157 deletions(-)
--
1.7.10.4
next reply other threads:[~2012-11-09 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 14:19 ciminaghi [this message]
2012-11-09 14:19 ` [PATCH 01/10] drivers/mfd/sta2x11-mfd: add apb-soc regs driver and factor out common code ciminaghi
2012-11-09 14:19 ` [PATCH 02/10] drivers/mfd/sta2x11-mfd: add regmap support ciminaghi
2012-11-09 14:19 ` [PATCH 03/10] drivers/mfd/sta2x11-mfd: add sta2x11_mfd_get_regs_data() function ciminaghi
2012-11-09 14:19 ` [PATCH 04/10] drivers/mfd/sta2x11-mfd: use defines for platform devices' names ciminaghi
2012-11-09 14:19 ` [PATCH 05/10] drivers/mfd/sta2x11-mfd: only add sta2x11_mfd if it hasn't already been added ciminaghi
2012-11-09 14:19 ` [PATCH 06/10] drivers/mfd/sta2x11-mfd: platform probe: don't mind about gpio platform data ciminaghi
2012-11-09 14:19 ` [PATCH 07/10] drivers/mfd/sta2x11-mfd: use one lock per device instead of one lock per mfd ciminaghi
2012-11-09 14:19 ` [PATCH 08/10] drivers/mfd/sta2x11-mfd: add scr (otp registers) platform driver ciminaghi
2012-11-09 14:20 ` [PATCH 09/10] drivers/mfd/sta2x11-mfd: add defines for some sta2x11 sctl registers ciminaghi
2012-11-09 14:20 ` [PATCH 10/10] drivers/mfd/sta2x11-mfd: add myself to copyright ciminaghi
2012-11-19 17:58 ` [PATCH v3 00/10] sta2x11-mfd patches Samuel Ortiz
2012-11-19 18:44 ` Samuel Ortiz
2012-11-20 0:19 ` 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=1352470801-2418-1-git-send-email-ciminaghi@gnudd.com \
--to=ciminaghi@gnudd.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=giancarlo.asnaghi@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@gnudd.com \
--cc=sameo@linux.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®