From: mporter@linaro.org (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] BCM59056 PMU regulator support
Date: Tue, 11 Mar 2014 11:46:10 -0400 [thread overview]
Message-ID: <1394552775-31264-1-git-send-email-mporter@linaro.org> (raw)
The BCM59056 is a multi-function power management unit used with the
BCM281xx family of SoCs. This series adds an MFD and voltage regulator
driver to support the BCM59056. The bcm28155-ap DT support is updated
to enable use of regulators on the otg and sdhci peripherals.
Changes since v2:
- Move to mfd_add_devices() approach, eliminating representation
of the regulator block as a hardware subdevice. Regulators are
listed in the PMU binding and referenced via the parent device
of_node by the regulator driver.
- Allow mfd driver to build as module
- Remove regulator constraints from the .dtsi include only the
board-specific constraints in the board .dts.
Changes since v1:
- renamed to bcm590xx to accomodate future family parts
- remove use of subsys_initcall
- fix BCM590XX_MAX_REGISTER value
- remove unused chip id in mfd of/i2c matching
- switch to of_platform_populate() in mfd
- update binding to single document with regulators as optional
properties in the regulator subdevice IP description
- remove unused regulator get/set mode ops
- remove unneeded regulator NULL constraint check
- regulators property is optional, allow the driver to probe
when it is missing
- move of_node presence check into bcm590xx_parse_dt_reg_data()
Matt Porter (5):
mfd: add bcm590xx pmu DT binding
mfd: add bcm590xx pmu driver
regulator: add bcm590xx regulator driver
ARM: configs: bcm_defconfig: enable bcm590xx regulator support
ARM: dts: add bcm590xx pmu support and enable for bcm28155-ap
Documentation/devicetree/bindings/mfd/bcm590xx.txt | 41 ++
arch/arm/boot/dts/bcm28155-ap.dts | 47 ++-
arch/arm/boot/dts/bcm59056.dtsi | 77 ++++
arch/arm/configs/bcm_defconfig | 7 +
drivers/mfd/Kconfig | 8 +
drivers/mfd/Makefile | 1 +
drivers/mfd/bcm590xx.c | 93 +++++
drivers/regulator/Kconfig | 8 +
drivers/regulator/Makefile | 1 +
drivers/regulator/bcm590xx-regulator.c | 413 +++++++++++++++++++++
include/linux/mfd/bcm590xx.h | 31 ++
11 files changed, 726 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/mfd/bcm590xx.txt
create mode 100644 arch/arm/boot/dts/bcm59056.dtsi
create mode 100644 drivers/mfd/bcm590xx.c
create mode 100644 drivers/regulator/bcm590xx-regulator.c
create mode 100644 include/linux/mfd/bcm590xx.h
--
1.8.4
next reply other threads:[~2014-03-11 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 15:46 Matt Porter [this message]
2014-03-11 15:46 ` [PATCH v3 1/5] mfd: add bcm590xx pmu DT binding Matt Porter
2014-03-11 15:46 ` [PATCH v3 2/5] mfd: add bcm590xx pmu driver Matt Porter
2014-03-11 16:08 ` Lee Jones
2014-03-11 22:19 ` Matt Porter
2014-03-11 22:45 ` Lee Jones
2014-03-11 23:25 ` Matt Porter
2014-03-12 0:40 ` Mark Brown
2014-03-12 0:57 ` Matt Porter
2014-03-12 9:23 ` Lee Jones
2014-03-12 9:35 ` Lee Jones
2014-03-11 15:46 ` [PATCH v3 3/5] regulator: add bcm590xx regulator driver Matt Porter
2014-03-11 18:52 ` Mark Brown
2014-03-11 15:46 ` [PATCH v3 4/5] ARM: configs: bcm_defconfig: enable bcm590xx regulator support Matt Porter
2014-03-11 15:46 ` [PATCH v3 5/5] ARM: dts: add bcm590xx pmu support and enable for bcm28155-ap Matt Porter
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=1394552775-31264-1-git-send-email-mporter@linaro.org \
--to=mporter@linaro.org \
--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).