linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 10/18] regulator: vexpress: Use regmap instead of custom interface
Date: Wed, 08 Jan 2014 18:25:31 +0000	[thread overview]
Message-ID: <1389205531.23721.40.camel@hornet> (raw)
In-Reply-To: <20131224122455.GY30815@sirena.org.uk>

On Tue, 2013-12-24 at 12:24 +0000, Mark Brown wrote:
> On Mon, Dec 23, 2013 at 04:23:42PM +0000, Pawel Moll wrote:
> 
> > This patch makes the Versatile Express regulator driver
> > use regmap interface, instead of custom vexpress config
> > one. It will request the regmap resource associated
> > with the device, which makes it pretty much hardware
> > agnostic.
> 
> If this change is making the operations hardware agnostic regmap based
> ones then they should be being either replaced with standard operations
> or standard operations being added.  It looks like you should be able to
> use the existing linear map operations.

Bad wording on my side. What I meant was: it doesn't matter what wacky
VE-specific interface is hidden behind the regmap, not it's a generic
regulator driver.

Having said that, I could create helpers for continuous (linear won't
cut - if you remember the continuous_voltage_range was introduced for
VE's sake) regulator, which would simply read/write value to a specified
register. Not sure how useful would that be, though. I doubt that such
"regulator" will appear anywhere outside VE world. And if so, this would
probably call for a "generic continuous regulator" driver and a relevant
DT binding, which I don't think anyone really wants. If your opinion
differs, I'm happy to botch something up.

Cheers!

Pawe?

  reply	other threads:[~2014-01-08 18:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23 16:23 [RFC 00/18] Versatile Express config rework Pawel Moll
     [not found] ` < 1387815830-8794-7-git-send-email-pawel.moll@arm.com>
     [not found] ` < 1387815830-8794-5-git-send-email-pawel.moll@arm.com>
2013-12-23 16:23 ` [RFC 05/18] driver core: Do not WARN when devres list is not empty at probe time Pawel Moll
     [not found] ` <1387815830-8794-4-git-send-email-pawel.moll@arm.com>
2013-12-23 17:26   ` [RFC 03/18] GPIO: gpio-generic: Add label to platform data Linus Walleij
2014-01-08 15:57     ` Pawel Moll
2014-01-14 10:30       ` Linus Walleij
2014-01-14 10:44         ` Pawel Moll
     [not found] ` <1387815830-8794-9-git-send-email-pawel.moll@arm.com>
2013-12-23 17:31   ` [RFC 08/18] hwmon: vexpress: Use regmap instead of custom interface Guenter Roeck
2014-01-08 15:57     ` Pawel Moll
     [not found] ` <1387815830-8794-3-git-send-email-pawel.moll@arm.com>
2013-12-23 19:28   ` [RFC 02/18] power/reset: vexpress: Use sched_clock as the time source John Stultz
2014-01-08 16:01     ` Pawel Moll
     [not found] ` <1387815830-8794-13-git-send-email-pawel.moll@arm.com>
2013-12-23 20:05   ` [RFC 12/18] clk: versatile: Split config options for sp810 and vexpress_osc Mike Turquette
2014-01-08 16:06     ` Pawel Moll
     [not found] ` <1387815830-8794-8-git-send-email-pawel.moll@arm.com>
2013-12-24 12:19   ` [RFC 07/18] regmap: debugfs: Always create "registers" & "access" files Mark Brown
2014-01-08 17:31     ` Pawel Moll
2014-01-08 18:00       ` Mark Brown
     [not found] ` <1387815830-8794-11-git-send-email-pawel.moll@arm.com>
2013-12-24 12:24   ` [RFC 10/18] regulator: vexpress: Use regmap instead of custom interface Mark Brown
2014-01-08 18:25     ` Pawel Moll [this message]
2014-01-09 13:35       ` Mark Brown
     [not found] ` <1387815830-8794-7-git-send-email-pawel.moll@arm.com>
2013-12-24 12:45   ` [RFC 06/18] regmap: Formalise use of non-bus context Mark Brown
2014-01-09 13:08     ` Pawel Moll
2014-01-09 13:34       ` Mark Brown
2014-01-09 15:47         ` Pawel Moll
2014-01-16 17:09       ` Grant Likely
2014-01-16 17:20         ` Pawel Moll
     [not found] ` <1387815830-8794-2-git-send-email-pawel.moll@arm.com>
2014-01-06  9:48   ` [RFC 01/18] mfd: syscon: Consider platform data a regmap config name Lee Jones
2014-01-06 10:20     ` Lee Jones
     [not found] ` <1387815830-8794-19-git-send-email-pawel.moll@arm.com>
2014-01-06 10:40   ` [RFC 18/18] mfd: vexpress: Split sysreg functions into MFD cells Lee Jones
2014-01-08 16:17     ` Pawel Moll
     [not found] ` <1387815830-8794-5-git-send-email-pawel.moll@arm.com>
2014-01-08 17:28   ` [RFC 04/18] driver core & of: Mark of_nodes of added device as populated Rob Herring
2014-01-16 17:03     ` Grant Likely

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=1389205531.23721.40.camel@hornet \
    --to=pawel.moll@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).