From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Broadcom drivers changes for 4.4 (try 2)
Date: Sat, 24 Oct 2015 13:36:20 -0700 [thread overview]
Message-ID: <1445718981-13552-1-git-send-email-f.fainelli@gmail.com> (raw)
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
are available in the git repository at:
https://github.com/Broadcom/stblinux tags/arm/soc/for-4.4/rpi-drivers
for you to fetch changes up to 16134b3bc317c571e953d18196acf0a92afda5ff:
ARM: bcm2835: add mutual inclusion protection (2015-10-24 13:15:58 -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 adds the actual firmware driver and Alexander fixes the header file which
was missing include guards.
----------------------------------------------------------------
Alexander Aring (1):
ARM: bcm2835: add mutual inclusion protection
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 | 120 +++++++++++++
4 files changed, 388 insertions(+)
create mode 100644 drivers/firmware/raspberrypi.c
create mode 100644 include/soc/bcm2835/raspberrypi-firmware.h
next reply other threads:[~2015-10-24 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 20:36 Florian Fainelli [this message]
2015-10-24 20:36 ` [GIT PULL 1/2] Broadcom Device Tree changes for 4.4 (Part 2, try2) Florian Fainelli
2015-10-24 20:38 ` Florian Fainelli
2015-10-26 5:28 ` Olof Johansson
2015-10-26 5:27 ` [GIT PULL 2/2] Broadcom drivers changes for 4.4 (try 2) Olof Johansson
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=1445718981-13552-1-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--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).