From: ciminaghi@gnudd.com
To: sameo@linux.intel.com, rubini@gnudd.com, giancarlo.asnaghi@st.com
Cc: linux-kernel@vger.kernel.org, Davide Ciminaghi <ciminaghi@gnudd.com>
Subject: [PATCH 0/8 RESEND] sta2x11-mfd patches
Date: Wed, 12 Sep 2012 12:22:46 +0200 [thread overview]
Message-ID: <1347445374-32140-1-git-send-email-ciminaghi@gnudd.com> (raw)
From: Davide Ciminaghi <ciminaghi@gnudd.com>
Hi,
this is a resend of a patchset dated Jun 10th (see
https://lkml.org/lkml/2012/6/10/188) even if some of the
commits have been squashed.
I'm working on the implementation of the common clock framework
for the STA2X11 (aka CONNEXT) soc.
To configure, enable and disable clocks, some general purpose
registers (apb-soc-registers) must be accessed. Such registers
can be reached through bar #1 of a multifunction pci device,
which is not covered by the current version of sta2x11-mfd.
This patch series adds support for the apb-soc-registers device
and rearranges the sta2x11-mfd driver to avoid unnecessary
code duplications and to cope with the increased number of platform
devices.
Davide
Davide Ciminaghi (8):
sta2x11-mfd : add apb-soc regs driver and factor out common code
sta2x11-mfd : add sta2x11_mfd_get_regs_data() function
sta2x11-mfd : use defines for platform devices' names
sta2x11-mfd : only add sta2x11_mfd if it hasn't already been added
sta2x11-mfd : platform probe: don't mind about gpio platform data
sta2x11-mfd : use one lock per device instead of one lock per mfd.
sta2x11-mfd : add defines for some sta2x11 sctl registers.
sta2x11-mfd : add myself to copyright
drivers/mfd/sta2x11-mfd.c | 416 ++++++++++++++++++++++++++-------------
include/linux/mfd/sta2x11-mfd.h | 190 ++++++++++++++++++-
2 files changed, 470 insertions(+), 136 deletions(-)
--
1.7.9.1
next reply other threads:[~2012-09-12 10:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 10:22 ciminaghi [this message]
2012-09-12 10:22 ` [PATCH 1/8] sta2x11-mfd : add apb-soc regs driver and factor out common code ciminaghi
2012-09-25 19:20 ` Mark Brown
2012-09-26 14:56 ` Davide Ciminaghi
2012-09-26 15:04 ` Mark Brown
2012-09-26 16:31 ` Davide Ciminaghi
2012-09-26 16:49 ` Mark Brown
2012-09-27 8:39 ` Davide Ciminaghi
2012-09-27 8:56 ` Davide Ciminaghi
2012-09-27 13:41 ` Davide Ciminaghi
2012-09-27 13:49 ` Mark Brown
2012-09-28 8:43 ` Davide Ciminaghi
2012-09-28 10:52 ` Mark Brown
2012-09-27 14:13 ` Alan Cox
2012-09-28 15:29 ` Davide Ciminaghi
2012-09-12 10:22 ` [PATCH 2/8] sta2x11-mfd : add sta2x11_mfd_get_regs_data() function ciminaghi
2012-09-12 10:22 ` [PATCH 3/8] sta2x11-mfd : use defines for platform devices' names ciminaghi
2012-09-12 10:22 ` [PATCH 4/8] sta2x11-mfd : only add sta2x11_mfd if it hasn't already been added ciminaghi
2012-09-12 10:22 ` [PATCH 5/8] sta2x11-mfd : platform probe: don't mind about gpio platform data ciminaghi
2012-09-12 10:22 ` [PATCH 6/8] sta2x11-mfd : use one lock per device instead of one lock per mfd ciminaghi
2012-09-12 10:22 ` [PATCH 7/8] sta2x11-mfd : add defines for some sta2x11 sctl registers ciminaghi
2012-09-12 10:22 ` [PATCH 8/8] sta2x11-mfd : add myself to copyright ciminaghi
2012-09-16 21:25 ` [PATCH 0/8 RESEND] sta2x11-mfd patches Alessandro Rubini
-- strict thread matches above, loose matches on Subject: below --
2012-09-12 10:11 ciminaghi
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=1347445374-32140-1-git-send-email-ciminaghi@gnudd.com \
--to=ciminaghi@gnudd.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®