From: Mark Brown <broonie@kernel.org>
To: Michal Simek <monstr@monstr.eu>
Cc: Lee Jones <lee.jones@linaro.org>,
Michal Simek <michal.simek@xilinx.com>,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/2] mfd: syscon: Support early initialization
Date: Wed, 19 Feb 2014 22:59:38 +0900 [thread overview]
Message-ID: <20140219135938.GY2669@sirena.org.uk> (raw)
In-Reply-To: <5304B6E8.1090508@monstr.eu>
[-- Attachment #1: e --]
[-- Type: text/plain, Size: 527 bytes --]
On Wed, Feb 19, 2014 at 02:51:36PM +0100, Michal Simek wrote:
> On 02/19/2014 01:17 PM, Mark Brown wrote:
> > Like I said I've never seen the user you're adding for the regmap API so
> > I've no particular opinion on it.
> 2/2 is the code where I would like to use this when clk subsystem
> start to use better io helper functions then just static inline
> clk_readl/clk_writel.
> Then my 2/2 driver will be just nicer than current implementation.
OK, but I still haven't seen the code (or Lee's concerns for that
matter).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-19 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 11:04 [RFC PATCH v2 0/2] Syscon early initialization Michal Simek
2014-02-19 11:04 ` [RFC PATCH v2 1/2] mfd: syscon: Support " Michal Simek
2014-02-19 11:14 ` Alexander Shiyan
2014-02-19 11:16 ` Alexander Shiyan
2014-02-19 11:41 ` Lee Jones
2014-02-19 11:44 ` Michal Simek
2014-02-19 12:17 ` Mark Brown
2014-02-19 13:51 ` Michal Simek
2014-02-19 13:59 ` Mark Brown [this message]
2014-05-09 12:13 ` Tushar Behera
2014-02-19 11:04 ` [RFC PATCH v2 2/2] ARM: zynq: Use early syscon initialization Michal Simek
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=20140219135938.GY2669@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--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;
as well as URLs for NNTP newsgroup(s).