Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754655AbbK3P3N (ORCPT ); Mon, 30 Nov 2015 10:29:13 -0500 Received: from down.free-electrons.com ([37.187.137.238]:39085 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754061AbbK3P3K (ORCPT ); Mon, 30 Nov 2015 10:29:10 -0500 From: Maxime Ripard To: Mark Brown , Chen-Yu Tsai , Liam Girdwood Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Maxime Ripard Subject: [PATCH 0/2] regulator: Add support for parallel regulators Date: Mon, 30 Nov 2015 16:29:04 +0100 Message-Id: <1448897346-17780-1-git-send-email-maxime.ripard@free-electrons.com> X-Mailer: git-send-email 2.6.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1300 Lines: 39 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 Maxime Ripard (2): regulator: Add coupled regulator ARM: sunxi: chip: Add Wifi chip arch/arm/boot/dts/sun5i-r8-chip.dts | 44 ++++- drivers/regulator/Kconfig | 7 + drivers/regulator/Makefile | 1 + drivers/regulator/coupled-voltage-regulator.c | 241 ++++++++++++++++++++++++++ 4 files changed, 292 insertions(+), 1 deletion(-) create mode 100644 drivers/regulator/coupled-voltage-regulator.c -- 2.6.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/