From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Lee Jones <lee.jones@linaro.org>,
Stefan Wahren <stefan.wahren@i2se.com>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Eric Anholt <eric@anholt.net>
Subject: [PATCH v4 0/5] BCM2835 PM driver
Date: Wed, 12 Dec 2018 15:51:45 -0800 [thread overview]
Message-ID: <20181212235150.6491-1-eric@anholt.net> (raw)
v4 adds the system-power-controller node to the binding as requested
by Stefan. No driver changes are added to make the power controller
behavior optional yet, since it's really unrelated to this series.
Eric Anholt (5):
dt-bindings: soc: Add a new binding for the BCM2835 PM node. (v4)
bcm2835-pm: Move bcm2835-watchdog's DT probe to an MFD.
soc: bcm: bcm2835-pm: Add support for power domains under a new
binding.
ARM: bcm283x: Extend the WDT DT node out to cover the whole PM block.
(v4)
ARM: bcm283x: Switch V3D over to using the PM driver instead of
firmware.
.../bindings/soc/bcm/brcm,bcm2835-pm.txt | 46 ++
arch/arm/boot/dts/bcm2835-rpi.dtsi | 4 -
arch/arm/boot/dts/bcm283x.dtsi | 17 +-
arch/arm/mach-bcm/Kconfig | 1 +
drivers/mfd/Makefile | 1 +
drivers/mfd/bcm2835-pm.c | 92 +++
drivers/soc/bcm/Kconfig | 11 +
drivers/soc/bcm/Makefile | 1 +
drivers/soc/bcm/bcm2835-power.c | 661 ++++++++++++++++++
drivers/watchdog/bcm2835_wdt.c | 26 +-
include/dt-bindings/soc/bcm2835-pm.h | 28 +
include/linux/mfd/bcm2835-pm.h | 14 +
12 files changed, 878 insertions(+), 24 deletions(-)
create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-pm.txt
create mode 100644 drivers/mfd/bcm2835-pm.c
create mode 100644 drivers/soc/bcm/bcm2835-power.c
create mode 100644 include/dt-bindings/soc/bcm2835-pm.h
create mode 100644 include/linux/mfd/bcm2835-pm.h
--
2.20.0.rc1
next reply other threads:[~2018-12-12 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 23:51 Eric Anholt [this message]
2018-12-12 23:51 ` [PATCH v4 1/5] dt-bindings: soc: Add a new binding for the BCM2835 PM node. (v4) Eric Anholt
2018-12-12 23:51 ` [PATCH v4 2/5] bcm2835-pm: Move bcm2835-watchdog's DT probe to an MFD Eric Anholt
2018-12-12 23:51 ` [PATCH v4 3/5] soc: bcm: bcm2835-pm: Add support for power domains under a new binding Eric Anholt
2018-12-12 23:51 ` [PATCH v4 4/5] ARM: bcm283x: Extend the WDT DT node out to cover the whole PM block. (v4) Eric Anholt
2018-12-12 23:51 ` [PATCH v4 5/5] ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware Eric Anholt
2019-01-03 15:56 ` [PATCH v4 0/5] BCM2835 PM driver Stefan Wahren
2019-01-09 19:00 ` Stefan Wahren
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=20181212235150.6491-1-eric@anholt.net \
--to=eric@anholt.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=wim@linux-watchdog.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).