From: Davide Ciminaghi <ciminaghi@gnudd.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, rubini@gnudd.com,
giancarlo.asnaghi@st.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] sta2x11-mfd : add apb-soc regs driver and factor out common code
Date: Wed, 26 Sep 2012 16:56:15 +0200 [thread overview]
Message-ID: <20120926145615.GJ10147@mail.gnudd.com> (raw)
In-Reply-To: <20120925192048.GA17038@sirena.org.uk>
On Tue, Sep 25, 2012 at 08:20:48PM +0100, Mark Brown wrote:
> On Wed, Sep 12, 2012 at 12:22:47PM +0200, ciminaghi@gnudd.com wrote:
> > From: Davide Ciminaghi <ciminaghi@gnudd.com>
> >
> > A driver for the apb-soc registers is needed by the clock
> > infrastructure code to configure and control clocks on the sta2x11
> > chip.
> > Since some of the functions in sta2x11-mfd.c were almost identical
> > for the two existing platform devices, the following changes
> > have been performed to avoid further code duplication while
> > adding the apb-soc-regs driver:
>
> Glancing at the diff here this looks a lot like regmap-mmio... not sure
> if it is or not, though.
that would be ideal, but I also need to deal with the common clock framework,
which doesn't support regmap: clk_register_divider(), clk_register_mux(),
clk_register_gate(), all take a void __iomem * to access clock control
registers, so as far as I can understand we can't use regmap, unless of
course we convert the common clock framework to regmap.
Thanks
Davide
next prev parent reply other threads:[~2012-09-26 14:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 10:22 [PATCH 0/8 RESEND] sta2x11-mfd patches ciminaghi
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 [this message]
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
2012-09-12 10:11 ` [PATCH 1/8] sta2x11-mfd : add apb-soc regs driver and factor out common code 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=20120926145615.GJ10147@mail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.