From: Eric Anholt <eric@anholt.net>
To: linux-rpi-kernel@lists.infradead.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Pawel Moll <pawel.moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Kevin Hilman <khilman@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org, Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>,
Rob Herring <robh+dt@kernel.org>,
Alexander Aring <alex.aring@gmail.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] Raspberry Pi power domains
Date: Wed, 16 Dec 2015 16:26:45 -0800 [thread overview]
Message-ID: <1450312009-1791-1-git-send-email-eric@anholt.net> (raw)
Update from v3 to move the driver under drivers/soc. I've placed it
under drivers/soc/bcm since that's how the other drivers under
drivers/soc are structured.
Alexander Aring (3):
ARM: bcm2835: add rpi power domain driver
dt-bindings: add rpi power domain driver bindings
ARM: bcm2835: Add the Raspberry Pi power domain driver to the DT.
Eric Anholt (1):
ARM: bcm2835: Define two new packets from the latest firmware.
.../bindings/soc/bcm/raspberrypi,bcm2835-power.txt | 47 ++++
arch/arm/boot/dts/bcm2835-rpi.dtsi | 11 +
arch/arm/boot/dts/bcm2835.dtsi | 2 +-
drivers/soc/Kconfig | 1 +
drivers/soc/Makefile | 1 +
drivers/soc/bcm/Kconfig | 9 +
drivers/soc/bcm/Makefile | 1 +
drivers/soc/bcm/raspberrypi-power.c | 247 +++++++++++++++++++++
include/dt-bindings/soc/raspberrypi-power.h | 41 ++++
include/soc/bcm2835/raspberrypi-firmware.h | 2 +
10 files changed, 361 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/soc/bcm/raspberrypi,bcm2835-power.txt
create mode 100644 drivers/soc/bcm/Kconfig
create mode 100644 drivers/soc/bcm/Makefile
create mode 100644 drivers/soc/bcm/raspberrypi-power.c
create mode 100644 include/dt-bindings/soc/raspberrypi-power.h
--
2.6.2
next reply other threads:[~2015-12-17 0:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 0:26 Eric Anholt [this message]
2015-12-17 0:26 ` [PATCH v4 1/4] ARM: bcm2835: Define two new packets from the latest firmware Eric Anholt
2015-12-17 0:26 ` [PATCH v4 2/4] ARM: bcm2835: add rpi power domain driver Eric Anholt
2015-12-17 16:28 ` Ulf Hansson
2015-12-22 4:02 ` Eric Anholt
2015-12-17 0:26 ` [PATCH v4 3/4] dt-bindings: add rpi power domain driver bindings Eric Anholt
2015-12-17 0:26 ` [PATCH v4 4/4] ARM: bcm2835: Add the Raspberry Pi power domain driver to the DT Eric Anholt
2015-12-17 22:32 ` [PATCH v4 0/4] Raspberry Pi power domains Kevin Hilman
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=1450312009-1791-1-git-send-email-eric@anholt.net \
--to=eric@anholt.net \
--cc=alex.aring@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=ulf.hansson@linaro.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).