From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Brian Norris <computersforpeace@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
"maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
Doug Berger <opendmb@gmail.com>,
Justin Chen <justinpopo6@gmail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] soc: bcm: brcmstb: Updates to support newer controllers
Date: Fri, 11 May 2018 15:02:40 -0700 [thread overview]
Message-ID: <20180511220242.837-1-f.fainelli@gmail.com> (raw)
Hi all,
This patch series adds support for newer reveisions of the memory controller
which is necessary to make sure we do use the right programming sequence to
enter S2 and S3 suspend/resume modes.
Doug Berger (1):
soc: bcm: brcmstb: pm: Add support for newer rev B3.0 controllers
Florian Fainelli (1):
soc: bcm: brcmstb: Add missing DDR MEMC compatible strings
.../devicetree/bindings/arm/bcm/brcm,brcmstb.txt | 4 ++++
drivers/soc/bcm/brcmstb/pm/pm-arm.c | 16 ++++++++++++++++
2 files changed, 20 insertions(+)
--
2.14.1
next reply other threads:[~2018-05-11 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 22:02 Florian Fainelli [this message]
2018-05-11 22:02 ` [PATCH 1/2] soc: bcm: brcmstb: pm: Add support for newer rev B3.0 controllers Florian Fainelli
2018-05-22 22:30 ` Rob Herring
2018-06-04 21:16 ` Florian Fainelli
2018-06-04 21:15 ` Florian Fainelli
2018-05-11 22:02 ` [PATCH 2/2] soc: bcm: brcmstb: Add missing DDR MEMC compatible strings Florian Fainelli
2018-05-22 22:31 ` Rob Herring
2018-06-04 21:15 ` 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=20180511220242.837-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.0xf0@gmail.com \
--cc=justinpopo6@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=opendmb@gmail.com \
--cc=robh+dt@kernel.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).