linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Broadcom drivers changes for 4.15 (part 1)
Date: Fri, 20 Oct 2017 22:27:37 +0200	[thread overview]
Message-ID: <CAK8P3a0FYQu5GESHFTunJQC7kVfvBoocJRG2+Fr1SoQyRkoZDg@mail.gmail.com> (raw)
In-Reply-To: <20170925190112.3915-2-f.fainelli@gmail.com>

On Mon, Sep 25, 2017 at 9:01 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> This pull requests contains Broadcom SoCs drivers updates for 4.15, please pull
> the following:
>
> - Markus adds support for the Broadcom STB DDR PHY frontend which supports
>   dynamic firmware loading and offers the ability to respond with DRAM refresh
>   rates. He also adds a proper documentation binding document for that
>   peripheral
>
> - Brian adds support for S2/S3/S5 system suspend/resume modes on ARM-based SoCs
>   which is not new but had been lingering for a long time.
>
> - Justin adds S2/S3 system suspend/resume modes on MIPS-based SoCs which is a
>   bit new newer and builds on top of the ARM-based support.
>
> - Florian adds Device Tree binding documents for both ARM and MIPS based systems
>   describing the necessary nodes for S2/S3/S5 on these SoCs.
>
> (This pull request somehow missed the 4.14 merge window and is now being sent again
> for 4.15 along with build fixes from Arnd).

Pulled into next/drivers, thanks!

        Arnd

  reply	other threads:[~2017-10-20 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 19:01 [GIT PULL 1/2] Broadcom soc changes for 4.15 (part 1) Florian Fainelli
2017-09-25 19:01 ` [GIT PULL 2/2] Broadcom drivers " Florian Fainelli
2017-10-20 20:27   ` Arnd Bergmann [this message]
2017-10-19 16:08 ` [GIT PULL 1/2] Broadcom soc " Arnd Bergmann

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=CAK8P3a0FYQu5GESHFTunJQC7kVfvBoocJRG2+Fr1SoQyRkoZDg@mail.gmail.com \
    --to=arnd@arndb.de \
    --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).