From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/6 v2] Broadcom drivers changes for 4.19
Date: Fri, 13 Jul 2018 07:38:20 -0700 [thread overview]
Message-ID: <20180713143821.1514-5-f.fainelli@gmail.com> (raw)
In-Reply-To: <20180713143821.1514-1-f.fainelli@gmail.com>
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.19/drivers
for you to fetch changes up to 5773898b3b32f0e66059031afca5406702e89f9d:
Merge tag 'bcm2835-drivers-next-2018-07-03' into drivers/next (2018-07-09 10:47:30 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM/ARM64/MIPS SoCs drivers changes
for 4.19, please pull the following:
- Doug updates the low-level suspend/resume code for ARM SoCs to support
the latest rev B3.0 memory controllers found on newer chips with an
appropriate match structure to perform the correct entry sequencing
- Florian updates the Device Tree binding document for these memory
controllers to list all possible compatible strings that exist given
the supported memory controllers.
- Stefan adds the GET_THROTTLED firmware property value that is required
for the Rasperry Pi voltage monitoring driver and updates the
Raspberry Pi firmware driver accordingly to register such a device
using the HWMON subsystem. Finally he adds support for reporting under
voltage conditions using a specialized HWMON driver.
----------------------------------------------------------------
Doug Berger (1):
soc: bcm: brcmstb: pm: Add support for newer rev B3.0 controllers
Florian Fainelli (2):
soc: bcm: brcmstb: Add missing DDR MEMC compatible strings
Merge tag 'bcm2835-drivers-next-2018-07-03' into drivers/next
Kees Cook (1):
firmware: raspberrypi: Remove VLA usage
Stefan Wahren (3):
ARM: bcm2835: Add GET_THROTTLED firmware property
hwmon: Add support for RPi voltage sensor
firmware: raspberrypi: Register hwmon driver
.../devicetree/bindings/arm/bcm/brcm,brcmstb.txt | 4 +
Documentation/hwmon/raspberrypi-hwmon | 22 +++
drivers/firmware/raspberrypi.c | 29 +++-
drivers/hwmon/Kconfig | 10 ++
drivers/hwmon/Makefile | 1 +
drivers/hwmon/raspberrypi-hwmon.c | 166 +++++++++++++++++++++
drivers/soc/bcm/brcmstb/pm/pm-arm.c | 16 ++
include/soc/bcm2835/raspberrypi-firmware.h | 1 +
8 files changed, 247 insertions(+), 2 deletions(-)
create mode 100644 Documentation/hwmon/raspberrypi-hwmon
create mode 100644 drivers/hwmon/raspberrypi-hwmon.c
next prev parent reply other threads:[~2018-07-13 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 14:38 [GIT PULL 1/6 v2] Broadcom defconfig changes for 4.19 Florian Fainelli
2018-07-13 14:38 ` [GIT PULL 2/6 v2] Broadcom defconfig-arm64 " Florian Fainelli
2018-07-13 14:38 ` [GIT PULL 3/6 v2] Broadcom devicetree " Florian Fainelli
2018-07-13 14:38 ` [GIT PULL 4/6 v2] Broadcom devicetree-arm64 " Florian Fainelli
2018-07-13 14:38 ` Florian Fainelli [this message]
2018-07-13 14:38 ` [GIT PULL 6/6 v2] Broadcom soc " Florian Fainelli
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=20180713143821.1514-5-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).