From: Eric Anholt <eric@anholt.net>
To: f.fainelli@gmail.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>
Subject: [GIT PULL] RPi SOC changes for v4.3
Date: Wed, 12 Aug 2015 11:45:13 -0700 [thread overview]
Message-ID: <87oaic8hxi.fsf@eliezer.anholt.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
Following Lee's forwarding of the DT changes for the firmware driver for
4.3, here's the associated driver for the brcm arm-soc tree.
I think this is the first time RPi changes have been forwarded through
Florian. It was suggested by Florian when I was discussing RPi
upstreaming with him and Arnd. I think it makes sense, since general
-next trees for Broadcom are maintained there, and he's willing to
accept pull requests at any point.
The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git repository at:
http://github.com/anholt/linux tags/rpi-soc-for-4.3-v1
for you to fetch changes up to d39ae82e65dc538295eea0384ed1ad8752dabbae:
ARM: bcm2835: Add the Raspberry Pi firmware driver (2015-08-11 11:27:13 -0700)
----------------------------------------------------------------
This pull request contains the Raspberry Pi firmware driver, for
communicating with the VPU which has exclusive control of some of the
peripherals.
----------------------------------------------------------------
Eric Anholt (1):
ARM: bcm2835: Add the Raspberry Pi firmware driver
drivers/firmware/Kconfig | 7 +
drivers/firmware/Makefile | 1 +
drivers/firmware/raspberrypi.c | 260 +++++++++++++++++++++++++++++
include/soc/bcm2835/raspberrypi-firmware.h | 115 +++++++++++++
4 files changed, 383 insertions(+)
create mode 100644 drivers/firmware/raspberrypi.c
create mode 100644 include/soc/bcm2835/raspberrypi-firmware.h
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
reply other threads:[~2015-08-12 18:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87oaic8hxi.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®