linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Mark Brown <broonie@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	Liam Girdwood <lgirdwood@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: [PATCH v2 0/2] regulator: Add support for parallel regulators
Date: Tue, 12 Jan 2016 14:37:20 +0100	[thread overview]
Message-ID: <1452605842-9317-1-git-send-email-maxime.ripard@free-electrons.com> (raw)

Hi,

On some boards, devices consuming a lot of power cannot use a single
regulator, but few of them in parallel to spread the consumption.

In such a case, we must ensure that all these regulators are kept in
sync.

Since this is something that is totally board specific, it should
obviously not be handle by each and every customer drivers that might
be driving a device wired this way on a particular board.

Instead, we implemented a regulator driver that just aggregates
several parent regulators and just forwards the regulators calls to
them.

Let me know what you think,
Maxime

Changes from v1:
  - Added documentation
  - Fixed an error in the is_enabled callback returned value
  - Unwind the enable and disable callbacks in case of a failure
  - Added a depency on CONFIG_OF
  - Added the missing module device table

Maxime Ripard (2):
  regulator: Add coupled regulator
  ARM: sunxi: chip: Add Wifi chip

 .../bindings/regulator/coupled-voltage.txt         |  18 ++
 arch/arm/boot/dts/sun5i-r8-chip.dts                |  44 ++-
 drivers/regulator/Kconfig                          |   8 +
 drivers/regulator/Makefile                         |   1 +
 drivers/regulator/coupled-voltage-regulator.c      | 299 +++++++++++++++++++++
 5 files changed, 369 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/regulator/coupled-voltage.txt
 create mode 100644 drivers/regulator/coupled-voltage-regulator.c

-- 
2.6.4

             reply	other threads:[~2016-01-12 13:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 13:37 Maxime Ripard [this message]
2016-01-12 13:37 ` [PATCH v2 1/2] regulator: Add coupled regulator Maxime Ripard
2016-01-12 14:31   ` Rob Herring
2016-01-15  8:57     ` Maxime Ripard
2016-01-17  0:04       ` Rob Herring
2016-01-18 16:25         ` Mark Brown
2016-01-21 15:46           ` Maxime Ripard
2016-01-21 16:28             ` Mark Brown
2016-02-05 14:33               ` Maxime Ripard
2016-02-05 15:32                 ` Mark Brown
2016-11-07 15:47                   ` Maxime Ripard
2016-11-11 16:46                     ` Mark Brown
2016-01-12 13:37 ` [PATCH v2 2/2] ARM: sunxi: chip: Add Wifi chip Maxime Ripard

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=1452605842-9317-1-git-send-email-maxime.ripard@free-electrons.com \
    --to=maxime.ripard@free-electrons.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wens@csie.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).