public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: broonie@kernel.org
Cc: lgirdwood@gmail.com, lee.jones@linaro.org, sameo@linux.intel.com,
	linux-kernel@vger.kernel.org,
	patches@opensource.wolfsonmicro.com,
	Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Subject: [PATCH 0/3 v2] Add regulator supply alias
Date: Tue, 15 Oct 2013 20:14:19 +0100	[thread overview]
Message-ID: <1381864462-26167-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)

This series of patchs adds feature to allow an alias to
be created for regulator supply lookup. This aliases will
perform the lookup on a different device from that requested
by the end user. We also add features into the MFD core to
easily map supplies from a child device to the main MFD
device.

The main use case for this is when an MFD device is
registered as a single node through device tree. It allows
frameworks dealing with the individual child drivers to
locate their regulators on the main MFD device, without any
prior knowledge of its existance. An implementation is given
using the arizona driver which has its supplies registered
this way through device tree.

This patch series is based on Mark's regulator for-next
branch.

One thing I would be interested on improving is
the function names they get very long. For example
devm_regulator_register_bulk_supply_alias, I would wonder
if swapping the register for an add and perhaps swapping
supply_alias for just alias would be acceptable? This would
give us devm_regulator_get_alias() which is a bit more
reasonable in terms of length although perhaps slightly less
idiomatic.

Changes from version 1:
 - Added bulk and devm versions for all the calls
 - Registration of the aliases is added to the MFD framework
   rather than done in the driver probe

Charles Keepax (3):
  regulator: core: Add ability to create a lookup alias for supply
  mfd: Allow mapping regulator supplies to MFD device from children
  mfd: arizona: Specify supply mappings for Arizona CODECs

 arch/arm/mach-s3c64xx/mach-crag6410.c |   12 ---
 drivers/mfd/arizona-core.c            |   32 ++++++-
 drivers/mfd/mfd-core.c                |   22 ++++-
 drivers/regulator/core.c              |  170 +++++++++++++++++++++++++++++++++
 drivers/regulator/devres.c            |  163 +++++++++++++++++++++++++++++++
 include/linux/mfd/core.h              |    6 +
 include/linux/regulator/consumer.h    |   79 +++++++++++++++
 7 files changed, 464 insertions(+), 20 deletions(-)

-- 
1.7.2.5


             reply	other threads:[~2013-10-15 19:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 19:14 Charles Keepax [this message]
2013-10-15 19:14 ` [PATCH 1/3 v2] regulator: core: Add ability to create a lookup alias for supply Charles Keepax
2013-10-17 23:59   ` Mark Brown
2013-10-18  6:53     ` Lee Jones
2013-10-18 13:06       ` Mark Brown
2013-10-22 17:00         ` Lee Jones
2013-10-15 19:14 ` [PATCH 2/3 v2] mfd: Allow mapping regulator supplies to MFD device from children Charles Keepax
2013-10-23 11:17   ` Mark Brown
2013-10-15 19:14 ` [PATCH 3/3 v2] mfd: arizona: Specify supply mappings for Arizona CODECs Charles Keepax
2013-10-23 11:18   ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2013-10-15 19:12 [PATCH 0/3 v2] Add regulator supply alias Charles Keepax

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=1381864462-26167-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.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