public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: dd diasemi <dd.diasemi@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Anthony Olech <Anthony.Olech@diasemi.com>,
	gg@slimlogic.co.uk, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] regmap: Add support for register paging
Date: Fri, 11 May 2012 15:10:10 +0100	[thread overview]
Message-ID: <20120511141010.GE3960@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAEqHmAtm4-TkdmLSc-HUPMo_Fyw4WK+d6Xj=X9z1m4kK1A0oJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]

On Fri, May 11, 2012 at 03:55:54PM +0200, dd diasemi wrote:
> On Fri, May 11, 2012 at 1:27 PM, Mark Brown

> > right now the diff is pretty hard to read so I may have missed some
> > issues and I'm also reluctant to add any additional combinations of
> > build options that aren't actually needed.

> I did some rearrangement in the code, like splitting functions into
> halves, so it is hard to read it from the patch. However, I have not
> changed present functionality and if paging is not initialised, regmap
> behaves the same way as before.

Ah, if you're going to do this sort of thing the best way to do it is to
rearrange the code first as one patch then add a second patch adding the
new functionality.  That way the code motion isn't mixed up with the new
code which makes review easier.

> I will prepare patch without compilation flag, as it is not so important.

Thanks.

> > One other fun thing which just occurred to me is that I've got a bunch
> > of chips which have several independantly paged regions.  I'm not sure
> > that's really worth handling here, though.

> I have more advanced solution, which actually makes register mapping
> split into virtual address ranges. This may solve many problems,
> including giving capability to support several indirect register
> ranges at once.
> Let me know, what you think about this API?

I think that sounds roughly like what I was thinking of so it's probably
sensible but obviously it'll depend on the implementation.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-05-11 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 10:55 [PATCH] regmap: Add support for register paging Krystian Garbaciak
2012-05-11 12:27 ` Mark Brown
2012-05-11 13:55   ` dd diasemi
2012-05-11 14:10     ` Mark Brown [this message]
2012-05-11 15:33       ` dd diasemi

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=20120511141010.GE3960@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=Anthony.Olech@diasemi.com \
    --cc=dd.diasemi@gmail.com \
    --cc=gg@slimlogic.co.uk \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.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